Moving an email list sounds like a file transfer. Download a CSV from the old tool, upload it to the new one, done by lunchtime. That is the version everyone imagines, and it is the version that gets people into trouble, because the addresses are the easy part. What breaks a migration is everything attached to those addresses that does not fit in one file.
This is the practical order of operations: what to export, what to clean, what to import, and what to send first. It applies whichever direction you are moving.
Export two files, not one
Almost every platform splits your people across more than one export. The one you notice is your active subscribers. The one that matters just as much is everyone who opted out.
Mailchimp is the clearest example: its audience export is a zip containing separate files for subscribed, unsubscribed and cleaned contacts. Most tools do some version of this. If you unzip that folder, grab the subscribed file and get on with your day, you have just left your entire opt-out history behind.
So export both files, and keep the unsubscribe file somewhere you will not lose it. On a platform that has a suppression or blocked list, that file is the first thing you upload, before your contacts. On one that does not, you are stuck manually keeping those addresses out of every import forever, which is a good reason to prefer a platform that has one.
Clean the list before you import it, not after
A list that has been sitting in an old tool for a few years is not the list you think it is. People change jobs and their work address dies. Domains lapse. Somebody typed gmial.com in 2023 and nobody noticed. None of that is visible in a spreadsheet, and all of it turns into bounces the first time you send.
Three passes, in increasing order of effort:
- Obvious junk. Rows with no @ sign, two addresses jammed in one cell, a name where the email should be. Sort the column alphabetically and the garbage clusters together.
- Dead domains. An address can be perfectly spelled and still be undeliverable because the domain no longer accepts mail. A platform that checks this for you at import time is doing real work; if yours does not, this is the pass that costs you the most bounces.
- Role addresses. info@, admin@, support@. These are real mailboxes, often the right business contact, and also the ones most likely to mark you as spam because several people read them and none of them personally signed up. Keep them if they matter to you, but know what they are.
Resist the urge to buy a validation service on the way in. For a normal coaching or community list, syntax plus a domain check catches the systematically bad rows, and the per-address services mostly charge you to confirm what your first send would tell you for free.
Bring the context, not just the addresses
The addresses are the least valuable thing in the export. What makes a list worth money is knowing who these people are, and that lives in columns people routinely drop on the way across:
- Tags or groups.The difference between "3,000 subscribers" and "400 people who attended the workshop". Map this column even if you are not sure you will use it; re-deriving it later is impossible.
- Signup date. Lets you email the recent, engaged half first instead of blasting everyone at once.
- Status. Subscribed, unsubscribed, cleaned, bounced. If your file has it, the new platform should read it rather than treating every row as a fresh opt-in.
- First and last name. Split across two columns in almost every export, and quietly truncated to the first name by importers that only map one.
Import in one pass you can undo
Before you upload anything, find out two things: whether the import shows you what it is going to do before it does it, and whether you can reverse it. A preview that says "4,812 will import, 188 skipped, here is why" lets you catch a bad column mapping while it is still free to fix. An import you cannot undo means a mistake is permanent, and the usual mistake, mapping the wrong column, is one you make in the first thirty seconds.
Tag the whole file as you import it, with something like mailchimp-august. It costs you one field and it means that six months from now you can still answer "where did these people come from?" without guessing.
What to send first
Do not make your first send on a new platform a launch. Send something small, useful and unmistakably from you, to your most recently active people first. You are doing two things at once: reminding an audience who you are before you ask them for anything, and giving yourself a cheap read on deliverability while the stakes are low.
Watch bounces and complaints on that first send. A bounce rate that spikes means your cleaning pass missed something. Complaints mean the list is colder than you thought, or the unsubscribe file did not make it across. Both are much easier to fix on a 300-person send than on a 4,000-person launch.
The mistake worth naming twice
If you take one thing from this: the unsubscribe file is not optional. Every other mistake here costs you some deliverability and a bit of embarrassment. Mailing people who already opted out is the one that is both a legal problem and the one your audience actually notices, because being emailed after you asked someone to stop is a specific kind of insult.
If you are choosing where to move, this is a fair question to ask before you pay anyone: can I upload my opt-out list, and will you keep honouring it if those addresses show up again later? A platform that cannot answer yes is one where this problem is now permanently yours. The companion piece, if you cannot leave, you do not own your list, has the rest of that checklist, and own your audience makes the case for why the list is the asset in the first place.
Questions coaches ask
Will I lose my subscribers if I switch platforms?
No, if you export properly. Your subscribers are email addresses, and every serious platform lets you download them as a CSV. What people actually lose in a migration is not the addresses, it is the CONTEXT: who unsubscribed, who bounced, when each person joined, and which tags they carried. Those live in separate exports or separate columns, and skipping them is what turns a clean list into a spam problem on the new platform.
Do I need to re-confirm subscribers after moving platforms?
Usually no, and re-confirming often costs you more than it saves. Consent belongs to you, not to the tool that collected it, so a list you gathered legitimately stays legitimate when you move it. The exception is a list you cannot vouch for: bought, scraped, inherited, or so old you cannot say where it came from. Re-confirming a list like that is worth the losses, because sending to it is worse.
What is the unsubscribe file and why does it matter?
Most platforms export your active subscribers in one file and the people who opted out in another. If you import only the first file, everyone who unsubscribed from you becomes a fresh, subscribed contact on the new platform, and your first send goes to people who already told you to stop. That is a legal problem in most jurisdictions and the fastest way to collect spam complaints, which follow your sending reputation, not the platform's.
How long should I wait before emailing a freshly imported list?
Send something within a few days, not a few months. A list that has not heard from you in a year is a list where addresses have gone dead and people have forgotten they signed up, and both show up as bounces and complaints. If the list is genuinely cold, warm it up in stages: start with your most recently active people, watch the bounce and complaint rates, and widen only if those stay healthy.
Does Drry let me import and export my list?
Yes, both, on every plan including free. Import takes a CSV and maps the columns for you, checks every address before it lands, and reads a status column so anyone who unsubscribed in your old tool goes to your blocked list instead of being imported. Export gives you the whole audience or any segment, plus your blocked list, whenever you want. We make Drry, so weigh that accordingly, but the behaviour is public and you can test it on the free plan.