Requires the free Dragon Migrate.
Licence
Enter your licence key on the plugin's settings screen (keys are in your dragoncore.ltd dashboard). Keys are stored encrypted; one seat covers one site, and you can deactivate a site from the same screen to move the licence. Updates are delivered automatically to licensed sites. If the licence lapses, the plugin keeps working with every Pro feature on each activated site; what stops is new versions and support, and renewing restores both on the same key. Renewal reminders arrive by email about two weeks before the period ends.
Your licence belongs to the site it is activated on, and is kept when a transfer replaces that site's database - pushing staging over production does not hand production the staging licence, or leave it unlicensed.
Features
- Site-to-site push/pull - pair two sites with a key and move the database directly, serialization-safe with URL replacement. The old site's address is rewritten in every form it takes in content: as reported, with the opposite scheme (http:// links on a site that later moved to https://), protocol-relative (
//old-site.com/...), URL-encoded (inside query strings and oEmbed caches), and the JSON-escaped form of each. Leave Find/Replace empty on a pull and the other site's address becomes this one's. Needs Dragon Migrate 1.0.10 or later on the site doing the rewrite. Internationalised (non-ASCII) domains are converted to their DNS form before pairing, so they connect like any other. - File sync - uploads/themes/plugins between paired sites.
- Schedules - recurring migrations for staging refreshes.
Pairing
Generate a pairing key on the destination, paste it on the source. Keys are stored encrypted and transfers run over HTTPS.
Safety
Every transfer that replaces a database takes a restore point on the receiving site first, and refuses to start if that restore point cannot be made. If the transfer then fails part way through, the site is rolled back to it automatically - in both directions, whether you pushed to the site or pulled from another one. The restore points are ordinary backups and stay listed on the free plugin's Backups tab, so you can also go back by hand.
Paired sites don't need to run the exact same release - preflight checks that both ends speak the same transfer protocol, and ordinary updates don't change it, so transfers keep working while auto-updates roll out at different times (you'll see a note that the versions differ). A release that changes the protocol says so in its changelog; only then must both ends update together, and the transfer is refused before anything is sent until they have.
Scheduled transfers survive an incoming transfer: the schedule belongs to the site it was set up on, not to the database that arrives.
Uninstall
Deleting the plugin keeps all its data by default, so a reinstall picks up where you left off. To remove everything on uninstall, opt in first:
wp option update dragonmigratepro_delete_data_on_uninstall 1