Quick Migrate

Find & Replace rewrites your live database, so always click Preview first. The preview changes nothing and shows the rows that would change. On production sites, also choose a pre-flight backup so you have a rollback file. The replacement itself runs on copies of your tables, and the live tables are only swapped once every copy is verified.

Yes. Quick Migratewalks serialized PHP structures and rewrites their string lengths. The stored value stays valid instead of breaking, as it would after a plain text replacement.

The database as database-<timestamp>.sql (unless you left the database out), the file components you selected and a manifest.json export summary. The archive is named migration-export-<date-time>.zip.

Every file component is unticked by default, so an export is database-only until you opt in. Tick the Database card or at least one file component.

In a spinx-quick-migrate folder inside your uploads directory (normally wp-content/uploads/spinx-quick-migrate/). The folder is created the first time you run an export or backup and is protected against direct web access. Files are downloaded only through a secure link that requires you to be logged in with permission to use the plugin, and every file name includes a random token. Exports and backups are deleted from the server as soon as they have been downloaded. Anything left behind, such as a find & replace pre-flight backup or a file created with WP-CLI, is removed automatically after 24 hours.

The job's state is stored on the server. When you reopen SPINX Quick Migrate, the progress popup reattaches to the running export, backup or Find & Replace and continues. A paused job can be resumed within one hour.

Go to Settings and lower Max data per step (default 6 MB) or Rows per SQL batch (default 2,000). Each step then does less work, which helps on hosts with short PHP time limits. You can also run the job from WP-CLI.

Yes. With WP-CLI installed you get wp spinx-qm export, wp spinx-qm backup, wp spinx-qm find-replace and wp spinx-qm profile. For example:

• wp spinx-qm export --files --tables=wp_posts,wp_options
• wp spinx-qm backup --gzip
• wp spinx-qm find-replace --url-from=https://old.test --url-to=https://new.test --dry-run
• wp spinx-qm profile run "Nightly export"

The plugin can be activated network-wide and installs its tables on every site, including sites created later. On multisite, only Super Admins can use it, because exports, backups and find & replace can reach network-wide tables such as users. Each site keeps its own exports, backups and profiles. Migrating a subsite into a standalone install, or the reverse, is not supported.

By default, Quick Migratetrusts only REMOTE_ADDR. To use forwarded headers, add: add_filter( 'spinxqm_trust_proxy', '__return_true' ); Only enable this if you really are behind a proxy that strips forged headers.

Require a custom capability instead of manage_options: add_filter( 'spinxqm_required_cap', function () { return 'spinxqm_manage'; } ); Then give spinxqm_manage to every role that should use the plugin, including Administrator, with a role editor plugin or get_role( 'editor' )->add_cap( 'spinxqm_manage' );. Only grant it to people you trust: the plugin can export and rewrite the whole database.

No. Deactivating clears the plugin's scheduled tasks and never deletes user data.

Delete the plugin from the Plugins screen. Uninstalling removes its settings, its operation-history and audit-log tables, any leftover job records and temporary find & replace tables, and the spinx-quick-migrate storage folder (including any exports or backups still in it) on every site of the network.

When you open a support request, please include:

• WordPress version
• PHP version
• The operation you ran (Export, Backup or Find & Replace) and its settings
• The error message shown in the progress popup, if any
• Steps to reproduce the issue