Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Email Marketing › Email Fundamentals

Migrating to a New Email Platform

How to move email to a new platform without losing subscribers or reputation: inventory, consent and suppression, authentication, flows, forms and staged sends.
Tutorialintermediate11 min readUpdated

Why migrations lose subscribers and reputation

A migration fails quietly because the old platform did a lot of work nobody wrote down. It held the suppression list, so people who had unsubscribed, bounced or complained were never mailed. It held consent records against each contact. It ran flows whose exits had been tuned over years. It received sign-ups from forms embedded around the website. It signed mail with keys published in the domain's DNS. None of that moves on its own, and a contact export, which is what most migrations start and end with, carries almost none of it.

The consequences arrive with the first sends. People who opted out years ago are mailed again, which is a consent problem before it is a deliverability problem, and they are the recipients most likely to report the message as spam. The suppression list entry describes how often that file is the one left behind. New sign-ups go to a form that still posts to the old account, so the welcome series never fires. A flow rebuilt without its purchase exit sends reminders to people who have already ordered. Mail signed for the platform's own domain rather than the business's fails alignment, and the domain's DMARC policy starts working against its own newsletter.

What the old platform doesWhat breaks if it is missedWhere the detail lives
Holds unsubscribes, hard bounces and complaintsPeople who opted out are mailed againSuppression list, list hygiene SOP
Stores consent records against contactsThe business cannot show how anyone joinedList building and consent
Signs and sends mail for the domainAlignment fails and mail is filteredEmail sending domain setup checklist
Runs flows with tuned triggers and exitsDuplicate or mistimed messagesEmail automation flow launch checklist
Receives sign-ups from forms and the shopNew subscribers are never welcomedWelcome series tutorial
Feeds reports with tagged linksResults cannot be compared across the moveUTM and naming conventions

The move also changes what mailbox providers see. A new sending platform is new infrastructure, and the deliverability guide explains why a platform migration reads, from the provider's side, as a change in behaviour that should be staged. The steps below are ordered so that the parts that protect people and reputation are in place before anything is sent.

Before you start

  • The new platform chosen and contracted, with administrator access, after a selection made on the programme's requirements rather than on a demo.
  • Access to the old platform's exports, including suppression lists and, where the platform offers it, engagement history, and a note of when the old contract ends.
  • DNS access, or the person who has it, booked for the authentication step, since most of it is DNS changes that marketing cannot make alone.
  • An owner for each area. Contacts and consent, deliverability, each flow, forms and integrations, and reporting each need one named person. A RACI matrix with one accountable owner per row stops the classic gap where everyone assumed someone else exported the suppression file.
  • A list of every system that feeds or reads the email platform: the shop or booking system, the CRM, form tools, the analytics property, any ad platform audience sync. The data flow and integrations guide explains how to map them. If the CRM is being replaced in the same project, the tutorial on moving to a new CRM covers that side.
  • The campaign calendar for the migration period, so that no large promotional send is planned for the weeks when the new platform is being staged. The email marketing calendar template is the place to mark the freeze.
  • Seed addresses at the major mailbox providers and a way to read full message headers.

A business inheriting a programme it did not set up should run the account and data inventory in the tutorial for taking over a marketing programme first; this tutorial assumes the email programme itself is understood.

