Considerations for Person Account Migration

Consider including these steps in your plan before you migrate account and contact records to person account records.

• Modify and validate your data to meet these requirements:
  • Only individual accounts with a single direct account contact relationship can successfully convert to person accounts. For each person account, the account record has only one contact record.
  • The account and contact have the same record owner.
  • The account and contact use the same currency value, if applicable.
  • Both the Parent Account field on the account and the Reports To field on the contact are empty.
  • The account isn’t a parent account of any other account records.
  • No other contact records relate to the contact.
  • The migration maps the contact name to person accounts. If you used a middle name, salutation, and suffix, the migration run includes that information in the name of the person account.
  • The contact cannot be associated with an active Community user.
• Review third-party applications for compatibility with person accounts.
• Turn off tracking for the Account Name field.
• Consider any limitations of using Data Loader to migrate data.
• Migrate contact-triggered automations.
  • Take an inventory of automations that are initiated when a contact is created, updated, or deleted.
  • Simplify where possible, and eliminate unused automations.
  • Consider best practices for setting up automations.
  • Decide what will be built in Flow, and in Apex after migrating to Education Cloud.
  • In a sandbox, recreate the automations on the account object.
    • For Flow and Apex, use the IsPersonAccount field to ensure that the automations don’t run for business or organization accounts.
    • Move Workflows and Process Builder automations to Flow or Apex.
    • Consider a trigger framework for Apex automations.
• Migrate validation rules.
  • Take an inventory of validation rules on the contact object.
  • Simplify where possible, and eliminate rules that aren’t required.
  • In a sandbox, recreate the validation rules on the account object. Use the IsPersonAccount field to ensure that the validation rules don’t apply to business or organization accounts.
• Migrate Experience Cloud users.
  • Deactivate all users associated with contacts.
  • Migrate contacts to person accounts.
  • Create new users and relate them with person accounts.
  • Reassociate record ownership if needed.
• Create the required record types and then rebuild page layouts for person accounts.
• Update lookup reference IDs, if needed.
• Test your person account migration sequence in a sandbox, including page layouts and user experience.

SEE ALSO:

• Considerations for Using Person Accounts
• When to Use Data Loader
• Salesforce Automation Best Practice Guide
• Migrate Account and Contact Records to Education Cloud