For a US business website, a hosting move should keep the website, enquiries and chosen email arrangement working together. Start with an inventory of what must move, then match the destination package and migration scope to that inventory.
Make an inventory before changing anything
A website move can involve more than the visible pages. List the files, databases, domain registration, DNS records, email accounts, scheduled tasks, application settings and third-party connections used by your project. Domain registration and hosting can remain with different companies.
Decide whether the provider, a contractor or you will perform the move. An included migration service can have eligibility conditions, limits or exclusions. Check the selected plan rather than assuming every website and mailbox will be transferred.
Prepare an independent copy
Create a copy of the website files and export the database where applicable. Save configuration and DNS records securely. Check that the copy is complete and that you know how to restore it. Keep passwords and database exports out of public folders.
A backup at the old hosting company may disappear after the account is cancelled. Review the daily-backup hosting selection, but treat provider backup features and your own migration copy as separate parts of the plan.
Prepare and test the destination
Confirm that the new environment supports your application's software versions and requirements. Copy files and import the database if needed, then adjust configuration. Use a provider-supported preview or test method before changing public DNS.
Check page loading, login, images, forms, outgoing messages, redirects and certificate configuration. For WordPress, verify plugins, permalinks and any background jobs. Avoid leaving test copies publicly indexable or allowing them to process real customer orders by accident.
Move email deliberately
Website DNS changes do not automatically copy mailboxes or messages. Inventory mail users, aliases, mailbox sizes and client settings. Confirm which service will handle email after the move and arrange the transfer of existing messages where required.
Review MX records and the SPF, DKIM and DMARC configuration used by your email providers. Preserve legitimate sending services when adjusting authentication. Do not copy values blindly between platforms; follow the new mail provider's instructions.
Plan the DNS switch and final synchronisation
DNS changes can be cached, so different visitors may temporarily reach different environments. A lower TTL can help with planned changes when applied sufficiently early, but it does not guarantee an instant switch everywhere.
A live shop or membership site may need a maintenance window or another method of final data synchronisation. Agree how new orders, uploads and messages will be handled while the move is in progress. The right process depends on the application; do not assume a static-file copy is enough.
Verify before cancelling the old account
| Area | Final check |
|---|---|
| Website | Pages, assets, redirects, forms and application jobs work. |
| Security | The correct domain has a working certificate and sensible access settings. |
| Incoming and outgoing mail work; required old messages are available. | |
| DNS | Website, mail and verification records point to their intended services. |
| Recovery | You have an independent copy and know the rollback procedure. |
Keep the old service available until checks and any required synchronisation are complete. Then review cancellation, renewals and any domain or mail services you intend to retain.
Choose the destination by what it must do
Compare the software, administration and recovery features your project requires in our shared hosting catalogue. For WordPress projects, read what managed WordPress includes. You can also review hosting costs and commitments before paying for a long term.
This checklist is a planning aid. The detailed transfer procedure depends on your application and the current instructions of the old and new providers.
Your next hosting step for US websites
List the website, database and email services separately and agree which ones are included in the transfer. Test the copied site before changing the intended DNS records. Keep the original service available until the move and the chosen mail arrangement have been checked. Plan these choices for your US website using the USD display.
Build a shortlist: Compare web hosting for US websites · WordPress hosting for US websites.