MigraSync » WordPress to WordPress Migration: Clone to a New Host

Moving WordPress to a new hosting provider — whether your current host is slow, your renewal price jumped, or you are launching on a production domain after building on staging — can feel daunting. The fear is always the same: broken images, missing plugins, login loops, and URLs that still point to the old server.

Manual migrations involving transferring every file via FTP, exporting SQL, and running search-replace scripts work until they do not. One wrong path in wp-config.php or a half-finished database replace can take your site offline for hours.

This guide walks you through cloning WordPress to a new host with MigraSync using an encrypted cloud backup on your source site and a 1-click restore on your destination. URLs are rewritten automatically, and the job runs entirely in the background so you are not stuck watching a progress bar.

Time Estimate: 45–120 minutes of active setup (plus backup/restore runtime, which scales with site size).
What You Will Need:
- Admin access to your source WordPress site (current host)
- A destination WordPress install on the new host (fresh or empty)
- A MigraSync account with an Essential or Pro backup plan (backup trial available)
- Your Master Vault Key from the source backup (save it before you start)

Overview: How WP-to-WP Cloning Works

MigraSync does not use giant export ZIP files sitting on your server. Instead, it securely bridges the two environments through a streamlined cloud workflow:

1.Source Site Configuration:Steps 1 – 3.

Install the MigraSync plugin on your current live site, connect your unique API account key, and generate a secure Master Vault Key to execute a manual backup directly to the encrypted cloud vault.

2.Destination Site Prep:Steps 4 – 5.

Set up a clean WordPress environment on your new hosting platform, install the MigraSync plugin, and bind it using the exact same account API key.

3.Execute Cloud Restore:Step 6.

Launch the WP Restore engine on the new host, select the “Restore to another URL” protocol, input your Master Vault Key, and let the cloud system process database entries and re-write URLs.

When Manual / DIY Migration Breaks

Before jumping into the step-by-step setup, it helps to understand why traditional manual or DIY hosting moves frequently run into issues:

DIY Approach	Common Failure Point
FTP copy of `wp-content` only	The database still points to old URLs, resulting in broken internal paths and media links.
phpMyAdmin export + manual import	Serialized data breaks when you attempt a standard global text search-and-replace for URLs.
All-in-One WP Migration plugin	Runs into file upload size limits on shared hosting or encounters server timeouts on large media libraries.
Host “free migration” service	Frequently skips custom database tables, cron jobs, or specialized plugin configurations.
Manual `wp search-replace` CLI	Misses URLs buried inside widgets, theme modification arrays, or serialized option rows.

MigraSync’s restore engine naturally handles serialized WordPress data and runs a structured URL rewrite post-import. Backups stream directly to the MigraSync Managed Cloud using AES-256 encryption rather than generating multi-gigabyte ZIP files that clog your server’s local disk space.

Step 1: Prepare Your Destination Host

Set up WordPress on your new host before running the restore process.

Minimum System Requirements (Both Sites)

PHP 8.1+ with common extensions compiled (mysqli, curl, zip, xml)
HTTPS active on the destination with a valid SSL certificate
Available disk space tracking at least 2× your current total site size
A MySQL or MariaDB database instance (ensure it is empty or disposable, as the restore process completely overwrites it)

Install a fresh instance of WordPress using your new host’s automated setup tool. You only need a working administrator login to access the dashboard—MigraSync will replace the placeholder database tables entirely during the restore phase.

Pro Tip: Use a temporary URL or your host’s preview domain to verify the cloned site’s layout and functionality before pointing your live public DNS records over.

Step 2: Create Your MigraSync Account

Head over to the MigraSync account registration portal.
Create your account credentials and verify your profile via the confirmation email.
Log in to access your central MigraSync Dashboard.

Selecting a Plan Tier for Cloning Capabilities

Plan Tier	Cloning Support
Backup Trial	Test out basic backup and restore functionality on a small scale.
Essential	Full secure cloud backup pipelines along with comprehensive 1-click restore mechanics.
Pro	Offers larger cloud storage allocations, automated daily backups, and advanced retention rules.

Note: Executing a full WP Restore sequence requires an active Essential or Pro subscription.

Step 3: Install MigraSync on the Source Site

Download the latest version of the MigraSync plugin from your account dashboard.
Navigate to Plugins → Add New → Upload Plugin.
Choose the downloaded .zip file, click Install Now, and then click Activate.

Step 4: Connect Your API Key (Source Site)

Open MigraSync → General Settings → Status.
Paste your active API key directly from your central MigraSync cloud dashboard.
Click Save & Validate.

Confirm that your account plan displays as active and validated before moving forward.

Step 5: Set Up Your Master Vault Key

The Master Vault Key encrypts your site’s database payload before it leaves your server.

Critical Warning: If you lose this key, encrypted backups cannot be recovered or restored under any circumstances.

