Email Marketing Platform Migration Checklist
An email list is more than a column of addresses. It contains subscription decisions, exclusions, field values, campaign history, and the logic that decides who receives the next message. A platform change can break those relationships even when the contact count appears correct.
1. Inventory audiences and the messages they receive
List audiences, signup forms, ecommerce connections, welcome sequences, renewal reminders, and recurring campaigns. Record which messages are marketing and which belong to an operational sending system. The transactional versus marketing email guide helps define that boundary; this checklist focuses on moving the marketing workflow.
Decide what historical material must remain accessible. Old campaign reports, templates, and contact activity may need a separate archive if the destination cannot import them. Keep a migration owner and a sending owner so nobody schedules a normal campaign while the audience state is being rebuilt.
2. Preserve status and exclusions explicitly
Export subscribed, unsubscribed, non-subscribed, and undeliverable contacts as distinct categories where the provider supports them. Preserve the available source and timing information behind subscription decisions. Do not infer permission from a purchase, an existing CRM record, or the mere fact that an address appears in a file.
Mailchimp’s switching guidance recommends keeping subscription categories separate. Its import documentation also describes how existing contact statuses affect imports. Check the destination’s rules and your organization’s requirements before importing any category into a sendable audience.
3. Map fields, segments, and personalization
Translate fields such as customer type, language, purchase category, and signup source into the destination format. Watch for blank-value behavior and differences between tags, groups, and calculated segments. A segment named “Customers” may be a static list in one tool and an automatically changing rule in another.
| Source item | Destination test | Acceptance condition |
|---|---|---|
| Unsubscribed address | Import and inspect status | Excluded from marketing sends |
| Preferred language | Preview localized segment | Correct contacts and message version |
| Welcome automation | Test new signup | Enters once at the intended step |
| Personalized greeting | Preview missing first name | Readable fallback text |
4. Rebuild automations without replaying the past
Create workflows in a paused or controlled state and identify the event that starts each one. Decide what happens to contacts partway through a sequence. A bulk import should not accidentally look like a fresh signup and send a welcome discount to years of existing customers.
Test one new contact, one existing customer, and one excluded address. Check entry rules, exit rules, time delays, and timezone assumptions. Document which system owns each live signup route during the move so two platforms do not both start a sequence.
5. Validate the sender and customer experience
Follow the destination provider’s current instructions for domain authentication and sender setup. Test from addresses your team controls, checking links, images, personalization, and the unsubscribe journey. Confirm that the resulting status change is respected by every relevant integration.
Plan the first production sends with the provider using current audience quality and sending history. Do not assume moving a large audience establishes a healthy sender reputation overnight. Compare platforms on these operating requirements alongside price; the Campaign Monitor review and Moosend review provide starting points.
6. Cut over forms and reconcile the final changes
Choose a cutover point, pause the source workflows as planned, and move signup destinations deliberately. Capture late subscriptions and unsubscribes that happened after the first export. Keep a record of the import result, rejected rows, intentional exclusions, and the final source-to-destination mapping.
Reconcile by status and segment rather than expecting every raw row to become a sendable contact. Test a new signup after the switch and monitor the first live campaign for delivery and audience issues. Retain the required archive and access until the agreed acceptance work is complete.
Email Marketing Platform Migration Checklist FAQs
Can you import every old contact as subscribed?
No. Preserve the original status and exclusions, and establish the appropriate basis for any marketing send. An import does not create permission.
Will campaign history move with the contacts?
Not necessarily. Verify which reports, events, templates, and automation positions are supported, and decide what needs a separate archive.
What is the most important migration test?
Use a subscribed contact, an opted-out contact, and a new signup to prove that inclusion, exclusion, and automation entry behave as intended.
Next step: Create a contact-status map before exporting the audience. Then compare email marketing software offers using the import and sending workflow you need.