Use person accounts when most of your customers are individuals who buy, sign or get served in their own name. Homeowners, patients, students, retail investors and donors fit that pattern. Stay with business accounts and contacts when individuals are rare or always tied to an employer. Decide carefully, because Salesforce does not let you switch person accounts off once they are enabled. Test the change in a sandbox against your integrations, reports and installed packages first.
Why does the standard Account and Contact model struggle with individual customers?
Account and Contact assume every person works for a company. When the customer is the person, you either invent a fake company or leave the contact without a meaningful parent.
That mismatch shows up quickly. Opportunities, cases and orders want an account. A homeowner who buys a roof has no employer that matters to the sale. Teams end up typing the person's surname into the account name, or parking thousands of people under one placeholder record. Both workarounds leak into every report, every integration and every duplicate check that follows.
What exactly is a person account in Salesforce?
A person account is an account record type that also carries contact fields, so one record represents one individual. Behind the screen, Salesforce stores a linked account and contact pair.
Users see a single page with a first name, last name, email, phone and mailing address. Opportunities, cases and activities attach to it the way they attach to any account. Because a contact sits underneath, the person can still be a campaign member or receive email. Accounts that are not person accounts are called business accounts, and both kinds can live in one org.
Salesforce Help lists several prerequisites and warnings. Confirm them against current documentation before you schedule the work.
- The Account object needs at least one record type before you enable the feature.
- Contact sharing must be Controlled by Parent, or Account and Contact sharing must both be Private.
- Profiles that can read accounts should also be able to read contacts.
- The admin enabling it needs Customize Application and View All Profiles permissions.
- Once enabled, person accounts cannot be disabled, so Salesforce recommends previewing the effect in a sandbox.
What are the alternatives to person accounts?
There are four common alternatives: a single bucket account, one account per individual, industry household models, and Contacts to Multiple Accounts. Each solves part of the problem.
The bucket approach parks every individual under one account called something like Individuals or Consumers. It is quick, but it creates account data skew. Salesforce engineering guidance warns about locking and sharing slowdowns once an account has more than about 10,000 child records. It also makes account-level reporting meaningless, since one account appears to own all consumer revenue.
The one-account-per-person approach, sometimes called the individual model, creates a business account named after each customer with a single contact beneath it. It avoids skew but doubles data entry, splits fields across two pages, and invites drift between the account name and the contact name.
Industry clouds add a household layer on top of person accounts rather than replacing them. Financial Services Cloud and Nonprofit Cloud both group individuals into households through relationship records. If you are heading toward either product, read the dedicated guide first, because the cloud's data model drives the person account decision for you.
Contacts to Multiple Accounts links one contact to several accounts through an account contact relationship. It suits advisers, board members or consultants who work with several firms. Salesforce Help says person accounts can take part, but only as indirect relationships, because a person account has no primary account.
| Modeling option | Best for | Reporting impact | Pitfall |
|---|---|---|---|
| Person accounts | Businesses where most customers are individuals buying in their own name | Individuals show in account reports, and Is Person Account separates them from companies | Irreversible once enabled; some packages and integrations do not support them |
| Bucket account | A handful of individuals in an otherwise business-to-business org | All consumer activity rolls to one account, hiding real customer counts | Data skew and locking once the account holds many thousands of contacts |
| One business account per individual | Small consumer volumes where enabling person accounts is not yet justified | Counts look right, but every report mixes fake companies with real ones | Duplicate data entry and names drifting between account and contact |
| Households in an industry cloud | Wealth, banking, insurance and nonprofit teams that serve families | Household roll-ups for assets, gifts or policies, built on person accounts | Choosing the household design before agreeing how members are matched |
| Contacts to Multiple Accounts | People linked to several organizations, such as advisers or trustees | Relationship reports show every account a person touches | Treating it as a substitute for person accounts in a consumer business |
Can business and consumer customers share one Salesforce org?
Yes. Mixed orgs are common, and person accounts were designed to sit beside business accounts. The work is in keeping the two experiences clearly separated.
- Record types: at least one person account record type and one business account record type, with sensible defaults per profile.
- Page layouts: a consumer layout with personal fields and a business layout with company fields, so neither team sees clutter.
- List views and reports: a filter on Is Person Account in every saved view that should show only one kind.
- Automation: flows and validation rules that check the record kind before requiring fields such as industry or employee count.
- Opportunity and case processes: separate sales paths or support queues where consumer and business journeys genuinely differ.
Leadership dashboards usually need both views at once. Build them by grouping on Is Person Account rather than maintaining two parallel sets of reports. That keeps totals reconcilable when someone asks why the numbers differ.
Hierarchies are a separate decision. Person accounts cannot have a parent account, so corporate family trees belong on business accounts only.
How do person accounts change reports, duplicates and lead conversion?
They touch all three. Plan each one before enabling, rather than discovering the effect after go-live.
Reports. Salesforce Help says person account fields appear in account reports with a Person Account prefix. The Is Person Account field is available in both account and contact reports. Existing contact reports may suddenly include consumers, so review saved reports and dashboards for unexpected totals.
Duplicates. Salesforce ships a standard person account matching rule and duplicate rule, which you activate after enabling the feature. Its match keys include email; first initial and last name with city or postal code; street address; and phone. Consumer data often has shared household emails and common names, so tune the rule against a sample before relying on it.
Lead conversion. In Lightning Experience, Salesforce converts a lead with a blank Company field into a person account. A lead with a company becomes a business account and contact. The converting user's default person account record type is applied, so web forms and lead record types need to handle Company deliberately.
Which integrations and packages need checking before you enable person accounts?
Check every system that reads or writes accounts and contacts. Some tools assume a contact always belongs to a separate company record.
- Installed AgentExchange (formerly AppExchange) packages: look for explicit person account support in the listing or vendor documentation, then test in a sandbox.
- Custom code: Apex, flows and integration mappings that create a contact and an account separately may fail or create stray records.
- Email, telephony and form tools: confirm they can match an inbound email to a person account, not only to a lead or contact.
- Billing, ecommerce and ERP connectors: check whether customer sync expects a company name on every account.
- Marketing platforms: confirm how each one represents a person account before you migrate any data.
Account Engagement handles person accounts through a connector setting called Sync Prospects with Person Accounts. Salesforce Help notes that the setting cannot be turned off once enabled. Marketing Cloud Engagement and other tools have their own rules. Ask each vendor, and your Salesforce account team, how sync works today.
What does a person account cost in storage and licensing?
Expect more data storage per individual than a contact alone. Each person account is generally understood to use storage as both an account and a contact, so model your storage before a large load.
That roughly doubles the per-record footprint compared with storing the same customer as a contact. For a consumer business with large customer volumes, model storage before migration rather than after. Edition requirements and any licensing effects vary, so confirm them with your Salesforce account team.
How should individual customer data be protected?
Treat person accounts as personal data from day one. Consent, retention and deletion requests apply to each individual, not to a company.
Salesforce's Individual object stores privacy preferences and can link to the leads, contacts and person accounts that represent the same human. The wider consent data model adds channel-level and contact point consent. Which objects you need, and whether a product such as Privacy Center applies, depends on your regulations and edition. Our data privacy guide covers the controls in more depth.
How do you move existing contacts into person accounts?
Salesforce converts a business account into a person account when you change its record type. That only works when the account has exactly one contact and meets a few other conditions.
- Profile the current data: which contacts sit under bucket accounts, which share an account with colleagues, and which have no account at all.
- Reshape it so each consumer has their own business account with one contact, creating accounts for extra contacts where needed.
- Check blockers: Salesforce Help notes that accounts enabled for customer portal or Experience Cloud users cannot be converted this way.
- Change the record type to the person account record type in batches with Data Loader or a similar tool.
- Reconcile counts, related opportunities and cases, and campaign history after each batch.
What belongs in a phase-one person account plan?
Phase one should prove the model on one customer segment before the whole database moves. Keep scope narrow and the decision log explicit.
- Write down which customers become person accounts and which stay business accounts, with examples of edge cases.
- Inventory integrations, packages and automation that touch accounts or contacts, and record each one's support status.
- Enable person accounts in a sandbox and run the full regression suite there.
- Design record types, layouts, duplicate rules and lead conversion behavior for both kinds of customer.
- Convert one segment, compare reports against the old model, and agree any differences with leadership.
- Set up consent tracking and a process for privacy requests before consumer volumes grow.
If an industry cloud is in your future, sequence that decision first. Rebuilding households after a generic person account rollout is avoidable work.
