You are here:
Lightning Sync Considerations for Companies With Multiple Salesforce Organizations
If your company uses multiple Salesforce organizations, review these considerations to avoid sync issues and unsupported configurations.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
If your company uses multiple Salesforce organizations, review these considerations to avoid sync issues and unsupported configurations.
| Available to sync records from: Salesforce Classic, Lightning Experience, and the Salesforce mobile app |
| Available to set up from: Salesforce Classic and Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions with Sales Cloud, Service Cloud, and Lightning Platform |
You’re using multiple organizations if you:
Setting up the same user to sync across multiple orgs is not supported. While we recommend testing in a sandbox org before rolling out Lightning Sync, remove users from sandbox sync configurations before adding users to production configurations.
Likewise, we don’t recommend marking a Lightning Sync configuration as inactive to prevent a user from syncing across multiple orgs. You risk forgetting that user is included in multiple configurations, and marking the configuration as active later, by accident.
You’re testing Lightning Sync features in your sandbox org. You add user Marianne Schumacher to a sync configuration in the sandbox org. After you’re satisfied with how you’ve set up Lightning Sync features for Marianne, you’re ready to add her to a configuration in your production org.
Before you add Marianne to a configuration in your production org, remove her from the configuration in your sandbox org. Otherwise, Marianne could experience sync issues. You also risk syncing test data onto your production org and email server.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.