What needs to move
Check moving a website to DotMoose with the destination tested before DNS changes, then synchronizing changing data and keeping the old service available until traffic and application behavior are verified.
Site migration Canada
Transfer files and databases, test forms and logins, then change DNS. Keep a way back until the new site 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 website to DotMoose with the destination tested before DNS changes, then synchronizing changing data and keeping the old service available until traffic and application behavior are verified.
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 site move works in a set order. Copy files and database to the destination, test the site there on a temporary address or hosts entry, fix what the test exposes, then change DNS. Testing first means visitors never see the broken version of the new home.
Changing data needs a final sync at cutover. Orders, comments, form entries, and new uploads created on the old site after the first copy must move again in a short final pass. Keep the old service available until traffic and application behaviour are verified on the destination.
Drop the DNS TTL to 300 seconds a day before cutover. Short records make the switch and any rollback take minutes, not hours.
Copy MX, SPF, DKIM, and DMARC records into the new zone before the switch. Mail breaks quietly when records are rebuilt from memory.
Test a login, a form submission, a checkout or booking, and outbound mail on the destination. A homepage that loads proves very little.
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.