Dragon Migrate - Site Migration, Database Backup & Search Replace
| 开发者 | dragoncoreltd |
|---|---|
| 更新时间 | 2026年10月10日 10:26 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Database Export - Streamed, gzipped SQL exports with table selection
- Database Import - Resumable imports that pick up where they left off
- Serialization-Safe Search & Replace - Handles nested serialization, Gutenberg block attributes and Elementor data correctly
- Full-Site Archive - Database plus uploads, themes and plugins in a single zip to download and keep (unpacked by hand; the database part imports from the Import tab)
- Backup & Restore - One-click snapshot before a risky change, and a way back
- Dry Run - See exactly what will be replaced before anything is written
- Migration Profiles - Save a configuration and re-run it as often as you need
- WP-CLI -
wp dragon-migrate exportandwp dragon-migrate find-replace - Resumable Everything - Row-offset cursors resume mid-table, even on a two-million-row table
安装:
- Upload the
dragon-migratefolder to/wp-content/plugins/ - Activate the plugin through the Plugins menu in WordPress
- Go to Tools > Migrate
屏幕截图:
常见问题:
Will this break my page builder content?
No. Search and replace unserializes data before replacing, then reserializes it. Elementor data, which stores JSON with escaped slashes, is handled specifically.
My host has a 30-second timeout. Will migrations finish?
Yes. Jobs run in small batches that are sized dynamically from how long the previous batch took and how much memory it used. A job resumes from its exact cursor position on the next tick.
Where are export files stored?
In a randomly named directory inside your uploads folder, protected from direct access. Downloads are served through an authenticated endpoint, so the raw file path is never exposed.
How do I move WordPress to a new domain?
Export with Find set to your old URL and Replace set to the new one, then import the file on the new site. The search-replace is serialization-safe, so widgets, theme settings and page builder layouts survive the move. Dragon Migrate moves the database. Copy your files (uploads, themes and plugins) yourself over SFTP or your host's file manager.
Can I restore a full-site archive?
Not from the plugin. A full-site archive is a zip you download and keep. To move a site with one, unzip it on your computer, upload the uploads, themes and plugins folders into wp-content on the new host over SFTP, then, on a WordPress install there with Dragon Migrate active and the same table prefix, place the database.sql.gz file from the zip in the migration folder and import it from the Import tab, with Find and Replace set to the old and new site addresses. Dragon Migrate imports the database part; it does not unpack or restore the files.
Why did a plain SQL search and replace break my site?
WordPress stores many settings as serialized PHP strings that record each value's exact length. Editing them with a raw text replace corrupts those lengths, and WordPress silently discards the data. Dragon Migrate decodes values first, replaces inside them, and re-encodes them correctly.
Can I undo a migration?
Yes. A backup is taken automatically before every import and restore, and you can take one manually before any risky change. Restoring can itself be undone, because the current state is backed up first.
Is there a file size limit?
The plugin imposes no limit. Exports stream to disk in batches and imports resume from their exact position, so large databases finish on ordinary shared hosting. To import, place the file in the migration folder shown on the Import tab over SFTP or your host's file manager; files are not uploaded through the browser, which fails for large files on most shared hosting.
Does it support multisite?
Not in this version.
更新日志:
- Removed the Pro tab, the Upgrade to Pro link and the Pro note from the plugin's screens.
- Corrected the FAQ and the Archive tab: a full-site archive is a download you unpack and upload by hand. Dragon Migrate imports its database part from the Import tab and does not restore the files.
- The directory listing is titled "Site Migration" in place of a name that used the word WordPress.
- Every admin action and background step checks its security token and your permission itself. Exports, imports, backups and archives work as before.
- File names and search and replace values are still used exactly as entered, including dump files copied in over SFTP.
- Fixed: malformed requests no longer write PHP warnings to the debug log.
- Fixed: uninstall deletes data only when the opt-in is clearly on (1, true, yes or on), not for a value set to "false" or "no".
- Imports load into working tables and switch them in with one rename, so visitors never see a half-imported site and an interrupted import leaves the site untouched. Dumps that cannot be switched safely (for example with foreign keys) use the previous method.
- Large mysqldump files import quickly: each step reads only new data and stops within a time limit.
- Backup retention applies as each backup finishes, backups in use are never deleted or offered for restore, and backups are ordered by when they were taken.
- Cancel is honoured right up to the final switch.
- Fixed: an import from another site keeps this site's own Dragon Migrate settings and backup folder.
- Fixed: the site stays reachable between import steps.
- Database dumps from mysqldump and MariaDB import cleanly.
- Find and replace reports rows it could not write, and finished exports show a download link.
- Every screen, email and alert is now translatable, so community translations from translate.wordpress.org cover the whole plugin. Counts use proper plural forms, and numbers and dates follow your site's language.
- Job progress shows its unit (rows, files or megabytes).
- Fixed: the pull form's "sends to" line updated the wrong side when you picked a connection.
- An "Upgrade to Pro" link on the Plugins screen, a one-line pointer at the foot of the plugin's own screens, and a single dismissible note once the plugin has done its job. All three disappear when the Pro add-on is active; nothing in the free plugin is locked or changed.
- The Pro tab now links to the Dragon Migrate Pro page.
- Fixed: a full-site archive whose file list could not be written to disk (a full disk, or a manifest that could not be opened) now fails with a clear error instead of reporting a complete archive with files missing.
- Fixed: a file whose manifest entry could not be read is now counted in the "files could not be read" total and named in the job log, rather than being left out of the archive silently.
- Fixed: a file whose name cannot be listed is counted and named too.
- Improved: search and replace jobs can opt in to rewriting every form a site URL takes in content (the opposite scheme, protocol-relative links, and URL-encoded copies). Off by default - the Find/Replace screen matches exactly what you type, as before. Dragon Migrate Pro 1.0.10 uses it for push and pull.
- Asks for a WordPress.org review once, only on the Migrate screen and only after a job has completed. "Maybe later" snoozes it for a month and "No thanks" is permanent.
- New
dragonmigrate_job_completeaction fires when an export, import, archive or find-replace job finishes. - Listing title, description and tags now say what the plugin does, so it is easier to find in the plugin directory.
- Fixed: large imports now finish even when the imported database replaces your login session mid-import - each migration carries its own tick credential, and you are told to log back in afterwards.
- Fixed: importing dumps made of many small statements (phpMyAdmin exports, mysqldump --skip-extended-insert) no longer fails part-way.
- Fixed: the import and restore progress bar now actually moves - progress is measured in bytes of the dump applied.
- Fixed: a batch boundary landing inside quoted text could drop spaces from imported content; statement splitting is now byte-exact and comment handling no longer fuses tokens.
- Fixed: search and replace only touches genuinely textual columns - numbers, dates, and binary data are no longer rewritten as text - and composite-key tables such as term relationships are now walked instead of skipped.
- Fixed: search and replace no longer rewrites rows the search never matched, leaves custom-serialized (C:) payloads untouched, and reports any matching values it had to skip.
- Fixed: exports order rows deterministically on tables without a simple primary key, exclude generated columns, and exclude database views (views and triggers are announced in the job log as not included).
- Fixed: importing a dump with a different table prefix now says so clearly instead of reporting a success that changed nothing.
- Fixed: abandoned jobs are cleaned up properly - partial files no longer linger looking like real backups, and retention pruning can no longer delete a backup a queued restore is about to use.
- Fixed: full-disk conditions during export, archive, and decompression are detected instead of producing silently truncated files.
- Fixed: the Profiles tab's Use button now applies the profile on the Export tab.
- Fixed: WP-CLI plain-SQL export works via the new --uncompressed flag, and an empty table selection is refused instead of claiming success.
- Hardened: archives skip symbolic links entirely and report every file they had to leave out; the storage directory's .htaccess covers Apache 2.4.
- Security hardening: blocked PHP object injection via serialization-safe replace.
- Housekeeping: refreshed the shared admin design kit.
- Compatibility: tested up to WordPress 7.1.
- Housekeeping: job-history pruning queries now use WordPress's identifier placeholder.
- Safety: deleting a backup or profile now asks for confirmation naming the exact file.
- Housekeeping: finished job history is pruned after 60 days.
- Polish: the multisite notice only appears where it is relevant.
- Data safety: uninstalling the plugin no longer deletes its data unless you explicitly opt in first - a reinstall now picks up exactly where you left off.
- New look: the Dragon design system arrives - a consistent Dragon Core header, cleaner tables, and unified status colours. Purely visual; no behaviour changes.
- Renamed all option, hook, function and constant prefixes to the unique
dragonmigrate_/DRAGONMIGRATE_prefix. Existing settings, backups and scheduled tasks are migrated automatically on update.
- Initial release