In short
  • Inventory everything the old platform does, including what you take for granted.
  • Export every subscriber with their status. Unsubscribes, bounces and complaints move to the new suppression list, never the send list.
  • Treat paid members as a separate project. Stripe can copy customers and cards between accounts, but not subscriptions.
  • Redirect every old archive URL one to one with permanent redirects, and keep them for at least a year.
  • Authenticate the new sending domain before the first send, then warm up from your most engaged readers out.
  • Pause automations before you import, or the import itself can trigger them.
  • Keep the old platform running, and keep a written rollback plan, until the new one has sent cleanly.

Illustrative example. Figures are fictional.

The shape of a safe migration

Every migration has the same five phases. Skipping one does not save time. It moves the work to the week after cutover, when readers are watching.

PhaseWhat happensDone when
AuditInventory lists, payments, archive, automations, forms and integrationsEvery item has an owner and a destination
BuildImport data, set up the domain, rebuild templates and flowsCounts reconcile and test sends pass authentication
Warm-upSend to engaged readers first, widen step by stepThe full list receives mail with steady bounces and complaints
CutoverSwitch forms, DNS, billing and redirects to the new platformNothing new lands on the old platform
MonitorWatch delivery, signups, payments and search trafficSeveral issues sent cleanly and the old account can close

If you are still deciding where to go, settle that first. Our guide to choosing a newsletter platform covers the tradeoffs.

1. Inventory everything first

List what lives on the current platform. The forgotten items are the ones that break.

  • Audience: subscribers, every custom field, tags, segments and subscription status.
  • Money: paid tiers, coupons, comped readers, gift subscriptions and the Stripe account behind them.
  • Content: the archive, images, author pages and any paywalled posts.
  • Automations: welcome series, re-engagement flows, referral rewards and anything triggered by a tag.
  • Entry points: embedded forms, landing pages, pop-ups, link-in-bio pages and partner sites.
  • Integrations: webhooks, Zapier steps, analytics, ad tools and anything reading the platform's API.
  • DNS: every record the old platform asked you to add.

How to check it: search your codebase and website for the old platform's domain and form URLs. Then read your DNS zone line by line. Anything you cannot explain goes on the list.

2. Export subscribers with their status

A list of email addresses is not an export. You need each reader's status, signup date, source and fields. Status is the part that protects you.

Each platform exports differently. Mailchimp can give you a ZIP with separate CSV files for subscribed, unsubscribed, non-subscribed and cleaned contacts. Cleaned contacts are addresses that hard bounced or repeatedly soft bounced. Beehiiv offers a basic export and a full export from Settings, Export Data, and the full one adds custom fields and statistics. Its download links expire after 24 hours. Substack exports subscribers as a CSV from the Subscribers page, and the full publication export from Settings, Exports.

Then map every status to the new platform before you import.

Status on the old platformWhat it meansWhere it goes
ActiveCurrently receiving the newsletterImport as subscribed, with signup date and source
UnsubscribedAsked to stopSuppression list only
Bounced or cleanedAddress failed permanentlySuppression list only
ComplainedMarked an issue as spamSuppression list only
UnconfirmedNever completed double opt-inLeave out, or confirm again from the new platform

The FTC's CAN-SPAM guidance says opt-outs must be honored within 10 business days, and that opted-out addresses cannot be sold or transferred, except to a company you hired to help you comply. A migration does not reset anyone's choice. If the new platform cannot hold a suppression list, keep one yourself and filter every import against it.

A fictional worked example: your export has 41,200 rows. 37,800 are active, 2,600 unsubscribed and 800 cleaned. After import, the new platform should show 37,800 subscribed and 3,400 suppressed. If it shows 38,100 subscribed, 300 people who left are about to hear from you again. Find them before the first send.

How to check it: reconcile counts by status, not in total. Then spot check ten addresses you know: one active, one unsubscribed, one bounced, one paid.

3. Bring consent along, not just emails

Export when and how each reader subscribed: date, form, source and confirmation status. Under the GDPR, where processing is based on consent, you must be able to demonstrate that the person consented. A bare address list cannot do that.

Keep the raw exports somewhere safe and dated. They are your record of what the list looked like the day you left.

4. Plan paid subscriptions as their own project

Paid members are the riskiest part of any move. A mistake here does not cost opens. It charges someone twice, or stops charging them at all.

