Working with Salesforce Person Accounts

Overview

Our Salesforce integration supports both standard Account-Contact models, as well as Salesforce Person Accounts. This article explains how Person Accounts are synced from Salesforce to Ortto.


Person Accounts in Ortto

In Salesforce, a Person Account combines Account and Contact fields into a single record to simplify managing information about individual customers.

By default, Ortto automatically creates an Organization and Contact record for each Person Account in Salesforce.

To ensure data syncs correctly, refer to the sections below on setting up selective sync criteria and configuring journey action shapes.


Selective sync

The selective sync for Accounts and Contacts operates independently. If you are working with Person Accounts, it’s important to align the selective sync settings for both to ensure each Contact has a corresponding Account (Organization) record in Ortto, enabling seamless data syncing back to Salesforce, especially through Journey action shapes.

Example of selectve sync setup with Person Accounts.

In the example above, the same field is used for both the Account and Contact objects. This approach guarantees that both objects are synced to Ortto (Organization and Contact), preventing any misalignment between records.

NOTE: Not all fields are shared between Account and Contact records in Salesforce—only a subset is mirrored between these objects. If a custom field isn’t available in the Contact filter when setting up selective sync criteria, you’ll need to create it as a Contact field in Salesforce first.


Journey action shapes

When working with Person Accounts, updates from Ortto to Salesforce through a Journey action shape must be made at the Account level. This means you need to select the Account object when sending an update from Ortto to a Person Account in Salesforce.

Example of updating a Person Account via a Journey action. Click on the GIF to maximize it.