What needs to move
Check leaving WHC by separating registrar/DNS ownership from website files, databases, mailboxes, cron jobs, certificates, and any server-specific configuration that needs a destination equivalent.
Migrate from WHC
Plan a move from WHC to DotMoose by separating website files, databases, mailboxes, DNS, domains and server-specific settings that need a destination equivalent.
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 leaving WHC by separating registrar/DNS ownership from website files, databases, mailboxes, cron jobs, certificates, and any server-specific configuration that needs a destination equivalent.
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
WHC accounts commonly combine cPanel hosting with domain registration and DNS in the same login. Export the site from cPanel as a full account backup plus separate database dumps, and export the DNS zone from the client area as its own record. Keeping the two exports separate matters because registration, DNS and hosting can move at different times.
Certificates and cron jobs are the quiet casualties in this move. The old certificate stays behind, scheduled tasks point at old paths, and mailboxes need recreating before stored mail can follow. Issue a fresh certificate at the destination during testing, rebuild each cron entry against the new paths, and confirm every mailbox opens before the nameservers change.
Download the DNS zone apart from the hosting backup. Compare it line by line with the zone the new host builds.
Note the PHP version, enabled extensions and any custom PHP settings in the old account. Match them at the destination before testing the site.
Request the new certificate while the site is still in private testing. HTTPS problems are easier to fix before visitors arrive.
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.