The steps

  1. Inventory everything the old platform does

    Build a migration register, one row per item, before exporting anything. List every list or audience and the fields it uses, including the consent fields; every suppression list by type; every saved segment with its written definition; every flow with its trigger, timing, branches, exits and the templates it sends; every sign-up form, checkout opt-in and confirmation message; every integration that sends events in or data out; the sending domains and their authentication; and the reports people rely on. Add three columns: the owner, the state on the new platform (not started, built, tested, live) and the date the old item was switched off. The register is the plan, the progress report and, afterwards, the record of what moved. Anything that turns up later and is not on it is the warning that the inventory was too quick. If the business keeps a standing register of its marketing integrations, start the integration rows from it, and update it once the move is finished.

  2. Export contacts with consent records and the suppression files

    Export active contacts with every field the programme uses, and above all the consent record: the source, the timestamp, the wording the person saw, the choices they made and, where double opt-in was used, the confirmation timestamp. The list building and consent guide explains why that record matters; in the UK the regulator's direct marketing guidance, listed in sources, explains the rules on electronic marketing it supports. Export the suppression lists as separate files, one per type, because a status field that does not map across is how unsubscribes become ordinary contacts. Export engagement history too where the platform allows it, since the staging step needs to know who engages. Reconcile the counts: the active export plus the suppression files should account for every address the old platform holds.

  3. Authenticate the new platform on your own domain

    Set the new platform to sign mail with the business's own domain, not the platform's shared one, and to send from a domain or subdomain that aligns with the visible From address. Merge its SPF include into the existing record rather than adding a second record, publish its DKIM keys and keep the DMARC policy where it is until the reports show the new platform passing. Confirm that marketing sends will carry the one-click unsubscribe headers RFC 8058 specifies, a List-Unsubscribe header with an HTTPS address and a List-Unsubscribe-Post header, alongside a visible unsubscribe link; Google's sender guidelines document both for bulk senders, as the deliverability guide explains. The email sending domain setup checklist holds every line of this step, and the authentication group should be ticked with test sends to the seed addresses before anything else is loaded.

  4. Load suppressions first, then contacts into a holding segment

    Import the suppression files before a single contact, as a global suppression that applies to every send the new platform makes. Then import the active contacts, tagged with their consent source and placed in a holding segment that no campaign or flow can reach yet. Where an address appears in both an active export and a suppression file, the suppression wins; a person who opted out once does not become mailable because a spreadsheet disagreed. Check the counts against the reconciliation from the export step and investigate any difference. Hard bounces belong in the suppression list too, because mailing addresses that no longer exist is one of the first things a provider notices about a new sender. The email list hygiene SOP describes how those lists are kept once the move is done.

  5. Rebuild segments from written definitions

    Rebuild each standing segment from its written definition in the register, not by copying the old platform's saved filters, which often encode logic nobody remembers. Use the small set of standard attributes the segmentation guide recommends, such as lifecycle stage, engagement tier and stated preferences, and combine them at send time. Compare each rebuilt segment's size with the old platform's figure for the same definition. Small differences usually come from how each platform counts engagement or handles missing fields; write the explanation down, because whoever compares reports across the migration date will need it. Retire any segment nobody has mailed in a long while rather than moving it.

  6. Rebuild each flow with its exits

    Rebuild flows one at a time, starting with the welcome series because every new subscriber passes through it. For each, copy the trigger, timing, branches and content from the register, and set every exit to be evaluated before each send, not only at entry, as the automation hub explains. Decide what happens to people who are part-way through a flow at the cutover: either they finish in the old platform and nobody new enters it, or they start again in the new one; never both. Run each rebuilt flow through the email automation flow launch checklist and push test contacts through every branch, including a purchase mid-sequence and an unsubscribe, before it is switched on.

  7. Move sign-up forms and the confirmation step

    Point every sign-up form, checkout opt-in and integration at the new platform, and keep the consent wording identical unless it is deliberately being changed, in which case the new wording goes into the record from the day it appears. Rebuild the confirmation message for double opt-in and the expiry of unconfirmed addresses. Then submit a real sign-up through each form and follow it: the contact is created with its source and timestamp, the confirmation arrives where it should, and the welcome series starts. A form that still posts to the old account is the most common reason a migrated programme seems to stop growing.

  8. Keep link tagging and reporting continuous

    Carry the campaign tagging conventions across unchanged: the same UTM parameters, the same source and medium values and the same campaign naming, set out in the UTM and naming conventions template. Platforms differ in how they count opens and clicks, so annotate the migration date on every email report and compare the periods either side on clicks and on outcomes recorded in analytics and the order system rather than on the platforms' own engagement figures. Record which report each person used before the move and confirm it exists, built from the new platform's data, before the old account closes.

  9. Stage the first sends from the most engaged subscribers

    Release contacts from the holding segment in stages, starting with the subscribers who have engaged most recently. Google's sender guidelines advise against sudden spikes in volume and recommend a gradual ramp, and the deliverability guide explains how a new platform reads as a change in behaviour. After each stage, read bounces, complaints and unsubscribes, and the provider's view in postmaster tools where the domain is verified; widen the audience while they hold steady and pause when they worsen. Keep everything else still: the deliverability guide's advice never to combine a migration with a list import and a new cadence in the same week applies here in full.

  10. Switch off the old platform only after the final export

    Stop the old platform's flows on the day the rebuilt ones go live, so that nobody receives both. Keep the old account able to process unsubscribes, because links in emails sent before the cutover still point at it, and move those opt-outs into the new suppression list until the last of them has arrived. Then take a final export of suppressions and engagement history, file it with the register, and close the account. Remove the old platform from the SPF record and retire its DKIM keys only once it has stopped sending; until then, removing it would make its remaining mail fail. Unknown sources that appear in DMARC reports afterwards are diagnosed in the DMARC failing guide.