Navigate to MigraSync → WP Backup.
Under Step 1 / 4, expand the Master Vault Key settings drawer.
Click Generate Key (or enter your pre-existing key if you are already using MigraSync backups).
Click Update / Save Key.
Click Download Sheet to save your migrasync-recovery-sheet.html file somewhere secure (such as a password manager or an offline hardware backup drive).

Step 6: Run a Manual Backup on the Source Site

For a one-time hosting migration, skip automated schedules and trigger a manual backup pool.

Executing the Backup Wizard

Step 1 / 4: Verify that your Master Vault Key is saved. Select Manual / Instant Backup and click Next.
Step 2 / 4: Select your backup scope. For a complete host-to-host clone, check all boxes: Database, Media, Plugins, and Themes. Click Next.
Step 3 / 4: Establish your retention policy (how long the backup stays in cloud storage). For a standard migration, 30 days is typically plenty of time. Click Next.
Step 4 / 4: Review your selections, check the data processing agreement box, and click Start Backup.
Step 5 / 4 (Progress): The data pipeline is now running. You can safely close the browser tab; the processes run asynchronously in the background.

Once finished, the completed job will appear in your Recent Backup Jobs log. Note the exact execution timestamp, as you will select this specific restore point on your destination site.

Step 7: Install MigraSync on the Destination Site

Now, move over to the administrative panel on your new host:

Install the same MigraSync plugin file (Plugins → Add New → Upload Plugin).
Activate the plugin.
Navigate to MigraSync → General Settings → Status.
Paste the exact same account API key you utilized on your source site.
Click Save & Validate.

Once authorized, your cloud backups from the original server will instantly populate within the destination interface.

Step 8: Run WP Restore — Clone to the New URL

Open MigraSync → WP Restore on your new host’s dashboard.

Phase 1: Destination Mapping

Select Restore to another URL. This tells the engine that you are performing a cloning run (taking data from oldsite.com and restoring it to newsite.com). The engine will automatically:

Rewrite siteurl and home values inside the database options tables.
Update post elements, page blocks, internal link paths, GUID strings, meta fields, and comment loops.
Flush your structural permalinks and reset configuration parameters within your .htaccess file.

Click Next.

Phase 2: Select Your Restore Point

Click Refresh List to sync cloud storage states.
Select the completed backup you generated on your source site by matching the timestamp and asset scopes.
Click Next.

Phase 3: Choose What to Restore

Ensure you configure your asset deployment strategy cleanly:

Database (Required): Automatically selected to overwrite existing destination tables.
Media Library (Uploads): Check this to pull down and extract your complete wp-content/uploads directories.
Plugins & Themes (Sidecar Packages): Check these to copy your plugin and theme files into a secure sidecar folder on your new host. This keeps them ready for manual installation and avoids activation conflicts mid-restore.

Click Next.

Phase 4: Security Decryption & Execution

Enter your Master Vault Key (retrieved from your source site settings, secure notes, or your downloaded recovery sheet).
Click Next, review the override warnings, and confirm to Start Restore.

Phase 5: Progress Monitoring

The wizard displays live progress bars tracking file downloads, SQL structure building, and media extractions. You can safely close the tab. The restoration pipeline runs completely server-side. Once finalized, the screen will reload to confirm completion.

Step 9: Install Plugins and Themes (Sidecar)

Once the database and media arrays are fully restored to the file system:

Navigate to Plugins → Installed Plugins (or Add New). MigraSync holds your source plugin files securely in a server sidecar directory to prevent automatic initialization conflicts.
Install and activate your required plugins from this local staging folder.
Navigate to Appearance → Themes, install your theme from the sidecar folder, and click Activate.
Re-enter premium plugin license validation keys on the new host if prompted.

Step 10: Verify the Clone Before DNS Cutover

Always test your site thoroughly on the destination or staging URL before updating your live public domain mapping:

[ ] Confirm the homepage resolves cleanly with all styling and fonts intact.
[ ] Click into various posts and pages to verify structural formatting.
[ ] Inspect image elements to ensure their src attributes pull from the new host rather than referencing the old server.
[ ] Verify that you can access the dashboard via /wp-admin using your source site’s original administrator credentials.
[ ] Check Settings → General to ensure both the WordPress Address and Site Address correctly reflect the destination URL.

Flushing Permalinks

If you experience unexpected 404 errors when clicking internal links, navigate to Settings → Permalinks and click Save Changes without editing any fields. This simple action forces WordPress to regenerate its core routing rules.

Step 11: Point Your Domain to the New Host

When you are confident that the cloned site is running smoothly:

Lower your DNS TTL (Time to Live) to 300 seconds roughly 24–48 hours before cutover to ensure fast propagation.
Update your domain’s A Record pointing to the new host’s IP address (or transition your nameservers completely) within your registrar account.
Verify that your SSL certificate is fully active and functional on the new host.
Keep your old hosting account active for at least 48–72 hours as a safety fallback while global DNS propagation finishes.

Step 12: Post-Migration Checklist

