Which platforms import past posts
beehiiv has a Content Import tool under Settings. Its Substack guide says free posts import from your publication URL, paywalled posts need your Substack export ZIP, and a migration usually takes 5 to 10 minutes. [1] Its Ghost importer connects through a Ghost Content API key and URL, and because that API only exposes public content, paywalled posts must be set to public temporarily. [2] Its Mailchimp importer connects to your Mailchimp account and imports campaigns built with the New Email Builder; campaigns made with the Legacy Email Builder are not imported. [3]
The MailerLite and Kit pages we read describe recreating content rather than importing it. MailerLite's Substack migration guide covers subscribers, forms, landing pages, templates and automations, with no step for past posts. [5] Kit's archive guide has you recreate each past newsletter as a Broadcast, set its published date to match the original, and publish it to the web without sending it. [6]
| Destination | How past posts arrive | Known gaps |
|---|---|---|
| beehiiv from Substack | Content Import: URL for free posts, export ZIP for paid [1] | Video, podcast, comments, categories, galleries; paywall placement [1] |
| beehiiv from Ghost | Content Import via Ghost Content API key [2] | Paywalls, comments, code blocks; internal links may break [2] |
| beehiiv from Mailchimp | Content Import via Mailchimp login [3] | Legacy Email Builder campaigns not imported [3] |
| MailerLite | No importer in the migration guide; archive block shows MailerLite campaigns [5] [4] | Past posts must be rebuilt or left on the old site |
| Kit | Recreate each issue as a Broadcast with a backdated published date [6] | Manual; redirects not covered [6] |
Decide what is worth moving
A full import is only free when there is an importer. If there is not, rebuilding a few hundred issues by hand is a real project, and you should cut the list down first. MailerLite's newsletter archive block, for example, displays up to 50 newsletters, chosen from campaigns sent in your MailerLite account, so an older back catalogue will not appear there anyway. [4]
Start from data rather than habit. Pull your top-traffic posts from analytics or server logs; Google's site move guidance suggests building the URL list from sitemaps, top-traffic URLs and the links report in Search Console. [7] Posts that still bring in readers or backlinks are worth recreating with redirects. The rest can stay in a downloadable archive or be dropped.
Keeping old URLs working
The cleanest case is when the URL pattern does not change. beehiiv says it uses the same /p/ structure as Substack, so pointing your custom domain at beehiiv keeps post links working without manual redirects. [1] Ghost is different: beehiiv says it adds /p/ to post URLs and that backlinks to past posts will not work unless bulk 301 redirects are configured. [2]
Google recommends server-side permanent redirects, such as 301 or 308, from each old URL to its mapped new URL, kept for as long as possible and generally at least a year. [7] Redirect straight to the final destination, keep any unavoidable chain to three hops or fewer, and update internal links in the moved posts to the new URLs. [7] Plan changes matter too: MailerLite says cancelling a paid subscription removes access to custom domains, and your sites stay on the default MailerLite URL. [9]
Redirect map template
Keep one row per old URL. The Status column records your decision and the Checked column records when you last confirmed the redirect returns the right code and lands on the right page. Google's guidance includes images and other assets in the mapping, so add rows for downloadable files that were linked from posts. [7]
| Old URL | New URL | Decision | Redirect code | Checked |
|---|---|---|---|---|
| news.example.com/p/pricing-guide | news.example.com/p/pricing-guide | Move, same path | None needed | 2026-10-30 |
| example.com/blog/welcome-issue | news.example.com/p/welcome-issue | Move, path changed | 301 | 2026-10-30 |
| example.com/blog/2023-roundup | news.example.com/p/best-of-2023 | Merge into newer post | 301 | 2026-10-30 |
| example.com/blog/old-giveaway | news.example.com/archive | Retire, nearest page | 301 | 2026-10-30 |
| example.com/files/checklist.pdf | news.example.com/files/checklist.pdf | Re-host file | 301 | 2026-10-30 |
Images after you cancel the old account
beehiiv's Substack and Ghost importer articles do not explain whether images in imported posts are copied to beehiiv or keep loading from the old host. [1] [2] That is the question to answer before you cancel. Open a sample of imported posts, inspect a few image addresses, and check which domain they load from. If they still point at the old platform, re-upload them to the new one or to storage you control.
Do the same for files readers downloaded from posts, such as PDFs and worksheets, and for embedded audio and video. beehiiv's Substack guide already says video and podcast posts are not migrated and must be recreated separately. [1]
Archive move checklist
Work through this before switching your domain and again before cancelling.
- Export all post content and keep a copy outside both platforms. [8]
- List every old URL from sitemaps, analytics and backlink reports. [7]
- Set your default post style before importing; beehiiv says styling can only be changed post by post afterwards. [1] [2]
- Restore paywalls on paid posts, since importers drop paywall placement. [1] [2]
- Fix internal links between posts to the new URLs. [2] [7]
- Add 301 redirects for every changed path and test each one. [7]
- Check image and file hosts on a sample of posts.
- Keep redirects live for at least a year. [7]
Questions before you decide
Can MailerLite import my old Substack or beehiiv posts?
Its Substack migration guide covers subscribers, forms, landing pages, templates and automations, with no step for past posts. MailerLite's newsletter archive block shows up to 50 campaigns sent from your MailerLite account.
Do my Substack post links keep working after moving to beehiiv?
beehiiv says it uses the same /p/ post URL structure as Substack, so if you point your custom domain to beehiiv you do not need to set up redirects manually for posts.
What does beehiiv's Ghost importer not bring across?
beehiiv lists paywall placement, comments and code blocks as not migrating, says internal post links may break, and notes that old backlinks will not work unless you set up bulk 301 redirects to the new /p/ URLs.
How long should redirects stay in place?
Google recommends keeping redirects for as long as possible, generally at least one year, and pointing each old URL straight to its final destination rather than through a chain.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- beehiiv: How to migrate from Substack to beehiiv Accessed 30 Oct 2026
- beehiiv: How to migrate from Ghost to beehiiv Accessed 30 Oct 2026
- beehiiv: How to migrate from Mailchimp to beehiiv Accessed 30 Oct 2026
- MailerLite: Newsletter archive Accessed 30 Oct 2026
- MailerLite: Migrate from Substack Accessed 30 Oct 2026
- Kit: How to migrate your newsletter archive to your Kit Newsletter site Accessed 30 Oct 2026
- Google Search Central: Site moves with URL changes Accessed 30 Oct 2026
- beehiiv: Exporting post content or subscriber data Accessed 30 Oct 2026
- MailerLite: Cancel my subscription Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.