Title: VIP Platform: Data Sync and SQL Import Improvements
Author: WordPress VIP Documentation
Published: November 4, 2021
Last modified: August 5, 2025

---

 1. [Changelog](https://docs.wpvip.com/changelog/)
 2. [VIP MU plugins [Production]](https://docs.wpvip.com/changelog/vip-mu-plugins-production/)
 3. VIP Platform: Data Sync and SQL Import Improvements

# VIP Platform: Data Sync and SQL Import Improvements

---

 04 November 2021

18:50:26 GMT+0000

 [ VIP MU plugins [Production] ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/)

 [ Permalink  ](https://docs.wpvip.com/changelog/vip-mu-plugins-production/vip-platform-data-sync-and-sql-import-improvements/)

[Data syncs](https://docs.wpvip.com/technical-references/vip-dashboard/data-sync/)(
production -> child env) will now run `wp vip data-cleanup datasync` directly inline
during the sync job. This happens both before cron is re-enabled and before maintenance
mode is lifted, helping better ensure the the cleanup hooks have run before any 
requests hit the application. A new hook has been introduced to perform actions 
during this cleanup: `vip_datasync_cleanup` (note that `vip_go_migration_cleanup`
still runs, though there are plans to deprecate in the future).

[SQL Imports](https://docs.wpvip.com/how-tos/migrate-content-databases/) (any env)
will also run a similar `wp vip data-cleanup sql-import` directly inline as well.
There is a new WP hook that can be used to perform actions during this cleanup: `
vip_sqlimport_cleanup`.

Alongside those new cleanup processes, the WP options below are backed up before
a data sync or SQL import takes place, then restored afterwards. The main reasoning
behind this is to prevent production environments from sharing this data with their
child environments, as they need to remain unique per environment.

    ```wp-block-syntaxhighlighter-code
        'jetpack_options',
        'jetpack_private_options',
        'vaultpress',
        'vip_jetpack_connection_pilot_heartbeat',
        'wordpress_api_key',
        'vip_search_index_versions',
        'vip_search_global_index_versions',
    ```