A migration is safer when rollback is a planned decision, not an emergency guess. Before changing DNS, record the current site, test the destination, and define the evidence that lets the owner keep or reverse the change.
Quick verdict
Keep the source environment available until the destination passes the agreed public checks. A managed host can simplify platform work, but it does not remove the need to inventory content, test forms, confirm redirects, or assign a rollback owner.
Who each option is for
| Approach | Best fit | Question to answer |
|---|---|---|
| Managed migration service | Teams that want a defined handoff and platform support | What is included and who owns the cutover? |
| Team-led migration | Teams with a tested runbook and technical owner | Who can restore the source if a check fails? |
| Staged rebuild | Sites that need a controlled content or plugin change | How will old and new URLs be compared? |
Feature and cost comparison table
| Control | Why it matters | Evidence |
|---|---|---|
| Full content inventory | Missing media or forms can appear after launch | URL, media, form, redirect, and cron lists |
| Staging copy | Changes can be tested without changing the public site | Staging URL and test result |
| Rollback window | DNS changes need an owner and a decision time | Named owner, cutoff, and source access |
| Restore evidence | A backup is useful only when it can be restored | Restore test and timestamp |
Migration or implementation notes
- Record the source WordPress, PHP, theme, plugin, DNS, and redirect state.
- Copy the site to staging and compare the home page, key pages, media, forms, login, and canonical URLs.
- Test the highest-value user journeys with cache and security settings enabled.
- Lower DNS TTL only after the rollback owner and cutover window are written down.
- After DNS changes, check the public site from a fresh browser and keep the source available until the checks pass.
Use the WordPress moving documentation as a reference for the parts that must be verified during a move.
Decision checklist
- We have the source URL and destination URL recorded.
- We tested forms, redirects, media, login, sitemap, and measurement.
- We have a named rollback owner and decision time.
- We know which DNS records change and how to restore them.
- We will keep the source available until public readback passes.
FAQ
Should the old host be deleted immediately?
No. Keep it available for the agreed rollback window and confirm that no required data still arrives there.
Does a staging check prove production is correct?
No. Production can differ because of DNS, caching, permissions, or environment settings. Perform a public readback after cutover.
What is the first rollback signal?
Use the written acceptance checks. A broken form, missing page, bad redirect, or failed login is a concrete reason to pause and investigate.
Leave a Reply