[ ] Re-save your permalink choices on the live domain setup.
[ ] Update or add your new site properties inside Google Search Console if your root URL changed.
[ ] Submit your updated XML sitemap to ensure search engine crawlers map the new host efficiently.
[ ] Confirm that your analytics tracking tags (such as GA4) are collecting data normally.
[ ] Re-verify transactional API keys for tools like payment processors, CDN networks, or external email dispatch plugins.

Optional: Enable Auto Backup on the New Host

Now that your site is settled in its new home, set up automated backup protection:

On your destination site dashboard, navigate to MigraSync → WP Backup.
Select the Auto Backup option.
Configure your desired frequency (daily, weekly, or monthly) along with your retention preferences.
Click Save Schedule.

Troubleshooting Common Issues

The Interface Displays a “Connection Required” Alert on Restore

Navigate to MigraSync → General Settings → Status and verify that your destination site is successfully validated using the exact same API key as your source environment.

The Backup List Appears Empty on the Destination Site

Verify that the original backup job finished successfully on your source site. Click Refresh List on Step 2 of the restore wizard to manually pull down recent cloud states.

The Restore Fails at the Master Vault Key Phase

The security key must exactly match the original alphanumeric string used when the backup was encrypted on the source site. Refer to your downloaded Recovery Sheet instead of trying to generate a new key on the fly.

You Are Stuck in a Login Redirect Loop After Restore

This typically indicates a URL value mismatch inside your core tables. Verify your settings or check your wp-config.php file to ensure there are no hardcoded WP_HOME or WP_SITEURL rules overriding your new environment parameters.

Plugins Are Missing From the Dashboard Post-Restore

This is intended behavior. Plugins are delivered safely into a server sidecar package to prevent breaking your live administrative environment during file extractions. Simply navigate to your plugins page to complete their activation manually.

WP-to-WP Clone vs. Other Migration Tools

Migration Approach	Best Suited For	Key Limitations
MigraSync Backup & Restore	Full-site clones to new hosts or domains, utilizing encrypted cloud delivery and background processing.	Requires an active Essential or Pro tier subscription plan.
All-in-One WP Migration	Quick moves for very small web properties.	Frequently encounters upload size limits or timeouts on large media portfolios.
Manual FTP + phpMyAdmin	Advanced developers who are highly comfortable working directly with SQL structures.	High risk of breaking serialized arrays during text-based URL search-and-replace actions.
Host Migration Services	Completely hands-off setups for highly basic, standard layouts.	Highly variable quality; automated scripts may drop custom tables or complex configurations.

What MigraSync Handles vs. Your Responsibilities

Automated Tasks	Manual Responsibilities
Running encrypted cloud backups directly from your source host	Choosing, provisioning, and setting up your new web hosting space
Executing seamless database table imports on the destination	Handling DNS namespace cutovers at your domain registrar
Completely re-writing internal URLs across all database tables	Activating themes and plugins directly from sidecar packages
Unpacking and organizing media assets into your uploads folder	Re-entering premium license keys or re-verifying custom APIs
Processing background backup and restore queues asynchronously	Updating search engine configurations and web analytics trackers

Frequently Asked Questions

How long does a WordPress to WordPress hosting migration take?

For a small site under 500 MB, the entire backup and restore sequence usually wraps up within 30–60 minutes. For massive sites with gigabytes of media assets, the data transfer can take several hours. Because MigraSync processes everything server-side in the background, you can safely close your browser tab without interrupting the job.

Can I clone my WordPress site to a completely different domain name?

Yes. When running the WP Restore wizard on your destination site, make sure to select Restore to another URL. MigraSync’s engine will automatically scan your database and cleanly rewrite all instances of your old URL (e.g., https://www.oldsite.com) to match your new domain topology (e.g., https://www.newsite.com) without breaking serialized data.

Do I need to have the MigraSync plugin installed on both servers?

Yes. The plugin acts as the secure endpoint on both sides of the bridge. You need it active on your source site to package and encrypt your data up to the cloud vault, and you need it active on your fresh destination site to pull down and deploy the assets. Remember to use the exact same account API key on both sites.

What happens if I lose my Master Vault Key?

Because MigraSync uses a strict Zero-Knowledge encryption protocol to secure your database payloads, your Master Vault Key is never stored on our central servers. If you lose this key and do not have your downloaded Recovery Sheet handy, the encrypted backup file cannot be decrypted or restored by anyone. Always save a copy in a secure password manager before running a backup.

Will my live website experience downtime during the migration?

No. Your source website remains completely online and accessible to your visitors while the background backup pipeline runs. By setting up your cloned environment on a temporary or staging URL at your new host first, you can fully test and verify the migration before modifying your live DNS records—resulting in a seamless, near-zero-downtime transition.

Does the database restore include WooCommerce orders and custom tables?

Yes. The database migration engine targets and packages the entire SQL database structure. This includes all core WordPress tables, custom plugin tables, user profiles, metadata, and active WooCommerce order logs. We highly recommend putting your store into maintenance mode right before triggering the final backup pass to ensure no new orders are placed mid-transit.