Migration field note

Move the system, not just the subscriber CSV.

A newsletter move can look complete while forms, welcome emails or old links are quietly broken. Use this before changing DNS or sending from the new platform.

Four lock-in questions to answer first

Can the audience leave?

Confirm that active contacts, consent records, unsubscribes, tags and custom fields can be exported in a usable format.

Can the archive leave?

Check whether posts, URLs and images can be exported or whether important pages need to be recreated manually.

Who owns billing?

Understand where customer payment details live and what subscribers must do when the billing system changes.

What breaks on day one?

List forms, automations, integrations, DNS records and old links that depend on the current platform.

Do not delete the old account immediately

Keep the old account available until the new signup path, suppression list, sending setup, archive links and billing flow have been verified. Exact retention and migration rules differ by platform; check the provider documentation for your account.

Disclosure

This checklist is platform-neutral. Some beehiiv links elsewhere on Stackgap Atlas are affiliate links and may generate a commission at no additional cost to you. No migration data leaves your browser from this checklist.