What needs to move
Check moving a conventional website into Canada while preserving files, database state, email dependencies, DNS, TLS, redirects, cron jobs, and a rollback path.
Move hosting Canada
Plan the website copy, destination tests and DNS change together. Keep the old service available until the move is checked.
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 a conventional website into Canada while preserving files, database state, email dependencies, DNS, TLS, redirects, cron jobs, and a rollback path.
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
Most shared hosting accounts hold the site in a home directory, with the database exported through the panel and mail stored in Maildir folders under each account. Export the files, dump each database as SQL, and list every mailbox, forwarder and cron job before anything is copied to the new Canadian account.
The failures in this move are usually small and quiet. A cron job points at a path that changed, a contact form sends through a mail account that was never recreated, or an addon domain loses its document root. Test the copied site on a temporary address, send a form, and check each mailbox before DNS moves.
Save every record type from the current zone before the move, including MX, SPF, DKIM selectors, DMARC and any verification TXT records. The new zone is built from that capture.
List addresses, aliases, forwarders and autoresponders at the old host. Mailboxes that exist only in a mail client get missed when the account list is skipped.
The source account keeps serving traffic and mail until the Canadian copy passes its checks. DNS changes last, after forms, logins and mail flow are proven.
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.