A cookware shop's platform move (illustrative)

Illustrative example — not a real result

Pansorrel Cookware's migration register

Pansorrel Cookware, an online cookware shop, moves its email to a new platform over six weeks with one marketer, an agency developer for the forms and the owner for DNS. The register at the end of the move:

ItemOwnerOld platformNew platformSwitched
21,400 active contacts with consent source and timestampMarketerExported week 1Loaded week 2 into holdingWeek 6
Suppression files: 2,310 unsubscribes, 640 hard bounces, 230 complaintsMarketerExported week 1Loaded week 2, before contactsFinal export week 6
SPF, DKIM and DMARC alignmentOwnerSigning for shop domainSigning for shop domain, tests passOld DKIM retired week 7
Welcome series, cart, post-purchase and win-back flowsMarketerLiveRebuilt and tested weeks 2 to 3Old flows off week 4
Footer form and checkout opt-inDeveloperPosting to old accountRe-pointed, real sign-ups testedWeek 4
Monthly email reportMarketerPlatform dashboardRebuilt on clicks and ordersWeek 5

The import found 85 addresses in both the active export and the unsubscribe file; they stayed suppressed. The first send in week 4 went to 4,800 subscribers who had clicked in the previous quarter, with 1 complaint and 6 hard bounces. Three further stages over two weeks reached the rest of the list, and complaints per send stayed between 1 and 3. Twelve unsubscribes arrived through the old platform after the cutover and were copied across before the account closed.

Common mistakes

  • Exporting contacts and nothing else. The suppression files, consent records and flow logic are the parts that protect people and reputation, and a contact export carries none of them.
  • Loading contacts before suppressions. For the hours or days in between, people who opted out are ordinary subscribers to the new platform.
  • Signing with the platform's domain. SPF and DKIM pass for the platform, the From address uses the brand, and DMARC fails anyway.
  • Copying saved segments instead of definitions. Old filters carry logic nobody can explain, and counts that differ for reasons nobody wrote down.
  • Both platforms sending at once. The same subscriber receives two welcome emails, or a cart reminder from each, and neither platform's exits know about the other.
  • Forms left on the old account. New sign-ups never reach the new platform and the welcome series never fires.
  • First send to the whole list. A new platform with no history and a full-volume send is the spike the sender guidelines advise against.
  • Closing the old account too early. Opt-outs from emails sent before the cutover have nowhere to go.

When the move is done, the fundamentals hub sets out the hygiene routine that keeps the new platform's list in the state the migration left it.

Frequently asked questions

Do subscribers have to confirm again when we move to a new email platform?

Not because of the move itself. People agreed to hear from the business, not from a particular piece of software, so a consent record that travels with each contact remains the record. What the move exposes is any address whose record is missing or doubtful; those are better sent a re-permission message, or a confirmation step, than imported with everyone else. Rules differ by market and nothing here is legal advice; the list building and consent guide explains what the record should contain.

Should the old and new platforms run side by side?

For sending, as briefly as possible, because two platforms mailing the same people produce duplicate emails and two sets of flows with no shared exits. For receiving, longer: unsubscribe links in emails sent before the cutover still point at the old platform, so it has to keep processing them, and those opt-outs have to reach the new platform before the old account closes. Plan a sending cutover date and a later closing date, and do the final suppression export between them.

Does a new email platform need warming if the sending domain stays the same?

Treat it as a change that mailbox providers can see. The deliverability guide explains that a migration to a new sending platform reads, from the provider's side, like a change in behaviour, and Google's sender guidelines advise against sudden spikes in volume. Start the new platform with the subscribers who engage most, widen the audience in steps while bounces and complaints stay steady, and avoid combining the move with a list import or a new cadence in the same week.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Email sender guidelines — Google Workspace Admin Help
  2. RFC 8058: Signaling One-Click Functionality for List Email Headers — IETF
  3. Direct marketing guidance — Information Commissioner's Office (UK)

Related