Person Accounts combine the fields of both Account and Contact objects into a single record, making them ideal for organizations that work with individual consumers rather than business entities. For example, a financial services company might use Person Accounts to track individual clients, or a healthcare organization might use them to manage patient records. Because Person Accounts fundamentally change the data model of your org, once enabled, they cannot be disabled — not even by Salesforce Support.
As part of the Person Accounts enablement process, administrators are required to acknowledge that the feature cannot be disabled. We strongly advise testing this feature in a Sandbox before enabling it in Production so you can evaluate how it will work in your environment.
Note: This is a permanent, irreversible change to your organization's data model. Please review all relevant documentation and test thoroughly in a Sandbox prior to enabling Person Accounts in Production.
Professional, Enterprise, Unlimited, and Developer
Submit an activation request with Salesforce Support
Review Salesforce documentation on Person Accounts and thoroughly test in a Sandbox environment before submitting an activation request.
Person Accounts are designed for organizations that need to manage relationships with individual people rather than business accounts. Common business use cases include:
Because Person Accounts merge the Account and Contact objects at a data model level, enabling this feature triggers structural changes throughout the org that cannot be reversed.
Once Person Accounts have been enabled, they cannot be fully disabled by the organization or by Salesforce Support. This is a permanent change to your organization's data model.
Although the feature cannot be fully disabled, a System Administrator can remove the Person Account record type from profiles to restrict access. Removing the Person Account record type from profiles will prevent users from creating new records using that record type, effectively hiding it from end users without altering the underlying data model.
To remove the Person Account record type from a profile:
Important: This does not disable Person Accounts — it only restricts user access to the record type. Existing Person Account records will remain in the org.
000387315

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.