You are here:
Considerations for Transforming the Individual Data Model to Person Accounts in Financial Services Cloud
Review these considerations to determine whether transforming the individual data model to person accounts in Financial Services Cloud is right for your company.
After the person accounts model is enabled, you can’t disable it. This restriction is valid across Salesforce and not limited to Financial Services Cloud.
Review your technical architecture and the customizations that you’ve made to the following to ensure compatibility with person accounts:
-
Triggers, flows, and workflow rules
-
Components
-
Reports
Before switching from the individual data model to person accounts, be aware of the following:
-
Sharing—If you enable person accounts, your options for Organization-Wide Defaults (OWD) sharing are limited to either Controlled by Parent on Contact or Private on Account and Contact.
-
Business processes—If your org includes business accounts, contacts, and person accounts, consider whether you need to write separate business processes or workflows.
-
Integration—Integrations between Salesforce and third-party systems via the API use the Account object to access person accounts. You can query and update the Contact object via the API, but person accounts are created with the Account object.
-
AppExchange packages—Many applications designed for the Account and Contact objects work with person accounts. Check whether your third-party applications support person accounts.
After switching to person accounts:
- Use the Activities Lightning component, not the Client Activities component, to display the activity timeline for a person account.
- Use the standard Chatter Feed component, not the Client Collaborate component, for collaboration.
