← All documentationSearch guides

Verify migration before DNS cutover

Separate private import completion from switching public traffic.

  • Administrator
  • Intermediate
  • 1 min read
  • Reference: 101.18.15
  • Reviewed

Before you begin

Completed import, retained source data and a cutover plan.

Use the controls offered by your installed version and account permissions. This guide describes the workflow; it does not grant additional access.

Follow the steps

  1. Test static/PHP pages with intended hostname routing.
  2. Verify connections and representative recent database records.
  3. Inspect mailbox contents and planned mail routing.
  4. Review DNS and certificate readiness.
  5. Change public DNS only after planning for writes and mail received during transition.

Check the result

Destination workloads work and the public transition is controlled.

If something goes wrong

The tool does not promise automatic public DNS cutover or synchronization of later source writes. Keep the source available until verified.

Prepare useful details for support