Section 2 · Security and Access · 20% of exam
2.3 Person accounts and complex account-contact models
Exam objective
Compare the capabilities and implications of Person Accounts, business Accounts, Contacts, and Contacts to Multiple Accounts.
Salesforce models organizations as Accounts and people as Contacts. A Contact is normally related to a primary Account, giving users an organizational view of people and their business relationships. Person Accounts combine account and contact behavior for an individual consumer who needs account-like attributes and contact-like interaction history. They are not simply a second record type for every Contact: enabling Person Accounts is an org-level choice with implementation consequences and should be based on a real business model.
Use business accounts when the customer is an organization and people act as employees, buyers, or stakeholders within it. Use Person Accounts when each customer is an individual and the organization must manage that individual as a customer with account behavior. Person Accounts affect integrations, automation, reporting, imports, and relationships to other records. Some business processes assume that every Account represents a company, so changing that assumption can complicate downstream logic. Review the current Salesforce documentation and test the intended feature set before enabling Person Accounts.
Contacts to Multiple Accounts allows a Contact to have a primary account plus indirect relationships with other accounts. Account Contact Relationships can capture a person's role across subsidiaries, partner organizations, or customer accounts without creating duplicate Contact records. The primary relationship remains meaningful; additional relationships can carry role and status information. This model is useful when one person legitimately works with multiple entities. It is not appropriate to represent multiple people by attaching one Contact to many accounts or to bypass duplicate management.
When choosing a model, ask what the business calls a customer, how it bills and services the customer, whether individuals need account-level ownership or attributes, and how external systems identify the person. Then inspect lead conversion, opportunities, cases, campaigns, activities, sharing, and reporting. A model that fits a simple sales pipeline may fail for a household, a regulated patient, or a partner employee. Map each relationship before importing data, and determine which system is the source of truth for identity.
Data quality and access are closely connected. A duplicate Contact can split history and consent records; an incorrectly attached Contact can reveal information to another account's users. Use matching and duplicate rules, stable external identifiers, and governance for account-contact relationship changes. Limit who can create or change cross-account relationships when those links expose sensitive associations. For Person Accounts, validate how fields, record types, account hierarchy behavior, and integrations represent the combined individual record.
Scenario method: draw entities and cardinalities before creating records. If one organization has many people, model Account-to-Contacts. If one person belongs to more than one organization, evaluate Contact to Multiple Accounts. If a consumer is the account-level customer, evaluate Person Accounts and the lifecycle implications. Confirm whether standard functionality supports the needed relationship and whether reporting and sharing behave as expected. Test conversion and integration flows using records that reflect real edge cases, not only clean sample data. Exam focus: recognize that Person Accounts are for individual consumers and require deliberate org-level adoption. Recognize that Contacts to Multiple Accounts represents multiple legitimate business relationships for one person. Compare the data model rather than choosing a feature based on a label. Consider impact on visibility, reporting, imports, and integrations. When the requirement is simply to classify a person or distinguish business units, a record type or field may be more appropriate than a major account model change.
For relationship questions, count the real-world entities and ask whether the relationship is one-to-many or many-to-many before selecting a Salesforce object design.
Model migration deserves special attention. Identify whether a consumer already exists as a business Contact, how duplicate rules will match that person, what external ID remains stable, and how opportunities, cases, consent, activities, and household relationships will be migrated. Test report totals before and after conversion. Keep a rollback copy and compare downstream integrations that expect Account and Contact records separately. A relationship model should be tested with ordinary cases and with exceptions such as a person changing employers, representing multiple organizations, or requesting deletion of personal data.
Practical scenario:
A consultant works for a delivery partner and also advises two customer companies. Keep one Contact identity and create the appropriate additional account relationships with roles, rather than duplicating the person's Contact record. If the business instead sells directly to individual consumers with account-based service histories, assess Person Accounts separately and validate integrations before adoption.
Extra concept:
External IDs help preserve identity across imports and integrations, but they do not define the relationship model. A stable identifier can prevent duplicate creation while an Account Contact Relationship describes the person's affiliation. Keep identity, relationship, and access decisions distinct.
Key takeaways
- Use Person Accounts for individual consumer customers when the org model supports them.
- Use Contacts to Multiple Accounts for one person with several legitimate organizations.
- Test migration, sharing, integrations, and duplicate controls before changing the model.
- Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.account_contact_relationships.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.overview_of_custom_object_relationships.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&type=5
