This article is a checklist of everything you should prepare before migrating your WordPress site to Web60.
1. Check your WordPress version
Your site must be running WordPress 5.0 or later. Log in to your current WordPress dashboard and check the version at the bottom of any admin page, or go to Dashboard then Updates.
If you are on an older version, update WordPress at your current host before starting the migration.
2. Note your active plugins
Make a list of all active plugins on your current site. Go to Plugins then Installed Plugins and note which ones are active.
This helps you verify after migration that everything is still installed and activated. Some plugins may have licence keys tied to your old domain that need to be updated after migration.
3. Lower your DNS TTL
At your current domain registrar or DNS provider, lower the TTL (Time To Live) on your DNS records to 300 seconds. Do this at least 24 hours before you plan to switch DNS to Web60.
A low TTL means DNS changes propagate faster when you make the cutover. If you skip this step, some visitors may continue seeing your old site for up to 48 hours after the switch.
4. Create a full backup at your current host
Before you change anything, create a complete backup of your site at your current hosting provider. This is your safety net. If anything goes wrong during migration, you can restore the backup at your current host and try again.
Make sure the backup includes both WordPress files and the MySQL database.
5. Note your email configuration
This is the step most people overlook. Check your current DNS records and note:
- MX records: these tell email where to go. If you use Google Workspace, Microsoft 365, or another email provider, your MX records must be preserved.
- SPF record: this helps prevent your emails being marked as spam.
- DMARC record: this provides email authentication policy.
After migration, you will need to set these records up in the Web60 portal. If email DNS is not configured correctly after the cutover, your email will stop working.
6. Choose your migration method
Two options are available:
- Web60 Migration plugin (recommended): install the plugin on your current site, and it handles the file and database transfer to Web60 automatically.
- Manual migration: export your database using phpMyAdmin or mysqldump, download your files via SFTP or file manager, then upload everything to Web60 using SFTP and import the database.
7. Confirm access to database export tools
If you are migrating manually, make sure you can access your current host's database export tools before you start:
- phpMyAdmin: most hosting control panels (cPanel, Plesk) include this.
- SSH with mysqldump: if your host provides SSH access, you can export the database from the command line.
If you cannot access either, use the Web60 Migration plugin instead.
FAQ
Q: What WordPress version do I need to migrate to Web60?
A: Your site must be running WordPress 5.0 or later. If you are on an older version, update WordPress at your current host before migrating.
Q: Will my email be affected by the migration?
A: It can be, if DNS is not handled carefully. Note your current MX records before migrating and make sure they are set up correctly in Web60 after the DNS cutover.
Q: What is the easiest way to migrate?
A: The Web60 Migration plugin is the recommended method. It handles file transfer and database migration automatically. Manual migration via SFTP and database export is also supported.
Frequently asked questions
What WordPress version do I need to migrate to Web60?
Your site must be running WordPress 5.0 or later. If you are on an older version, update WordPress at your current host before migrating.
Will my email be affected by the migration?
It can be, if DNS is not handled carefully. Note your current MX records before migrating and make sure they are set up correctly in Web60 after the DNS cutover.
What is the easiest way to migrate?
The Web60 Migration plugin is the recommended method. It handles file transfer and database migration automatically. Manual migration via SFTP and database export is also supported.
Last updated: 4 April 2026