Start with one fact: Stripe can copy customers and their saved payment methods from one account to another, but it does not copy subscriptions, invoices, plans or coupons. Those get recreated on the other side. Whether you need a copy at all depends on whose Stripe account holds the data.

  • Same Stripe account: the simplest case. Ghost's Substack migrator asks you to connect the same Stripe account that is connected to your Substack, then imports paid members against it.
  • A Stripe account you cannot take with you: Ghost's own migration docs note that the Stripe account associated with a Beehiiv site cannot be connected to another platform, so paid subscribers there do not move easily.
  • Moving into Beehiiv: its paid subscriber migration copies card data into your Beehiiv-connected Stripe account, which can take up to 72 hours. Migrated readers keep their current price and sit on a temporary trial until their renewal date.

In every case, the old billing does not stop by itself. Beehiiv's Substack guide tells you to pause or cancel paid subscriptions on Substack after migrating to prevent double billing. Pause billing on the old side before the new side charges anyone.

Do not click Disconnect Stripe on Substack. Substack's help center says disconnecting Stripe there refunds and cancels all paid subscriptions and notifies your paying readers. If you are moving platforms, ask Substack support for help first.

Tell paying readers before anything changes. One short email: what is moving, when, and that their price and renewal date stay the same, if they do.

How to check it: after import, pick five paying readers and compare the old and new records: plan, price, next renewal date and card on file. Then confirm the old platform shows billing paused for the same five.

5. Move the archive and redirect every URL

Old issues sit in search results and in readers' inboxes. Move them to the new platform, or republish them as a fast archive on your own domain. Then redirect.

Google's site move guidance is direct. Use server-side permanent redirects, such as 301 or 308. Keep them as long as possible, generally at least a year. Map each old URL to its own new page. Sending everything to the homepage can be treated as a soft 404.

URL patterns differ by platform. Substack and Beehiiv both put posts under /p/. Ghost does not, and its migration docs give a regex redirect that sends /p/your-post to /your-post.

How to check it: pull every post URL from the old sitemap. Request each one and confirm it returns a single 301 to the right page, not a chain and not the homepage. After cutover, watch the Pages report in Search Console for new not-found errors.

6. Authenticate the new sender before the first send

Configure SPF, DKIM and DMARC for the new platform before you send anything. Our deliverability checklist covers each record.

  • SPF: add the new platform to your existing record. Do not publish a second record. Leave the old platform in until you close it, since Gmail asks that your SPF record include every sender for your domain.
  • DKIM: publish the new platform's keys so it signs with your domain, not its own.
  • DMARC: keep your policy, and read the aggregate reports to confirm the new sender passes and aligns.
  • Tracking and unsubscribe: set up custom link domains and confirm one-click unsubscribe works on the new platform.

How to check it: send a test to a Gmail address and open Show original. SPF, DKIM and DMARC should all read PASS, with your domain next to DKIM.

7. Warm up the new sender

Mailbox providers judge new sending patterns closely. Gmail's sender guidelines say to start with a low volume to engaged users and increase it slowly, and to avoid sudden spikes if you have no history of large volumes. After significant infrastructure changes, they advise ramping the changed traffic separately.

StepWho receives the issueMove on when
Week 1Readers who clicked in the last 30 daysBounces and complaints sit in your usual range
Week 2Add readers who clicked in the last 90 daysNo new deferrals at Gmail, Outlook or Yahoo
Week 3Add everyone active in the last six monthsClicks per send hold steady
Week 4Full active listTwo clean sends in a row

Illustrative example. Figures are fictional.

During warm-up, readers not yet moved keep receiving the issue from the old platform, so nobody misses an edition. Hold a step if any signal gets worse.

8. Rebuild automations, forms and integrations

Recreate each automation from the inventory, then test it with a real address you control. Watch the order of operations. Kit warns that adding imported subscribers to tags or forms may trigger automations using them, and that adding them to an active sequence starts the sequence. Other platforms behave similarly. Pause automations before the import, and turn them on deliberately afterward.

Point every signup form at the new platform. Then submit each one and confirm the reader lands with the right tags and receives the welcome email.

Rewire integrations last, once the data is settled. A webhook pointed at an empty list does damage quietly.

9. Run cutover day from a script

