Kit’s official migration guide is explicit about what is recreated and what is not. The safest plan is to move free subscribers and public archive content first, then handle paid subscriptions as a separate customer-communication project.
Free newsletter migration
Export the Substack subscriber CSV, recreate the profile and Newsletter Site in Kit, and import subscribers into a tag or other deliberate destination. Kit’s docs recommend confirming that you have permission to email every imported subscriber.
Archive migration
Kit documents recreating previous posts as Broadcasts, publishing them to the web, and changing their dates to match the old archive. Treat this as a selective archive rebuild rather than a reason to import every historical post.
Paid subscription warning
Kit’s current guide says there is no convenient way to migrate paid Substack payment details. The documented workaround involves cancelling old subscriptions and asking readers to resubscribe, so do not describe this as a one-click migration.
Use this checklist
- Export free and paid subscriber CSVs separately.
- Confirm permission to email the imported list.
- Tag paid subscribers before any automated sequence can run.
- Recreate only the archive posts worth keeping.
- Plan paid-subscription re-enrolment and refund communication separately.
Read the official product information
These are direct canonical links. Pricing, plan boundaries, and program terms can change; confirm them at the source before you act.