01 / Before you start: make an inventory.
Keep a simple record of each item, who owns the review, its status, and any unresolved issue. Export or back up the source before making changes.
Collect important URLs
Use the sitemap, navigation, analytics, and known external links. Include landing pages, older articles, PDFs, category pages, and other useful destinations.
Count content separately
Pages, posts, media files, products, and private records are different inventories. A page-layout count is not a record count.
List plugins by behavior
Record what each one does for visitors or staff, which external services it uses, and the data it stores.
Identify access and ownership
Confirm who controls the domain, DNS, hosting, assets, email service, payment provider, and integrations.
02 / In the preview: compare the site.
Choose representative pages first, then check the inventory. Keep the old website available while you review.
- Read imported text and check headings, links, images, downloads, and embeds.
- Compare the homepage, ordinary pages, articles, archives, and special layouts on desktop and phone.
- Open the CMS and create a test article. Check its layout and where it appears.
- Match important page addresses and compare titles, descriptions, canonical tags, and indexability.
- Log missing records and files explicitly; do not assume an attractive preview means the whole archive is present.
03 / Before launch: prove the workflows.
Assign each business-critical journey a person who can confirm it works. Keep private-data transfer work separate from the public-page review.
| Workflow | Acceptance check |
|---|---|
| Contact form | Submit realistic valid and invalid inputs; confirm delivery and any consent or follow-up action. |
| Newsletter | Verify signup, subscriber handling, sending-domain setup, and unsubscribe behavior. Existing lists need separate planning. |
| Store | Configure payments and check the purchase journey, confirmation, and delivery. Plan historical orders and subscriptions separately. |
| Members or customers | Verify access rules, account setup, recovery, and private content. Do not assume old passwords transfer. |
| Navigation and search | Check mobile menus, internal links, search results, and important empty/error states. |
04 / At launch: make the switch deliberately.
Choose a quiet period and decide how content changes made during migration will reach the replacement. Avoid two teams unknowingly publishing into different systems.
Agree the final content state
Use a short content freeze or a documented final update. Reconcile anything added since the preview was prepared.
Record the rollback route
Keep the prior hosting and DNS configuration available. Name the person who decides whether to revert.
Connect the domain
Apply the host’s domain instructions, preserve email records, and confirm HTTPS and the preferred hostname.
Run live checks
Test old URLs, forms, key pages, assets, and business workflows on the real domain.
05 / After launch: watch the real result.
Check for missing pages, unexpected redirects, failed forms, and delivery problems. Verify analytics and Search Console access on the live domain, and compare results with the baseline you recorded before the move.
Do not cancel the old hosting just because DNS now points elsewhere. Confirm that files, data, integrations, and rollback requirements have been addressed, then archive what you need and retire the old service deliberately.
A useful review record: item → original address → new address → owner → tested result → issue or follow-up.