Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Migration

Hosting migration rollback: decide how you will reverse a failed cutover

Published August 2026 · 2 min read · Updated 2026-09-05

Hosting migration rollback means preserving a safe path back while traffic and data move. The rollback must account for writes created on the new environment, DNS cache overlap, mail/cron/webhook behavior, and changes made to the source during preparation; it is more than saving the old IP address.

Freeze destructive source changes

Keep the old hosting account/server intact until verification ends. Record files, database, DNS, mail, cron, redirects, certificates, runtime versions, integrations, and any source-specific configuration.

Avoid cancelling the old provider on the same day as DNS cutover.

Define the authoritative data point

Decide when the database/uploads switch from source to destination and how final writes are synchronized. For transactional sites, use maintenance/read-only, replication, or an explicit final delta process.

If rollback occurs after new writes, plan how those writes return to the source or are preserved.

Keep DNS rollback narrow

Save old/new records and TTLs, change only the service records required, and leave unrelated mail/verification records alone. Remember recursors can hold both old and new values through the transition.

A low TTL reduces cache duration but does not guarantee immediate convergence.

Set rollback triggers and end condition

Define errors/latency/data-integrity failures that trigger rollback, who decides, and what tests prove recovery. End the rollback window only after real traffic, writes, jobs, mail, and monitoring are healthy on the destination.

  • Keep source alive.
  • Plan write synchronization.
  • Save exact DNS.
  • Define trigger/owner/end condition.

Next step

Keep the source intact, define rollback triggers, control changing data and document DNS or routing reversal before a hosting migration becomes one-way.

Plan a DotMoose migration

Keep reading

Related guides.

Change email hosting without downtime: migrate mail without losing messages

Change email hosting without downtime by preparing destination mailboxes first, copying historical mail, preserving aliases and authentication, switching MX carefully, and synchronizing messages delivered during the transition.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More migrations guides

We will handle the move. You check it first.

Your 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.

Start my free moveSee plans and prices
See pricesFree move