Yes — once Person Accounts is enabled in an org, you can absolutely have both regular (Business) Accounts and Person Accounts coexisting. They live in the same Account object, distinguished by Record Type and the IsPersonAccount system field. This hybrid scenario is common in industries that sell to both businesses and consumers — insurance, financial services, telecom, retail, healthcare.
The setup
When Person Accounts is enabled:
- Salesforce creates a default “Person Account” Record Type on the Account object.
- You can keep your existing Business Account Record Type(s) — they continue working as before.
- Users see both Record Types when creating an Account (subject to profile/perm-set assignments).
- Each Account record is one or the other — never both.
Internally:
- A Business Account is one row in the
Accounttable; its contacts are separate rows inContact. - A Person Account is two related rows: an Account row (with
IsPersonAccount = true) and a backing Contact row (withContact.IsPersonAccount = true). Salesforce hides the duality from most UIs — to a user, it looks like one record.
A typical hybrid use case
An insurance company sells:
- Personal Lines (auto, home, life) directly to consumers → Person Accounts
- Commercial Lines (business insurance) to companies → Business Accounts
The same agent might handle both. The Account list view can be filtered by Record Type — “My Personal Accounts” vs “My Commercial Accounts” — and most automation, reports, and page layouts adapt by Record Type.
What’s the same for both
- Stored in
Accountobject - Both have
OwnerId,Type,Industry,BillingAddressfields - Both support Opportunities, Cases, Tasks, Events, Notes, Files, Activities
- Both support Sharing rules, Account Teams, custom fields, validation rules
- Both can be parent of related custom objects
- Both can be auto-assigned via Account Assignment Rules
What’s different
| Aspect | Business Account | Person Account |
|---|---|---|
| Contacts | Has many separate Contact records | One implicit Contact (the Person itself) |
| Name | Company name (Account.Name) | Auto-built FirstName + LastName |
| Person fields (Birthdate, Email) | On Contact only | On Account directly (Person Account) |
| Record Type | Standard / business | Person Account RT |
IsPersonAccount | false | true |
| Person-Account-specific page layouts | N/A | Required |
| Marketing campaign membership | Via Contact | Direct via Person Account (Account itself becomes the Campaign Member) |
Page layouts
Person Accounts use their own dedicated page layouts — they’re distinct from Business Account layouts because the fields shown differ (you want Birthdate, SSN, personal address on Person Accounts; not on Business Accounts). When you enable Person Accounts, Salesforce auto-creates a “Person Account” page layout for you to customize.
Permissions and visibility
Both types respect the same sharing model. A user with Read access to “My Accounts” sees both regular Accounts and Person Accounts they own. Sharing rules can target one type via Record Type criteria.
You can also restrict Record Type assignment — e.g., the Commercial sales team only sees the Business Account Record Type, the Consumer team only sees Person Account — even though both records live in the same object.
Reporting in a hybrid org
Most standard reports work for both types. To filter to one or the other:
- Add a filter:
Account.IsPersonAccount = true(or false) - Or filter by Record Type Name = “Person Account”
Joining Person Accounts to Cases, Opportunities, Tasks works exactly like a Business Account-Contact join — Salesforce abstracts the duality.
Integration considerations
External systems pushing data into Account need to know which type they’re creating. Typical pattern: if a “person” field set is populated (FirstName, LastName, Email), create as Person Account; if “company” fields are present (Company Name), create as Business Account.
The IsPersonAccount flag can’t be set at insert directly — you set the Record Type, and Salesforce derives the rest.
Common interview answer
“Yes, once Person Accounts is enabled in an org, both regular Business Accounts and Person Accounts coexist on the same Account object. They’re distinguished by Record Type and the
IsPersonAccountsystem field. This is the standard pattern for hybrid B2B+B2C orgs — for example, an insurance company selling to both businesses and individuals.”
One-way street caveat
Worth restating: enabling Person Accounts is irreversible. You can co-exist with regular accounts freely after enabling, but you can never go back to a Person-Account-disabled org. Test thoroughly in sandbox before turning it on in production.
Verified against: Salesforce Help — Person Accounts Overview. Last reviewed 2026-05-17.