Websites and WordPress
Files, databases, configuration, PHP requirements, certificates, redirects, scheduled jobs, and the DNS change that puts the tested copy into production. Compare WordPress hosting if the destination is Shared Hosting.
Hosting migrations
Move to DotMoose with a tested cutover plan.
Migration help for websites, WordPress, email, VPS workloads, domains, and backup jobs.
Shared Hosting promotion
Free assisted website migration for qualifying new Shared Hosting customers.
Qualifying new Starter, Plus and Pro customers can have one standard website migration assisted by DotMoose. Enter 3MONTHS80 at checkout if you also want the separate 80%-off promotion. Complex multi-site, mailbox-heavy or custom application moves are scoped before we promise a cutover.
See hosting plansNo forced registrar move
Your domain can stay where it is.
We can migrate hosting without requiring a registrar transfer. DNS can change only after the destination is ready.
What we move
Bring the service you already run.
Mailbox moves are planned separately from the website so MX, SPF, DKIM, DMARC, account data, forwarding, and delivery testing are accounted for during cutover.
VPS workloads
Applications, services, databases, users, scheduled jobs, firewall requirements, ports, storage, certificates, and network dependencies can be rebuilt or copied onto a DotMoose VPS.
Domains
A registrar transfer can happen independently from hosting. Keep nameservers and DNS stable when the goal is only to move domain registration management.
Backup jobs
Existing backup software can be pointed at DotMoose SFTP storage after credentials, paths, capacity, transfer performance, and a real restore are tested.
Rollback
Keep the old environment available long enough to verify traffic, data, email, scheduled work, certificates, and customer-facing transactions on the new service.
Cutover
Copy first. Switch second.
Keep the old service available while the new copy is built and tested. Change DNS only after the destination is ready, then complete the final sync and verify the live service.
Inventory
Confirm websites, databases, mailboxes, DNS records, storage, runtimes, software, scheduled jobs, external services, and the access available at the source.
Copy and test
Build the destination, transfer data, match required software, and exercise the important customer paths before changing public traffic.
Final sync and observe
Reduce the change window, copy what changed, cut over only the required DNS, and watch logs, mail, forms, logins, orders, jobs, and resource use before retiring the source.
Switching providers
Start with the host you use today.
Provider accounts often combine hosting, domains, DNS, email and add-ons differently. These guides keep those dependencies visible before anything is cancelled or redirected.
01
Move from HostPapa
Inventory the HostPapa services in use and plan what moves to DotMoose versus what can stay in place.
02Move from Web Hosting Canada (WHC)
Separate hosting, mail, DNS, domain and server settings before choosing the destination.
03Move from GoDaddy
Map the GoDaddy products responsible for the site, WordPress, email, DNS and domain registration before cutover.
04Move from Hostinger
Plan website files, databases, mail, DNS, scheduled work and settings that may not transfer directly.
05Move from Bluehost
Prepare and test the destination before switching DNS or closing the old hosting account.
06Move from SiteGround
Account for application, database, mail, DNS, caching, cron, TLS and backup dependencies.
Migration guides
Know the sequence before the maintenance window.
WordPress
Move a WordPress site to a new host
Prepare the destination first, copy the site, test it, synchronize changes and then switch traffic.
WebsiteMove web hosting without downtime
Inventory, destination testing, data synchronization, DNS changes and keeping a rollback path.
DomainsDomain transfer checklist
Move registrar management without accidentally moving or breaking the services using the domain.
VPSMove a VPS to Canadian hosting
Inventory the server, copy it safely, test the destination, cut traffic over and preserve a rollback plan.
Can you migrate from another shared host?
Yes. Send the current control panel or provider, website count, storage used, email requirements, domain/DNS setup, runtime versions, and the access you have.
Can you migrate a VPS?
Yes. We first inventory the operating system, services, ports, storage, databases, scheduled jobs, users, certificates, and IP/DNS dependencies, then choose a copy or rebuild approach.
Does the domain have to transfer at the same time?
No. Hosting and domain registration are separate. The site can move first while the domain remains with its current registrar, and a registrar transfer can happen without changing nameservers.
How much downtime is required?
It depends on the workload. Many website moves can be prepared before DNS changes, while stateful applications or large databases may need a defined final-sync or maintenance window.
Start the move
Send us the current setup.
Include the provider, platform, storage used, domains, email, software stack, and what you want to improve.