How to Migrate WordPress by Plesk Migrator

admin

2 months ago

How to Migrate WordPress by Plesk Migrator migration tutorial showing backup, transfer, verification, and DNS cutover checks

Plesk Migrator can move WordPress safely when it matches the source, destination, and risk level. This method is best for moving subscriptions, websites, databases, mail, and WordPress installs into Plesk-managed hosting.

Audience: Plesk admins, agencies, and hosting providers moving sites into a Plesk server. Before using this path, decide whether the move changes hosts, domains, DNS, email, PHP versions, database versions, cache layers, or business data. Those details matter more than the migration button itself.

Before migration

Check source platform support in the Plesk Migrator guide.
Confirm destination subscriptions, PHP versions, database versions, disk space, and mail settings.
Lower DNS TTL and plan email cutover.
Back up the source before migration starts.

Migration steps

Install or open Plesk Migrator on the destination Plesk server.
Connect to the source server.
Select the subscriptions or sites to migrate.
Run pre-migration checks and resolve warnings.
Start migration and review logs.
Preview the migrated WordPress site before DNS cutover.

Post-migration verification

Check WordPress Toolkit detection, SSL, PHP handler, database connection, uploads, forms, mail, cron jobs, and Plesk logs. Confirm old and new DNS behavior during propagation.

Also check server logs, PHP errors, WordPress Site Health, cache behavior, CDN routing, redirects, robots/indexing state, cron jobs, and whether a new backup job exists on the destination.

Migration risks

Unsupported source configurations may need manual cleanup.
Mail and DNS can be migrated with stale settings.
PHP handler or extension differences can break plugins after an otherwise successful move.

Rollback and cutover planning

Keep the old site online until the new site is proven. For stores, memberships, bookings, LMS sites, directories, and lead-generation sites, plan a final data freeze or sync so records do not split between servers. Keep DNS rollback notes, old-host access, and a verified backup until traffic and logs are stable.

Fix I.T. Phill recommendation

Use Plesk Migrator when it gives you the cleanest preview and rollback path. If the site makes money or stores customer records, treat the final cutover as a maintenance window, not a casual copy job.