If ESP migration fails, try another file/format, unlock the file, reduce batch size, then update the tool/browser. Migration includes list cleaning, template/automation rebuild, domain warm-up and parallel run.
Why it matters
Most failures are input/lock/resource issues, not the tool itself.
Automations must be rebuilt.
Step by step
- Confirm list size, monthly sends, automation and transactional needs.
- Separate platform fee, overage, dedicated IP, verification tools and labor.
- Use real opens/clicks/unsubscribes for cost per email and ROI.
- 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
How do I fix a failed ESP migration task?
If ESP migration fails, try another file/format, unlock the file, reduce batch size, then update the tool/browser. 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