What needs to move
Check leaving HostPapa by first identifying the exact hosting, domain, DNS, email, WordPress, or VPS components in use because each component may need its own migration path.
Migrate from HostPapa
Compare a move from HostPapa to DotMoose by inventorying website files, databases, email, DNS, domains and any VPS or WordPress services before changing traffic.
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 HostPapa by first identifying the exact hosting, domain, DNS, email, WordPress, or VPS components in use because each component may need its own migration 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
A HostPapa account can hold several separate things at once: shared hosting, domain registrations, DNS, mailboxes and sometimes a VPS. Start with an inventory of which of those are actually in use. Shared sites export through the panel as files plus database dumps, while registered domains follow the registrar transfer path on their own schedule.
The common failure is assuming one export covers everything. Mailboxes live inside the hosting account, DNS may sit with the domain registration, and a site built with a website builder tool may not export as files at all. Check each component, test the rebuilt site privately, and change DNS only after mail and forms pass on the new copy.
List hosting, domains, DNS, mail and any VPS as separate items. Each one gets its own export method and its own completion check.
Ask how each site was built. Drag and drop builder sites usually need a rebuild at the destination, while WordPress and static sites copy as files.
Mailboxes stored in the hosting account move with the site data. Recreate each address and move its stored mail before the MX record changes.
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.