Organization Sync is available in: Enterprise, Performance, Unlimited, and Developer Editions
To use Organization Sync, you must purchase a secondary Salesforce org and its accompanying user licenses.
The primary and secondary orgs must be the same organization type (for example, production or sandbox) and edition.
To avoid inconsistent behavior, both orgs must have the same limits and settings. If the limits of the primary org have been adjusted, contact Salesforce to have the same changes made in the secondary org.
To avoid Duplicates Detected errors, we recommend turning off duplicate management in secondary orgs.
Organization Sync can be configured to work for more than two orgs, but it is designed to support a two-org setup.
Encrypted fields—both standard and custom—aren’t synced.
If you’ve enabled the option to sync feeds and audit fields, audit fields don’t appear in the list of publishable fields because they’re automatically synced. Audit fields are only synced when a record is copied from one org to another (for example, during a bulk sync). If an audit field on a synced record is updated, that update is not reflected in the linked org.
Rich text area (RTA) fields aren’t synced.
Formula fields and roll-up summary fields can’t be published because their values are determined by other fields’ values. As a workaround, make sure that the input fields for a formula or summary roll-up field are published. Then, create an identical formula or roll-up summary field in the secondary organization that refers to those input fields to calculate its value.
Lookup fields to unpublished objects aren’t automatically published because publishing such fields can cause syncing errors. For example, if a field on the Contact object includes a lookup to accounts and the Account object hasn’t yet been published, that field can only be published manually.
Callout fields such as geolocation fields aren’t synced.
Supported metadata is only synced in one direction, from the primary to the secondary org.
LiveAgent, Salesforce Knowledge, Portals, and Communities aren’t supported.
Managed packages aren’t synced. If you wish, you can install a package on both organizations to keep the user experience consistent.
Chatter file posts larger than 2 GB aren’t synced.
Chatter topics, groups, and likes aren’t synced.
In synced Chatter posts, user mentions aren’t clickable.
Chatter file versions aren’t supported.
Automation and Data Structure
Multi-level lookups with more than one level are only synced during bulk syncs.
Apex triggers, processes, and workflows aren’t duplicated from one org to the other because duplicate automation can lead to looping updates or errors. You may need to adapt your existing triggers, processes, and workflows for the secondary org.
A bulk sync can only copy records that were last created or modified no more than one year before the bulk sync date.
If the secondary org contained records before you established a connection between the two orgs, those pre-existing records in the secondary org aren’t auto-connected to matching records in the primary org. In this situation, bulk syncing entities that already exist in both orgs will cause duplicate alerts if duplicate management is enabled.
Salesforce does not recommend using a two-way sync for some objects and fields and a one-way sync for others.