What needs to move
Check leaving Bluehost with a destination-first website migration that verifies files, databases, PHP/runtime requirements, mail dependencies, DNS, redirects, SSL, and current writes before traffic changes.
Migrate from Bluehost
Plan a Bluehost-to-DotMoose move around the website and database copy, mail dependencies, DNS, redirects, SSL and a tested destination before cutover.
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 Bluehost with a destination-first website migration that verifies files, databases, PHP/runtime requirements, mail dependencies, DNS, redirects, SSL, and current writes before traffic changes.
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
Bluehost sites are usually WordPress on a cPanel style account, so the export is familiar: site files from the file manager or FTP, the database through phpMyAdmin, and mailboxes stored inside the account. Download a full backup as well. The panel backup and the manual exports together give two ways to rebuild if one restore path fails.
PHP version drift causes the visible failures here. A site that ran on an older PHP release can break on a newer default, and caching or security plugins can block the destination test address. Match the PHP version during testing, clear plugin caches on the copy, and check logins, comments and checkout before DNS changes and again right after.
Record the PHP version and extensions the site uses at Bluehost. Set the destination to match before judging any test result.
Security plugins sometimes reject logins from a temporary test address. Note which plugins do this and plan the whitelist step before testing starts.
Comments, orders and form entries keep arriving at the old site during the move. Sync the database once more inside the cutover window.
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.