---
schema_version: "1"
id: 957742b3b7a24abf8107b3d39db650778f52cdb5453e5903d1ad27ff434c4c2a
title: Lightning Sync Considerations for Companies With Multiple Salesforce Organizations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/exchange_sync_admin_config_avoid_sync.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.exchange_sync_admin_config_avoid_sync.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ad80f911816acc038b1e9a78cebcad3788198bcfb45f1bd436c9d7b73348ee14
description: If your company uses multiple Salesforce organizations, review these considerations to avoid sync issues and unsupported configurations.
products:
  - Sales Cloud
  - Cross Cloud
  - Service Cloud Voice
release: "264"
---
# 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.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available to sync records from: Salesforce Classic, Lightning Experience, and the Salesforce mobile app</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available to set up from: Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Sales Cloud, Service Cloud, and Lightning Platform</td></tr></tbody></table>

You’re using multiple organizations if you:

- Test new features in a sandbox org before setting up features in your live production org.
- Maintain separate Salesforce orgs for different divisions of your company.

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.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_productivity-264-0-0-production-enus/b2f6c36a-fa61-4a3c-9752-032ce1818a69/images/icon_example.png)

Example

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.