Cold email software migration checklist with a controlled cutover

Define the decision

A contact export is not a complete campaign migration. The new system may interpret status, timing and identity differently, and recreating a sequence can make old contacts eligible for messages they should not receive.

Work through the procedure

1. Inventory active campaigns, mailbox ownership, exclusions and unresolved replies.
2. Map source fields and states to the destination, marking unsupported data explicitly.
3. Test synthetic imports and controlled replies.
4. Pause the affected sending path during cutover.
5. Reconcile intended enrollments and retain a rollback plan before resuming.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Migration record: 500 intended active contacts, 80 excluded addresses, 12 open conversations
Release gate: exclusions preserved and open conversations assigned
Unresolved: historical enrollment position cannot be imported → review manually rather than restart every contact at step one

Read the result

The unresolved-state list is part of the deliverable. It prevents a superficially successful CSV import from hiding a behavior change.

Check before moving on

1. Check ownership of domains and purchased mailboxes before cancellation.
2. Keep old credentials only as required by the approved rollback window.

Limits and next action

Do not delete source records or cancel the old service before validation. This checklist does not imply a native migration importer or full-fidelity export in Zintara.

Source: Zintara implementation and product context