Pick a quiet week, not the week of a big sponsor or a launch. Freeze changes on the old platform the day before. Then work through a written runbook.

  1. Final delta export. Export signups, unsubscribes and bounces since the main import, and apply them.
  2. Reconcile counts by status one last time.
  3. Switch forms and any API integrations that add subscribers.
  4. Switch DNS for the archive and custom domain, then confirm redirects return 301.
  5. Pause billing on the old platform if paid members moved.
  6. Send a test issue to internal addresses at Gmail, Outlook and Yahoo, and check authentication.
  7. Send the first real issue from the new platform to the current warm-up segment.
  8. Leave the old account open. Do not delete anything.

Name one person who owns the runbook. Everyone else asks them before touching a setting.

10. Monitor the first two weeks

  • Every send: bounces, complaints and deferrals by mailbox provider, compared with your old platform's range.
  • Daily: new signups. A flat line means a form still points at the old platform.
  • Daily: unsubscribes processed on the new platform, and none still arriving on the old one.
  • On renewal dates: each paid reader charged once, at the right price.
  • Weekly: Google Postmaster Tools spam rate, DMARC reports and Search Console not-found errors.

11. Write the rollback plan before you need it

Most migrations never use it. The ones that do need it written down in advance, not drafted at 7 a.m. on send day.

  • Trigger: what would make you roll back. A complaint spike, a blocklisting, broken billing.
  • Path back: the old platform stays paid for and able to send until several issues have gone out cleanly.
  • Data: how signups and unsubscribes collected on the new platform get copied back, so nobody who left is emailed again.
  • Billing: who resumes old billing, and how you avoid charging anyone twice.

Platform-specific gotchas

PlatformWatch for
BeehiivExport download links last 24 hours. Suppressed addresses are accepted on import and filtered at send time, so counts can look higher than who actually receives mail. Ghost notes its Stripe account cannot connect to other platforms.
SubstackDisconnecting Stripe in Substack refunds and cancels paid subscriptions. Pause billing there after migrating to avoid double charges.
GhostThe Substack migrator needs the same Stripe account. Member CSVs accept a stripe_customer_id column, which can be set to auto to match by email. Old /p/ URLs need a redirect rule.
KitImports into tags, forms or sequences can start automations. Readers who previously unsubscribed in Kit stay cancelled when re-imported.
MailchimpExports split subscribed, unsubscribed, non-subscribed and cleaned contacts into separate files. Import the first and suppress the rest.

Platforms change their tools often. Check each one's current migration docs before you start.

What most guides miss

Lessons from systems we have built and run, not the usual checklist.

Migrate consent, not just emails

Bring across when and how each reader subscribed. If you ever need to prove consent, a bare email list is not enough.

Reconcile by status, not by total

Totals can match while the wrong people sit in the wrong bucket. Unsubscribed readers emailed after a move are the fastest route to complaints on a brand new sender.

Warm up with your best readers first

Start sending to the most engaged segment so mailbox providers see clicks and replies, then widen. Sending to everyone on day one is the fastest way to the spam folder.

Redirect every old archive URL

Old issues sit in search results and in readers' inboxes. Map each old URL to its new home with permanent redirects, or you lose the traffic and the trust.

Do not forget the forms you forgot

Embedded signup forms on old landing pages, partner sites and link-in-bio pages keep sending readers to the old platform. Find them and update them before you turn it off.

Old engagement history does not come with you

Most imports bring addresses and fields, not years of opens and clicks. Export engagement before you leave, and build your warm-up segments from it. Once the old account closes, it is gone.

How we do it

We moved a B2B trade newsletter, three issues a week with one operator, from Beehiiv to its own Resend-based infrastructure. That covered the full archive on its own domain, authentication, webhook-driven suppression of bounces and complaints, and rebuilt signup and reporting. See platform migrations or the case study.

Not sure what your current setup depends on? Start with a process audit before anything moves.

Sources

  1. Mailchimp Help: View or export your contacts
  2. Beehiiv Help: Exporting post content or subscriber data from beehiiv
  3. FTC: CAN-SPAM Act compliance guide for business
  4. EUR-Lex: Regulation (EU) 2016/679 (General Data Protection Regulation)
  5. Stripe Documentation: Copy customer and payment method data across Stripe accounts
  6. Ghost Developer Docs: Migrating from Substack
  7. Ghost Developer Docs: Migrating from beehiiv
  8. Beehiiv Help: How to import paid subscribers
  9. Substack Help: How do I turn off paid subscriptions on Substack?
  10. Google Search Central: Site moves with URL changes
  11. Gmail Help: Email sender guidelines
  12. Kit Help Center: How to import a subscriber list

Facts checked against these sources in October 2026.