How to Switch Marketing Automation Platforms in Six Gated Stages
Switch marketing automation platforms in six stages, from inventory and consent transfer to a parallel run and the domain ramp, each closed by an exit check.
On this page
A phased cutover plan for a marketing automation platform migration moves the work across in stages, and each stage ends with an exit check that has to pass before the next one opens. Six stages cover it: inventory, data mapping, consent and subscription status, rebuilt forms and workflows, a parallel run, and the sending domain ramp. Moving contact records is the quick part. The risk sits in everything attached to them: opt-outs, triggers, form endpoints, DNS records and the reputation of the domain you send from. For the basics, see what marketing automation covers.
Six stages and the check that closes each one
Marketing automation platform migration best practices come down to five concerns: phased cutover, data mapping, testing, deliverability and consent, and the order matters. Consent is settled before the new platform sends anything, and authentication is in place before the parallel run's first send, even though the volume ramp finishes last.
| Stage | What moves | Exit check |
|---|---|---|
| 1. Inventory | Workflows, forms, lists, integrations, templates, DNS records | Every live program has an owner and a decision |
| 2. Data mapping | Fields, picklist values, lifecycle stages, tags | A sample import reconciles with the source export |
| 3. Consent | Opt-ins with source and timestamp, unsubscribes, bounces, complaints | Suppressions reconciled, known opt-outs excluded from a test send |
| 4. Forms and workflows | Every kept program, rebuilt | Test contacts pass every branch |
| 5. Parallel run | Programs, in batches | No contact live in automations on both platforms |
| 6. Domain ramp | Sending volume | Authentication aligned, one-click unsubscribe working, spam rate under target |
1. Inventory what the old platform does
List every active workflow, form, list, scoring rule, integration and template, plus the DNS records the platform depends on. Give each row an owner and a decision: move, rebuild or retire. A program nobody will claim is a retirement candidate, and retiring it now spares you mapping its fields.
Export the history you want to keep, since sync tools carry less than teams assume. Klaviyo says its Mailchimp integration brings over subscribers, lists, and open and click data, imports the last 90 days of campaign data when campaign engagement syncing is enabled, and won't sync entire campaigns. The same guide notes that Mailchimp's drag-and-drop templates can't be exported.
Exit check: every row has an owner and a decision, and the reports you need for year-over-year comparisons are saved outside the old platform.
2. Map the data before importing it
Map one field at a time: source, destination, data type, allowed values and any transform. Lifecycle stage and lead status picklists need a value-by-value map, with a decision for every source value that has no twin on the other side.
Klaviyo's Mailchimp guide says tags and other custom audience fields do not sync automatically, and that tags can move through a CSV export and import as custom properties. A segment built on a tag that never arrived matches nobody. If an AI assistant drafts the first pass of the map, a person still signs off every row; our notes on setting up Claude for marketing work are a fair place to start.
Exit check: a few hundred imported records reconcile with the source export on row counts, a dozen spot-checked records and every picklist value.
3. Carry consent and subscription status across
Unsubscribes, bounces and complaints go in before the first send. Klaviyo tells migrating senders to keep unsubscribed and bounced addresses out of the subscriber CSV and import them as suppressions before sending email. Its "Apply bulk consent" option is meant only for a file where everyone has explicitly consented to email marketing. For API imports of existing subscribers, the guide says to set historical_import to true with a consented_at timestamp at least 5 minutes in the past, which skips double opt-in messages and list-triggered flows.
Carry the evidence too: where each opt-in came from, when, and what the form said. Under the GDPR, a controller relying on consent must be able to demonstrate that the person consented, and withdrawing must be as easy as giving consent, per Article 7 on EUR-Lex.
The old platform keeps a job after cutover. The FTC CAN-SPAM guide says opt-out requests must be honored within 10 business days, and that any opt-out mechanism you offer must be able to process requests for at least 30 days after you send your message. Unsubscribe links in the old platform's emails still point at it, so it keeps accepting opt-outs and passing them to the new one.
A worked example, hypothetical and with assumed figures: the old exports show 5,900 unsubscribes, 1,100 hard bounces and 200 spam complaints, with 150 addresses listed twice across the files. The new platform should hold 5,900 + 1,100 + 200 - 150 = 7,050 suppressed addresses before anything sends. If the old platform's last send goes out on March 3, its opt-out handling stays live until at least April 2, with a daily sync of new opt-outs.
Exit check: the suppression count matches the reconciled total, and 20 known opt-outs are excluded when added to a test send.
4. Rebuild forms and workflows in the new platform
Klaviyo's Mailchimp guide tells switching senders to recreate automations as flows and recreate sign-up forms, and says forms created in Mailchimp can't be redirected to Klaviyo. Triggers, enrollment rules and wait steps can behave differently between platforms, so even a faithful copy needs testing.
The rebuild is also the cheapest moment to decide which programs an AI agent should run. Settle the controls first (see the governance operating model for marketing agents); the AI ROI calculator helps size the return, and our agentic AI automation team takes on the build.
Exit check: test contacts walk every branch of every rebuilt workflow, and each form submission arrives with its consent source and timestamp filled in.
5. Run both platforms in parallel, one batch at a time
In a parallel run both platforms are live, and each program lives on exactly one of them. Move the lowest-stakes programs first and the flows that carry the most revenue last. Klaviyo's guide says to turn off all Mailchimp automations once the new flows are live so you're not double-emailing people, and after pointing every sign-up form at Klaviyo, to wait a few days and watch your Mailchimp audiences. An old list that keeps growing means some form still posts to it.
Exit check: no contact is active in automations on both platforms, the old lists have stopped growing, and a test opt-out on the old platform arrives as a suppression on the new one.
6. Ramp the sending domain under the bulk sender rules
The new platform has to meet mailbox provider rules from its first send, so this stage starts in DNS before the parallel run and closes at full volume. Google applies its bulk sender rules to senders of 5,000 or more messages a day to Gmail accounts and requires SPF, DKIM and DMARC (the policy can be none), a From: domain aligned with the SPF or DKIM domain, one-click unsubscribe on marketing and subscribed messages, and a Postmaster Tools spam rate below 0.30%, with a recommended target below 0.10%.
The Google sender FAQ adds two details that matter in a switch: a sender that meets the bulk criteria once is permanently a bulk sender, and messages from subdomains count toward the primary domain. By that counting rule, a fresh subdomain of the same domain will not take you out of the bulk rules. Yahoo asks bulk senders for SPF, DKIM, a passing DMARC policy of at least p=none, one-click unsubscribe, unsubscribes honored within 2 days and a spam rate below 0.3%.
On the domain itself, Klaviyo says the sender reputation associated with a branded sending domain carries over when you migrate it. If the old platform still needs to send during the move, it says to use an unused subdomain; to reuse the same one, stop sending from it on the old platform and remove the conflicting DNS records first. It also warns against deleting a shared SPF record that authorizes other email services, and says deliverability issues will not automatically resolve by switching ESPs. The ramp schedule has its own guide: how to warm up a sending domain.
Exit check: SPF, DKIM and DMARC pass and align, one-click unsubscribe works in a test, and the spam rate stays under 0.10% at full volume.
Why marketing automation migrations fail
The common reasons a marketing automation migration fails each map to one of the exit checks above.
| Failure | Stage | Check that catches it |
|---|---|---|
| Opted-out contacts get mailed from the new platform | 3 | Suppressions reconciled before the first send |
| An import fires welcome or opt-in emails at the whole base | 3 | Import settings tested on a sample |
| Segments built on tags come up empty | 2 | Sample compared field by field |
| A form still posts to the old platform | 5 | Old lists watched for growth |
| Contacts get the same email twice | 5 | No contact live on both platforms |
| Old unsubscribe links stop working | 3 | Opt-outs processed for 30 days after the last old send |
| Authentication breaks for other services | 6 | Shared SPF record kept |
| Gmail or Yahoo requirements missed | 6 | Alignment, one-click unsubscribe and spam rate checked |
Retire the old platform last
Decommissioning is the final gate. The old account can close once its last send is more than 30 days old, its opt-out sync has gone quiet and the reports are exported. Its DNS records come out last, without touching a shared SPF record, since Klaviyo's domain guide says removing a previous provider's records can disrupt authentication and delivery on that platform. Run the stages this way and cutover day becomes the least eventful day of the project.
Sources
- Google: Email sender guidelines, Google Workspace Admin Help
- Google: Email sender guidelines FAQ, Google Workspace Admin Help
- Yahoo: Sender best practices, Yahoo Sender Hub
- FTC: CAN-SPAM Act, a compliance guide for business
- EUR-Lex: Regulation (EU) 2016/679 (GDPR), Article 7
- Klaviyo: How to migrate existing email subscribers (and unsubscribes) into Klaviyo
- Klaviyo: How to migrate your branded sending domain from a previous ESP to Klaviyo
- Klaviyo: How to migrate from Mailchimp
