Clone WordPress to a new site (cross-URL restore)
MigraSync does not use a separate “clone” product. WP-to-WP migration = backup on the source site + WP Restore to another URL on the destination. MigraSync rewrites siteurl, home, and content URLs to the new hostname.
Use cases
- Move from shared hosting to a new provider
- Promote staging → production
- Change domain name while keeping content
Overview
Source site Destination site
───────────── ────────────────
1. Cloud backup → 3. Fresh WordPress + plugin
2. Same account API key → 4. WP Restore → another URL
Part A — Source site
- Install MigraSync Plugin and connect your API key.
- Set Master Vault Key.
- Run manual or scheduled backup to MigraSync Managed Cloud.
- Wait until Recent Backup Jobs shows Completed.
Part B — Destination site
- Install fresh WordPress on the new host/domain.
- Install MigraSync Plugin and connect the same account API key (same MigraSync customer).
- Open MigraSync → WP Restore.
- Choose Restore to another URL — MigraSync notes that URLs in the database will be rewritten to the current site hostname.
- Select the source backup point → scope → vault key → confirm restore.
Cross-URL notes (from the wizard)
- Permalinks and .htaccess may need a save on the destination after restore.
- Cloud backups tied to your account can be restored on any connected site with the same API key.
- DNS should point to the destination only when you are ready to go live.
DNS cutover checklist
- Lower TTL a day before cutover (optional).
- Complete restore on destination; test via hosts file or temporary URL if your host provides one.
- Update DNS A/AAAA records to the new server.
- Enable SSL on the new host.
- Verify redirects, login, and checkout.
Related
Related Articles
On this page