How to Move My Subscriber List to a New Email Service Without Losing Contacts or Consent

You've decided to switch newsletter platforms — maybe for pricing, features, or because the old tool became a headache. That's a perfectly normal move. The scary part is a different question: "what happens to my list? Will I lose subscribers? Am I even legally allowed to email them from the new service?"

Good news: if you do the migration properly, you lose no valid contact and no consent. Consent belongs to the relationship between you and your subscriber, not to the platform — but you have to carry the proof of it with you. In this guide I'll show you, step by step, how to export your list cleanly, keep the metadata that matters for GDPR, and avoid the one mistake that can wreck your deliverability on day one of the new service.

What "not losing consent" actually means

Consent isn't a button the platform hands you. It's the agreement your subscriber gave when they signed up — and the proof of that agreement lives in your data, not in the software you use.

Under GDPR, to show you're allowed to email someone, you need a few pieces of information per contact:

• the date and time they subscribed
• the source (a form on your site, a lead magnet, a checkout)
• the IP address used at signup, if you have it
• the text they consented to (what it said next to the checkbox)

As long as you carry these fields into the new platform, consent stays valid. You don't need to re-ask people just because you're changing providers. The problem starts when you export only "name + email" and throw the rest away — then you're left with no proof.

Export the full list, not just names and emails

Almost any serious platform gives you a CSV export. The mistake I see most often is that people tick only the "name" and "email" columns and lose all the context.

Before you export, look in the settings for the option to include all fields:

• each contact's status (subscribed / unsubscribed / bounced)
• signup date and source
• tags, groups, and custom fields
• unsubscribe history

The status column is essential. Never import people who unsubscribed or whose emails bounced back into the new platform. If you re-add them as "active," you're emailing them again without the right — and you damage your sender reputation.

Save the exported file somewhere safe and don't delete it after the migration. It's your consent-proof archive.

Import cleanly and check your field mapping

During import, the new platform will ask which CSV column corresponds to which internal field. This is where data gets lost if you're not careful.

A few practical rules:

• Explicitly map signup date and source into dedicated fields — don't let them fall into "notes."
• Import only contacts with "subscribed" status. Unsubscribed ones, if the platform allows, import separately as "unsubscribed" so you don't email them by accident.
• Don't tick "re-send a confirmation email to everyone" if you already have valid consent — you risk losing people who never reopen the message.

After import, check on a few test contacts that tags and fields landed correctly. It's far easier to fix now, on ten contacts, than a month later when your automations pull from empty fields.

Protect deliverability: authentication and warm-up

Even if the list arrives perfectly, there's one step many people skip and then wonder why their emails land in spam: authenticating your domain on the new service.

Before your first send, set up in your DNS:

• SPF and DKIM for the new provider
• ideally DMARC as well

Without them, the new service sends "on your behalf" with no proof, and Gmail and Outlook get suspicious.

Second thing: don't blast your entire list from a fresh domain on day one. Sender reputation is built gradually. Send first to your most active subscribers, then expand over a few days. That way the new provider earns trust with mailbox providers, and you don't suddenly get flagged as spam.

How we can help, if you'd rather not migrate solo

Migrating a list isn't hard, but it has steps where a single wrong tick costs you — either contacts, deliverability, or your proof of consent. If you have a large list or complex automations, it may be worth having someone who's done it before handle it.

At MPO Web Studio we work remotely, all across the country, and we take care of the technical side without the hassle: clean export, correct mapping of GDPR fields, SPF/DKIM/DMARC setup, and a warm-up plan so you don't lose deliverability. We show you upfront, transparently, what we do and what it costs.

If you'd like, message us on WhatsApp with which platform you use now and where you want to move — we'll tell you honestly whether it's worth doing yourself or whether we should help. No pressure and no exaggerated promises.