Home/Answers/ESP migration
EMAIL COST LAB / ESP migration

After ESP migration Processing

After ESP migration, spot-check the output, then decide whether to delete/archive the original; keep a backup.

Updated 2026-11-01About 3 minLocal test
Quick answer

After ESP migration, spot-check the output, then decide whether to delete/archive the original; keep a backup. Migration includes list cleaning, template/automation rebuild, domain warm-up and parallel run.

Why it matters

A backup lets you roll back if the output is wrong.

Automations must be rebuilt.

Step by step

  1. Confirm list size, monthly sends, automation and transactional needs.
  2. Separate platform fee, overage, dedicated IP, verification tools and labor.
  3. Use real opens/clicks/unsubscribes for cost per email and ROI.
  4. Do not compare monthly fees only; model 12-month total and migration cost.

Common mistakes

  • Comparing monthly fees without contact/overage charges.
  • Ignoring list cleaning and verification.
  • Confusing deliverability with open rate.
  • Not counting automation/template rebuild time during migration.

Checklist

  • How contacts are billed; duplicates/unsubscribes/inactive.
  • Monthly send limits, overage and transactional pricing.
  • Automation, A/B, segmentation and API included?
  • Deliverability tools/dedicated IP extra?
  • Compliance, data export and migration terms.

Key facts

  • Automations must be rebuilt.
  • Warm up domains.
  • Run in parallel.

FAQ

What should I do after ESP migration?

After ESP migration, spot-check the output, then decide whether to delete/archive the original; keep a backup. Migration includes list cleaning, template/automation rebuild, domain warm-up and parallel run.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: ScaledMail