solobuild
Moving an email list sounds like a file transfer. You export a CSV from the old tool, upload it to the new one, repoint your signup forms, and cancel the old subscription. Most of the list does arrive. The part that goes wrong is quieter, and you usually notice it two or three weeks later, when your open rate has dropped by a third and someone replies asking why they got an email they unsubscribed from last year.
That second problem is the one that costs you. A migration rarely deletes subscribers outright. What it does is break the invisible layer around them: the record of who already opted out, who has been ignoring you for a year, which tag decided which sequence they got, and the reputation your sending domain built up at Gmail over time. Rebuild that layer badly and the list is technically intact while performing far worse than it did before. Here is how to move a list so the number in the dashboard and the number of people actually reading you both survive.
What actually breaks when you switch email platforms
Subscriber records are the easy part. Every platform exports email addresses and every platform imports them, so the raw contact count usually transfers cleanly. The failure modes live in everything attached to those addresses.
The most damaging one is the suppression list. Your old platform has been quietly holding a set of addresses that unsubscribed, hard bounced, or marked you as spam, and that list almost never rides along in a normal contact export. If you export only your active subscribers and import them, you are fine. If you export everything and import it in one pass without marking status, you just resurrected every person who told you to go away. Emailing them again generates complaints fast, and complaints are the single fastest way to damage a new sending setup.
Tags, custom fields, and signup dates are the next layer down. These do transfer, but only if you deliberately include them as columns in the export, because most default exports give you email address, first name, and not much else. Lose them and your segments have to be rebuilt from memory, which usually means they never get rebuilt at all. Automations are worse, since almost nothing transfers between platforms automatically. You are rewriting those by hand no matter which tool you land on, so plan for it rather than discovering it on cutover day.
Then there is sender reputation, which is the part people underestimate. Inbox providers judge you partly on the infrastructure sending your mail, and a new platform means new sending servers with no history of you on them. Your domain reputation carries over if you keep the same sending address, but the combination of your domain and their servers is brand new. Sending your entire list on day one from that new combination looks, from Gmail's side, a lot like what a spammer does.
Clean the list before you export a single row
The instinct is to move everyone and sort it out later. Do the opposite, because whatever you carry over becomes the first impression your new setup makes. Migrating with dead addresses and long-inactive contacts means you start rebuilding reputation with the worst possible signals, and you have no history on the new platform to absorb the damage.
Start by pulling a report of everyone who has not opened or clicked anything in roughly the last six months. Send that group one honest email asking whether they still want to hear from you, with a single obvious link to stay subscribed. Give it a week. Anyone who does not respond gets unsubscribed on the old platform before you export, which means they never enter the new one at all.
Do the same with soft bounces, which are temporary delivery failures like a full mailbox. One soft bounce means nothing. Six in a row from the same address usually means the mailbox is abandoned, and abandoned mailboxes eventually get recycled into spam traps. Pull those out too. It feels like throwing away subscribers, but you are throwing away addresses that were already not reading you, and the smaller number will perform better than the bigger one did.
Export more than the email addresses
When you run the export, treat it as two separate files rather than one. The first file is your active, engaged subscribers with every column you care about attached: email address, first name, any custom fields, the date they subscribed, and their tags or list membership as their own column. Tags survive a migration perfectly well as long as they exist in the CSV, so spend the extra ten minutes getting the export settings right instead of running the default export and hoping.
The second file is your suppression list: unsubscribes, hard bounces, and complaints. Most platforms keep this somewhere separate from the main contact view, sometimes under a name like cleaned, bounced, or unsubscribed. Export it, then import it into the new platform as suppressed or unsubscribed contacts before you import anything else. Doing suppression first means that if a stale address somehow appears in your main file too, the new platform already knows not to mail it.
Everything that is not a contact needs to be captured manually. Take screenshots or write out the logic of every automation, every form, and every email template you still use. Note which integrations touch your list, since a Zapier connection or a checkout tool pushing new buyers into your old account will keep pushing after you move if you forget it exists. This part is tedious and there is no shortcut, but it is also the part that prevents a form quietly collecting subscribers into an account you cancelled.
The cutover: authentication, forms, and a deliberately slow first send
Before you send anything from the new platform, set up domain authentication. Your new tool will give you SPF, DKIM, and DMARC records to add to your DNS settings, which are the entries that tell inbox providers this platform is allowed to send on your behalf. This stopped being optional a while ago. Since February 2024, Google and Yahoo have required bulk senders to have DMARC in place along with one-click unsubscribe and a spam complaint rate under 0.30%, and by late 2025 non-compliant mail started getting rejected rather than filed into spam. Anyone sending 5,000 or more messages a day to Gmail addresses gets classified as a bulk sender, and the classification sticks even if your volume later drops.
Keep your sending address exactly the same as it was on the old platform. If your list has been receiving mail from hello@yourdomain.com for two years, keep sending from hello@yourdomain.com. Changing the tool and the from address in the same week doubles the amount of unfamiliarity you are asking both the inbox provider and the reader to absorb.
Then send slowly, starting with the people most likely to open. A reasonable ramp for a list under about 20,000 looks like this.
| Week | Who you send to | What you are watching |
|---|---|---|
| Week 1 | Top 10 to 20% most engaged | Bounce rate, spam complaints, delivery errors |
| Week 2 | Top 40 to 50% most engaged | Open rate holding near your old benchmark |
| Week 3 | Full engaged list | Complaint rate staying well under 0.30% |
| Weeks 4 to 6 | Normal sending resumes | Whether numbers stabilize or keep sliding |
Keep your usual frequency during this period. If you have always sent weekly, send weekly, because a sudden change in cadence is itself a signal that something about the sender changed. Plan on roughly 30 to 45 days before the numbers settle into a new normal, and resist the urge to declare the migration a failure after one underperforming send.
The last piece is your front door. Update every signup form, landing page, embedded widget, and integration to point at the new platform, then actually test each one by subscribing yourself with a real address. Leave the old account open and paid for at least one full billing cycle after the cutover so you can go back and check something you forgot to export. Cancelling on the same day you migrate saves you about twenty dollars and removes your only safety net.
When to hand the migration to the platform instead
Most platforms will do the move for you, and for a solo operator that is often the better trade even though it means committing to a paid plan sooner than you planned. Kit includes migration with every paid plan and splits it into two tiers. Under 10,000 subscribers you get an essentials migration covering subscribers, tags, lists, and segments, typically inside two to five business days. Above 10,000 subscribers the concierge tier adds forms, automation emails, email templates, and integrations like Zapier, ClickFunnels, and Kajabi. Kit's free plan supports up to 10,000 subscribers, but the migration help sits behind a paid plan, so the practical move is to start paid, get the migration done, and reassess later.
GetResponse runs a more consultative version. You fill out a survey describing what needs to move, book a discovery call with a customer success agent, and they build a migration plan around your setup before executing it. That structure suits people with messy accounts, several lists, and automations they cannot cleanly describe in a support ticket. Their paid plans start at $19 per month for 1,000 contacts on the Starter tier, and the free plan is capped at 500 contacts and 2,500 emails per month, so it works for testing the interface but not for landing a real list.
The honest version of the decision is that a done-for-you migration handles the mechanical work and none of the judgment. Nobody at either company is going to tell you that 4,000 of your 9,000 subscribers have not opened anything since 2024. The list cleaning, the re-engagement email, and the slow ramp are still yours, and they matter more to the outcome than who uploads the CSV. If you do the cleanup and let them handle the transfer, you get the best split of the work.
Frequently asked questions
Will I lose subscribers when I switch email marketing platforms? Not mechanically. A properly mapped import moves every active contact, and both Kit and GetResponse verify counts as part of their migration process. What you will lose is anyone you deliberately remove during cleanup, plus a slice of people who quietly stop opening because your first few sends from the new platform land in the promotions tab or spam folder. That second group is the one the slow ramp is designed to protect.
Do I have to make people resubscribe when I move to a new email platform? No, and you should not. Consent belongs to you, not to the tool, so as long as those people opted in to hear from you originally, that permission travels with the list. Running a resubscribe campaign typically loses you 60 to 90% of your list for no compliance benefit. The only situation where re-permissioning makes sense is a list you did not build yourself or one you have not emailed in well over a year.
How long does an email list migration take? A small, clean list with no automations can move in an afternoon. A realistic timeline for a working solo business is two to four weeks end to end, because the list cleaning takes a week on its own and the sending ramp takes another two or three. Platform-run migrations usually quote two to five business days for the data transfer itself, which is only one step inside that longer window.
Will my open rates drop after switching email providers? Usually yes, temporarily. A dip of a few percentage points across the first several sends is normal while inbox providers reassess your mail from unfamiliar servers. It should recover within 30 to 45 days if your authentication is correct and your complaint rate stays low. A drop that keeps deepening past six weeks is a signal that something is misconfigured, most often a DKIM or DMARC record that was added incorrectly.
The short version
Treat the contact list as the least fragile thing you are moving. The suppression list, the tags, and your standing with Gmail are the parts that actually decide whether the migration works, and all three are lost through carelessness rather than through anything the platforms do wrong. Clean first, export in two files with suppression imported ahead of everything else, authenticate before your first send, and ramp back to full volume over three weeks rather than one day.
If you want the transfer handled for you, Kit's included migration is the simpler path for most solo builders, particularly under 10,000 subscribers where it is fast and covers the segmentation that matters. GetResponse fits better when your existing setup is complicated enough that a conversation beats a form. Either way, do the list cleaning yourself before you hand anything over, and give the whole project a month on the calendar instead of an afternoon.