Enabling Person Accounts is not a click-path you do on a Tuesday afternoon. The actual day-of steps are short, but every step in the preparation matters more than the toggle itself.
- Audit your org for Account-touching customizations
List every validation rule, sharing rule, trigger, Flow, and Apex class that references Account or Contact. Each one needs a sandbox test against a Person Account record before production enablement.
- Build a sandbox with Person Accounts enabled
Salesforce can enable Person Accounts in a sandbox before production. Use a full or partial-copy sandbox refreshed from production so the test data resembles real records.
- Map field equivalents
Decide which Account-side fields (Industry, AnnualRevenue, Type) still make sense on Person Accounts and which should be hidden from page layouts. Document the mapping for every record type you plan to support.
- Test every automation path
Triggers fire on both the Account and Contact halves of a Person Account write. Walk through every trigger and confirm it does not double-process the same record. Walk through every Flow and confirm it picks the right object to act on.
- File the case to enable in production
With sandbox validation complete, file a Salesforce Support case requesting Person Account enablement in production. Salesforce typically requires a specific request format; check the current Help documentation before filing.
- Roll out in waves
Enable a specific record type or business unit first, audit for a full week, then expand. Mass-enabling across an entire B2C org on day one obscures which downstream system is breaking when something does break.
Every validation rule, sharing rule, trigger, and Flow that references Account or Contact needs explicit consideration. Skipping the audit creates production incidents that look like "the trigger broke" but are actually "the trigger never knew Person Accounts existed."
At least one full release cycle of sandbox testing. The toggle is a one-way change; the cost of catching a problem in sandbox is far less than the cost of catching it after enablement in production.
- Person Accounts cannot be disabled after enablement. The toggle is one-way. Sandbox-test for a full release cycle and roll out in waves before flipping the switch in production.
- Triggers fire on both the Account and Contact halves of a Person Account write. Triggers that were written for Business Accounts often double-process Person Accounts; audit every trigger before enablement.
- Person Accounts complicate Account-Contact Relationship modeling. A Person Account can be the Account in an ACR or the Contact in an ACR, but not both. Document the constraint before architects design relationships into the schema.