Overview
Sync is a feature within Application Lifecycle Management(ALM), and can only be leveraged that allows Power Users to copy over their Production environment's configurations into their Sandbox environment. This ensures that teams can build and test against applications that accurately mirror Production, without the risk of manual duplication errors or configuration drift over time. Sync is a one-way operation — it copies Production into Sandbox and cannot be run in the reverse direction.
Before you begin
Sync requires two active environments — Production and Sandbox — and must be enabled before it can be accessed. If your organization does not have a Sandbox environment or would like to enable Sync, please contact your account team.
How ALM Sync Works
Once Sync is enabled, environment banners will appear at the top of the screen to indicate which environment you are currently working in:
These banners will only be visible to users that have a Build entitlement.
Initiating a Sync
To initiate a Sync, you must be in the Production environment and have an Admin-All entitlement. The Sync page and the "Manage Environments" button are not visible in Sandbox, and users who do not hold the Admin-All entitlement will not see the sync controls even when viewing Production.
To begin a sync, navigate to the Production environment and click "Manage Environments" on the environment banner:
This will bring users to the Manage Environments Page, where Sync can be initiated from the Sync card.
The first modal presents consequence messaging describing the impact of running a sync. Clicking "Cancel" or the X exits the flow entirely with no changes made. Clicking "Continue" advances to the next step without starting the sync.
The second modal gives you the option to opt in to email notifications for sync status updates. You can specify individual users or roles to notify, though the sync initiator will always be notified regardless.
The final modal requires you to type the word "Sync" to activate the "Start Sync" button. This is intentional and exists to prevent accidental initiation. Once "Start Sync" is clicked, the operation begins.
What Happens During a Sync
Once a sync begins, all users currently logged into Sandbox are logged out immediately and presented with a static page indicating that a sync is in progress. Users cannot log back into Sandbox until the sync completes, but Production remains fully accessible during the operation.
Please note: any configuration changes made in Production during an active sync will not be included in that sync. We recommend pausing active building in Production until the sync has completed.
When the sync completes, the static page is removed, users can log back into Sandbox, and the sync history is updated with the date, the initiating user, and a status of "Complete." Once a sync completes successfully, a new sync cannot be initiated for seven days from that completion date. The Sync Environments card will reflect this:
Sync History
Every sync operation is recorded in Sync History, accessible by clicking "View History" on the Sync page. The history displays the date each sync was completed, the initiating user, and the resulting status. In-progress syncs appear at the top, and history is sorted by date requested in descending order. Sync History can be downloaded as a CSV file for record-keeping or audit purposes:
What Gets Synced and What Doesn't
Sync copies Production configuration into Sandbox. This includes applications, access objects, reports, and integration configurations. Operational data — including records, user accounts, attachments, and images — is not carried over. Admins should verify that the correct users have appropriate access in Sandbox before resuming test activities.
Integration configurations are copied from Production, but the credentials and environment-specific settings that make them functional are not. RCC integrations, self-built API integrations, and third-party connectors will need to be manually reconfigured in Sandbox after every sync before they are operational again.
SSO and SCIM are the only exception — after the first sync, those settings are retained in Sandbox and do not require reconfiguration on subsequent syncs. Likewise, after the first sync, user accounts will persist in the Sandbox environment, and will not need to be recreated.
Best Practices
ALM Sync is a destructive operation — when initiated, it immediately overwrites everything in Sandbox with Production configuration. Any in-progress work, test data, or configuration changes that exist only in Sandbox will be permanently lost. Because of this, communication before initiating a sync is critical.
Notify your team before syncing, confirm that no active work is taking place in Sandbox, and schedule syncs during low-activity windows such as after hours or weekends. Users who are logged into Sandbox at the time a sync begins will be logged out immediately with no grace period, so giving your team advance notice is essential to avoid disruption or loss of work.
Before syncing, confirm who is responsible for reconfiguring each active integration in Sandbox afterward, and build that step into a post-sync checklist to avoid teams working against broken connections. Since records are not carried over, maintaining a documented set of test scenarios or seed data that can be quickly re-entered will help your team resume testing faster.
Consider syncing at natural project milestones — such as after a major Production configuration change or before a new round of user acceptance testing — rather than on a frequent basis. Always confirm that Sync History shows a status of "Complete" before directing your team back to Sandbox, as a sync in an error state may leave Sandbox in an indeterminate condition.
FAQs
How often can I run a sync?
Once per seven-day period, measured from the last successfully completed sync. Failed or errored syncs do not count toward this limit.
Can I schedule a sync to run automatically?
No. Syncs must be manually initiated by an eligible administrator through the Sync page each time.
Can I sync from Sandbox to Production?
No. Sync is one-directional — Production into Sandbox only.
What happens to my integrations after a sync?
Integration configurations are copied from Production, but credentials and environment-specific settings must be manually reconfigured in Sandbox before those integrations will function. SSO and SCIM are retained in Sandbox after the first sync and do not need to be reconfigured.
What happens to users who are logged into Sandbox when a sync starts?
They are logged out immediately with no grace period and will see a static page until the sync completes.
Does sync affect manually added users or user groups in Sandbox?
User accounts are not included in the sync, but any users in Sandbox will retain after the first sync. Admins should still verify that the correct users have the appropriate access in Sandbox after each sync.
What if a sync fails?
A failed sync will show an "Error" status in Sync History and does not count toward the weekly sync limit. Sandbox may be left in an indeterminate state and should not be used until the issue is resolved. Contact support if you encounter a sync failure.
Can I run a second sync while one is in progress?
No. Only one sync can run at a time. The Sync button is disabled while a sync is in progress.
ALM Sync Limitations
- Sync is one-directional (Production to Sandbox only) and cannot be reversed
- Syncs must be manually initiated and cannot be scheduled or automated
- Only one sync is permitted per seven-day period
- Records, user accounts, attachments, and images are not included in the sync
Integrations (except for SSO and SCIM) require manual reconfiguration in Sandbox after every sync