What needs to move
Check moving WordPress with files, database, uploads, PHP/runtime compatibility, plugins, cron, mail, TLS, cache behavior, write synchronization, DNS cutover, and a tested rollback plan.
WordPress migration Canada
Move WordPress files and data with a plan for plugins, email and new orders. Test the destination before switching traffic.
Hosting options
Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →02Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
Check moving WordPress with files, database, uploads, PHP/runtime compatibility, plugins, cron, mail, TLS, cache behavior, write synchronization, DNS cutover, and a tested rollback plan.
Copy the site or application to the new host and test it privately. Check logins, forms, database writes, scheduled jobs, email and any external integrations.
Choose when to stop or synchronize new writes. Include orders, uploads and mail that arrived after the first copy. Avoid letting both systems accept independent changes.
Save the old DNS and routing settings. Switch traffic after the final tests, monitor the result and keep the old service until the agreed rollback period has passed.
Field guide
A WordPress move carries files, the database, and the uploads folder, and the three must agree. The database stores the site address, so URLs inside it need updating to the new domain or location with a tool that handles serialized data safely. A plain text replace corrupts those values.
Match the runtime before blaming the move. Check the PHP version and extensions on the destination against what the site runs now, and confirm plugins and the theme support them. After cutover, verify cron runs, mail sends, caching behaves, and permalinks resolve before calling the move done.
New posts, orders, and comments land on the old site until DNS settles. Run a final database sync after propagation or accept losing them.
Issue the certificate once DNS points at the destination, then force HTTPS and check for mixed content warnings in the browser console.
Keep the old hosting and the pre move database untouched for a week. A rollback is then a DNS change, not a rebuild.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.