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
Migration help for websites, WordPress, email, VPS workloads, domains, and backup jobs.
Rather start from your hosting company?
Step 1: Your current host
Choose a logo or search for your old host. We'll help you with the technical steps after you sign in.
No host selected yet
Type the company you pay for hosting. If you are unsure, we can help identify it from your website.
Choose your current hosting company. We will check the available transfer options after you sign in. Selecting a company does not start a transfer.
Choose what you have. Credentials are only requested after you sign in. We won't switch your live site without your approval.
Host names and logos are shown for identification only. DotMoose is not affiliated with these providers; available migration steps depend on your account.
We are checking each domain now. This takes about a minute. Nothing is copied or changed while we look.
Confirm each domain below. Only confirmed domains go ahead.
FOUND SO FAR
These are observations from the public Internet, not a complete list of your websites or private data.
Migration map
We checked one website address, not every service attached to the domain or hosting account. Other websites, subdomains, email, databases, scheduled tasks and applications may be missing. Nothing is ready to transfer or switch yet.
Next step
No password is asked for on this page. You sign in on the secure DotMoose page, and access to your old host is requested only after that.
The public check cannot see all your accounts, websites, subdomains or mailboxes. Continue to the secure client area to connect the old hosting account or provide a backup. We will verify everything before copying or switching traffic.
Observed publicly
Inferred
Access still needed
Automation
Cutover plan
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 plansWe can migrate hosting without requiring a registrar transfer. DNS can change only after the destination is ready.
What we move
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.
Mailbox moves are planned separately from the website so MX, SPF, DKIM, DMARC, account data, forwarding, and delivery testing are accounted for during cutover.
Applications, services, databases, users, scheduled jobs, firewall requirements, ports, storage, certificates, and network dependencies can be rebuilt or copied onto a DotMoose VPS.
A registrar transfer can happen independently from hosting. Keep nameservers and DNS stable when the goal is only to move domain registration management.
Existing backup software can be pointed at DotMoose SFTP storage after credentials, paths, capacity, transfer performance, and a real restore are tested.
Keep the old environment available long enough to verify traffic, data, email, scheduled work, certificates, and customer-facing transactions on the new service.
Cutover
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.
Confirm websites, databases, mailboxes, DNS records, storage, runtimes, software, scheduled jobs, external services, and the access available at the source.
Build the destination, transfer data, match required software, and exercise the important customer paths before changing public traffic.
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
Provider accounts often combine hosting, domains, DNS, email and add-ons differently. These guides keep those dependencies visible before anything is cancelled or redirected.
Inventory the HostPapa services in use and plan what moves to DotMoose versus what can stay in place.
02Separate hosting, mail, DNS, domain and server settings before choosing the destination.
03Map the GoDaddy products responsible for the site, WordPress, email, DNS and domain registration before cutover.
04Plan website files, databases, mail, DNS, scheduled work and settings that may not transfer directly.
05Prepare and test the destination before switching DNS or closing the old hosting account.
06Account for application, database, mail, DNS, caching, cron, TLS and backup dependencies.
Migration guides
Prepare the destination first, copy the site, test it, synchronize changes and then switch traffic.
WebsiteInventory, destination testing, data synchronization, DNS changes and keeping a rollback path.
DomainsMove registrar management without accidentally moving or breaking the services using the domain.
VPSInventory the server, copy it safely, test the destination, cut traffic over and preserve a rollback plan.
Yes. Send the current control panel or provider, website count, storage used, email requirements, domain/DNS setup, runtime versions, and the access you have.
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.
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.
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
Include the provider, platform, storage used, domains, email, software stack, and what you want to improve.