Title: Initiate a data sync operation
Author: liranadia
Published: October 1, 2026
Last modified: October 20, 2026

---

 1. [Databases](https://docs.wpvip.com/databases/)
 2. [Data sync between environments](https://docs.wpvip.com/databases/data-sync-between-environments/)
 3. Initiate a data sync operation

#  Initiate a data sync operation

**Caution**

**A sync to production overwrites production data and cannot be undone. **When the
destination is a production environment, a notice will warn that the action will
override data on the production site.

 1.  In the VIP Dashboard, select the application and the environment that will receive
     the data. This environment is the destination for the sync.
 2.  Navigate to **Sync Data** under the environment’s database options.
 3.  Complete the [step-up authentication](https://docs.wpvip.com/manage-user-access/vip-dashboard/step-up-auth/#Pop-up-window-for-authentication)
     challenge when prompted.
 4.  Under **Sync Data From**, select the source environment. The source environment’s
     database size and domain are displayed.
 5.  Review the **Sync Data To** panel, which displays the destination environment 
     and the time of its last backup. Refer to the Caution callout above when the destination
     is a production environment.
 6.  Review the mapped domains for the sync. Confirm that every required replacement
     is in the saved list. Review [Mapped domains](https://docs.wpvip.com/databases/data-sync-between-environments/#3-mapped-domains).
 7.  Under **Sync Method**, select how the data is applied to the destination environment.
     Review [Sync methods](https://docs.wpvip.com/databases/data-sync-between-environments/initiate-a-data-sync-operation/).
 8.  Select **Begin Sync**. A confirmation dialog summarizes the operation. When the
     destination is production, the dialog repeats the warning that production data
     will be overridden. When suggested mappings are unresolved, the dialog warns that
     those domains will not be replaced.
 9.  Confirm the operation to start the sync.

A data sync is a one-time operation and does not run again automatically. To run
another sync later, return to the **Sync Data** page and start a new sync.

If a required value is missing or the sync cannot start, the page reports the reason
above the form and next to the field that requires attention.

## Sync methods

The sync method determines how source data is applied to the destination environment.
Both methods perform a full-database sync. The method controls how the data is applied,
not how much data is transferred.

| **Method** | **Behavior** | 
| Replace database | Removes all existing data in the destination environment and replaces it with the source database. This can result in brief downtime and is best scheduled during low-traffic periods. | 
| Update existing database | Updates existing data in the destination environment and adds new data from the source. Data that exists only in the destination environment is not removed. |

**Replace database** is selected by default. Confirm the selected method in the 
confirmation dialog before starting a sync.

## Monitor sync progress

While a sync is running, a progress bar at the top of the **Sync Data** page reports
its status as the sync moves through its stages — started, importing, and cleanup—
and displays a completion percentage. Expanding the progress bar displays the source
and destination environments, the sync scope, and the selected sync method. When
a sync finishes, the progress bar reports the time the sync completed and how long
it took.

## Actions that occur during a data sync

During a data sync, the destination environment is placed in maintenance mode while
its database is overwritten with the source database. Domain and URL references 
are then replaced according to the saved mapped domains, with the destination environment’s
primary domain applied, or its convenience domain when no primary domain exists.
Protected options are restored, cleanup commands run, Jetpack reconnects, the object
cache is flushed, and maintenance mode is deactivated. Media files load automatically
after the sync completes.

## Protected options

A specific set of options that exist in the destination environment are backed up
before the data sync begins, then restored after the data sync has completed. This
prevents environment-specific configuration from being overwritten by the source
environment’s data.

## Troubleshooting

### A sync did not complete

When a sync fails, the **Sync Data** page displays a notice stating that something
went wrong with the sync and that VIP Support has been notified. No further action
is required to alert VIP Support. To retry, start a new sync from the **Sync Data**
page once the cause has been addressed. If the failure persists, contact [VIP Support](https://docs.wpvip.com/vip-support/).

### Links or references point at the source environment after a sync

The domain was not replaced because no saved mapping covered it. Open the **Sync
Data** page for the same source and destination pair, add the missing mapping to
the saved list, and run the sync again. Check the suggested list as well. A suggestion
that was never saved is not applied.

### A mapping cannot be saved

The mapping is missing a value, is not a valid domain, or conflicts with an existing
mapping. The reason is displayed next to the mapping being edited. Correct the value
and save again.

Last updated: October 20, 2026