A Black Friday hosting migration checklist helps you turn a hosting discount into a controlled move. Before buying, confirm what the new provider will transfer, what happens to your email and how you will recover if the new copy fails a critical check.
The practical order is simple: document the old setup, back it up, prepare the new hosting, copy and test the website, then switch traffic. Cancel the old account only after you have verified the new setup and preserved everything you still need.
Affiliate disclosure: We may earn a commission when you buy through our links, at no extra cost to you. Official migration documentation checked October 31, 2026. This is a planning guide, not a hands-on migration test or a guarantee of uninterrupted service. No unannounced Black Friday discount is assumed.
The quick decision
Buying for a new website? Focus on total cost and the features you will use. You do not need a migration service for a site that does not exist yet.
Moving an established blog? Prioritize a verified backup, a working preview and a clear DNS plan.
Moving a store or membership site? Plan how to handle new orders, signups and other database changes during the move. A cheaper subscription does not solve data synchronization.
Shortlist a host, then confirm the migration scope
Compare the full checkout total, renewal term, storage and recovery tools. Ask which website and email tasks are included before you pay.
Check Bluehost Plans →Check Hostinger Plans →Affiliate links. Offers and eligibility vary; confirm the final amount and selected billing term in checkout.
1. Decide whether switching is worth the work
A Black Friday offer can reduce your initial bill, but migration also consumes time. Write down the problem you expect the new host to fix: limited storage, a renewal bill you cannot justify, a workflow you dislike or missing tools. Ask the shortlisted provider to confirm that the selected package addresses that problem.
Compare the same purchase period. Add the upfront hosting payment, necessary email, backup costs, migration help and any overlap with your old account. Keep renewal costs separate so the introductory discount does not hide the next bill. See our monthly vs annual Black Friday hosting guide for the billing tradeoff.
2. Inventory the services attached to your domain
Your domain, website hosting, DNS and email can be managed by different companies. List where each one lives before changing anything. A domain transfer is a separate decision from moving the website; avoid combining extra changes unless you understand their dependencies.
| Item | Record before moving | Verify after moving |
|---|---|---|
| Website | Files, database, PHP requirements and required extensions | Pages, images, login and scheduled tasks |
| DNS | Current nameservers and complete DNS zone | Website and service records resolve as intended |
| Mailbox provider, accounts, aliases and authentication records | Inbound and outbound messages reach real inboxes | |
| Transactions | Orders, subscribers, payment integrations and webhooks | New records and callbacks arrive at the intended system |
| Recovery | Independent backup and old server details | Restore method and rollback owner are documented |
Store this inventory securely. A public checklist should never contain account passwords, private keys or customer exports. Give a migration team only the access required through its approved secure channel.
3. Confirm the migration scope before checkout
Ask whether your exact platform and site size qualify, whether the transfer includes email, and who handles DNS, SSL and follow-up fixes. If the site uses a proprietary builder, confirm an export or rebuild path rather than assuming a WordPress transfer tool can move it.
Hostinger’s migration guide says its website transfer covers files and databases, while email needs a separate move. It also excludes items such as cron jobs and DNS records. Its eligibility rules distinguish supported CMS sites and hosting packages, so check the current requirements for your site.
Bluehost’s Pro Migration finalization guide asks customers to review the migrated website, finalize DNS and SSL, and check email operation. Treat a transfer-complete message as a prompt to verify your setup.
For the package comparison, read Bluehost vs Hostinger Black Friday. For the migration details, use the provider’s current service scope and written answers for your account.
4. Make an independent backup you can recover
Keep a separate copy of your website files and database before the move. Include uploaded media and configuration files needed to rebuild the installation. If business email is leaving the old provider, preserve the mailbox data using a method supported by your email service.
A downloaded archive is more useful when you know how to restore it. Check that the archive opens, that the database export exists and that someone can explain the recovery steps. Store the copy somewhere you control outside the hosting account being replaced.
For a busy site, record when the backup was taken. A copy made on Monday does not contain Tuesday’s orders. This timestamp determines what must be synchronized before the final switch.
5. Copy and preview before changing DNS
Prepare the destination environment and migrate a copy while the old site still serves visitors. Use the preview method the provider recommends for your setup. A temporary address can behave differently from the real domain, so check whether your test method preserves the intended site address and configuration.
Test the homepage and several real article or product URLs. Open image galleries, search, menus and mobile layouts. Log in with a test account. Check that required plugins, scheduled jobs and integrations have the correct configuration. Avoid a theme redesign or a large plugin change during the same move; each extra change adds another possible cause if something breaks.
6. Give email its own checklist
Decide whether email stays with its existing provider. If it does, preserve the records that provider requires when recreating a DNS zone. If it moves, create the destination mailboxes and arrange the data transfer before changing mail routing.
Check mailbox names, aliases, forwarding rules and device settings. Compare MX, SPF, DKIM and DMARC configuration with the email provider’s instructions. Do not paste an old authentication value into a new service without checking that it applies.
After the switch, send messages to and from an unrelated external inbox. Test a contact form separately: a successful form submission on the screen does not prove that the notification reached the business. If email still depends on the old account, that account is not ready to cancel.
7. Plan the final database sync for active sites
A static brochure site and a busy shop need different cutover plans. For a store, decide who will capture the last orders, pause writes if necessary, move the final data and reopen transactions. Include memberships, form submissions, comments and inventory changes in that discussion.
Coordinate with the host or developer before the move. A short announced maintenance window may be easier to manage than two servers accepting new orders independently. Do not promise customers zero downtime unless the migration design supports it.
If a rollback becomes necessary after the new server has accepted transactions, preserve those records before reverting. Pointing DNS back alone does not merge new orders into the old database.
8. Switch traffic and verify the live domain
Change only the records required by your DNS plan. If you change nameservers, make sure the destination zone contains the non-website records your services need. Keep a copy of the previous values and record exactly what changed.
Then test the real domain over HTTPS. Confirm the intended version loads, important URLs still work, and the certificate is valid. Check redirects, canonical URLs, robots settings and the sitemap. A hosting-only move usually does not call for changing article URLs; if URLs do change, map and verify the required redirects.
Use fresh sessions and more than one network where possible. Check the live logs and application behavior instead of relying on one cached homepage. Recheck analytics and affiliate button destinations so conversion tracking and purchase paths still work.
9. Cancel the old plan after acceptance checks
Keep the old hosting during a planned verification period. Confirm the new website, email, scheduled tasks and transaction flow are working. Take another backup of the accepted setup and save any exports, invoices or account information you need from the old provider.
Review the old account’s renewal and cancellation rules. Make sure canceling hosting will not also remove mailboxes or another service you intended to keep. Only then complete cancellation and retain the receipt.
Which host should you shortlist for the move?
Shortlist Bluehost if its WordPress package, checkout total and available migration support match your needs. Ask specifically about your website size, mailbox count and any paid help you need.
Shortlist Hostinger if the selected plan meets your resource needs and your site qualifies for its migration workflow. Build separate time into your plan for email, DNS and excluded configuration.
Neither option wins this checklist on measured speed or support quality: we have not benchmarked those here. The useful decision is which complete package and migration scope fits your website. Browse our Black Friday hosting buying guide if you are still comparing providers.
Shortlist a host, then confirm the migration scope
Compare the full checkout total, renewal term, storage and recovery tools. Ask which website and email tasks are included before you pay.
Check Bluehost Plans →Check Hostinger Plans →Affiliate links. Offers and eligibility vary; confirm the final amount and selected billing term in checkout.
Frequently asked questions
Should I cancel my old hosting before migrating?
Keep it available while you copy and validate the destination. Cancel after the new setup passes your acceptance checks and you no longer need services or data from the old account.
Does a website migration include business email?
Do not assume it does. Ask for the exact service scope, mailbox allowance and exclusions. Website files, mailboxes and DNS each need an explicit plan.
Do I need to transfer my domain to change hosting?
A hosting move and a registrar transfer are separate actions. Confirm how to point your existing domain to the new hosting while retaining the registrar if that is your preference.
Can I buy a deal now and move later?
You can plan a later move, but check when billing starts, the refund conditions and any migration request deadlines before paying. Do not assume unused time postpones the renewal date.
Will switching hosts improve rankings?
A move does not guarantee higher rankings. Preserve working URLs and indexability, check the live site after launch and address the actual technical problems that motivated the move.
What should I do if the new site fails after the switch?
Follow the rollback plan agreed with your host or developer. Preserve new transactions and other changes before reverting, then investigate the failure using the known-good backup and configuration record.
Your final go-live check
Before committing to the deal, make sure you can answer four questions: What will the host move? What must you handle? What is the total cost? How will you restore service if a critical check fails? Clear answers make the discount more useful.
Sources checked October 31, 2026: Hostinger’s official website migration guide and Bluehost’s official Pro Migration finalization guide, linked above. The checklist and budgeting example are MentorsReview’s editorial planning guidance. Provider processes can change; confirm account-specific instructions before the move.
