How to move a Substack archive without losing its reading history
Decide which posts, subscribers, tags and publication settings deserve migration before rebuilding your newsletter elsewhere.

You have decided to leave Substack. The new storefront is ready, but your old publication contains years of posts, a subscriber list, topic labels and links readers still use. Moving the visible archive is one task. Preserving the route readers take through it, and being clear about what follows them, is another.
Start with an inventory, not an export
Before you move anything, make a list of what exists. Your archive may include free posts, paid posts, welcome emails, drafts, audio, images, downloads, notes about sponsorships and links to products that no longer exist. A single export can contain the words without preserving the decisions around them.
- 1List every published post, with its title, original publication date, URL, topic or tag, and whether it was free or paid.
- 2Mark each post as keep, revise, combine, redirect or retire. Do not carry dead links and outdated promises into a new archive by default.
- 3Record the posts that readers commonly reach through search, bookmarks, email links or a series page. These are the pages where a broken route will be noticed first.
- 4Make a separate list of subscriber data, including consent records, subscription status and any segments you are permitted to use.
- 5Write down publication settings: sender name, reply address, footer text, welcome sequence, paid access rules and any custom domain arrangements.
Decide what ‘reading history’ means
The phrase can describe several different things. Readers may mean the archive’s chronological order, their own bookmarks, a series they are following, or the fact that an old link still opens the expected post. Your analytics may also include views and clicks, but those are records about activity rather than a reader’s personal history.
| What you want to preserve | Practical treatment |
|---|---|
| The archive’s chronology | Keep the original dates visible and use a consistent archive index or series order. |
| Existing post links | Map each old URL to its new equivalent. Test the highest-use links before you announce the move. |
| Series and topics | Recreate the labels only where they help readers find related posts. Fewer useful categories are better than a copy of every tag. |
| Views, clicks and subscriber history | Export and retain the records you are allowed to keep, but do not imply that readers can see the same history in the new system. |
| Paid access | List which posts were paid, what each purchaser was promised and how access will work after the move. |
If you are rebuilding the archive in a storefront, organise the reading path before polishing the design. A simple home page can point to a ‘start here’ post, an archive, a few topic collections and your current offer. On store.fan, the store designer is useful for shaping that front door, while your existing posts can remain the main reading experience elsewhere if that is the less risky choice.
Handle subscribers as permissioned records
Subscribers are not just a spreadsheet of email addresses. For each record, separate the address from the person’s subscription status, consent, source and relationship to any paid product. Keep only what you have a lawful reason to retain, and document where the data came from.
- Export the list before you close or downgrade the old publication.
- Separate active, unsubscribed, bounced and paid subscribers rather than importing them as one audience.
- Do not add people to a new marketing list merely because you once emailed them. Use the permission and purpose attached to the original sign-up.
- Tell active subscribers what is changing, what they need to do and how to opt out. Give the message a clear subject and a plain explanation.
- Send a small test to yourself and a few consenting testers before sending the full migration announcement.
Rebuild the publication in layers
Do not wait until every post is perfect. Build a small working version first: one archive page, one representative post, one topic route, one sign-up path and one paid or product path if those apply. Follow each route as a reader would, on mobile and on desktop.
For a creator selling alongside a newsletter, store.fan can give the publication a home at store.fan/yourusername. The free plan is link-in-bio only; paid plans begin with a 14-day trial. store.fan takes 0% of sales, while Stripe’s own processing fee still applies, and money goes directly to your Stripe account. If the archive leads to a paid guide, you can connect it to digital downloads rather than leaving readers to search for the offer.
For the email part of the rebuild, check exactly which tools you need. Pro adds email marketing, discount codes, flash campaigns, hosted course video and creator-run affiliate programmes. The email marketing feature may suit a publication that needs campaigns and follow-up, but it does not remove the work of cleaning your imported records or confirming permission.
Test the reader’s route before you publish the move
Choose five to ten old posts that represent the archive: an early post, a popular post, a post in each important series, a paid post and one with images or downloads. Open the old link, follow the new route, check the date and read the whole page. Then test the sign-up, confirmation, product delivery and unsubscribe paths.
- Check that headings, images, captions, embeds and links survived the copy.
- Check that dates and series order tell the same story as the old archive.
- Check that a reader can move from an old post to the next relevant post without needing private knowledge.
- Check that retired posts do not leave a blank page or an unfulfilled promise.
- Check that your sender name, reply address and footer identify the new publication clearly.
Announce the change without pretending nothing changed
Your announcement should say where the archive now lives, what happens to future emails, whether readers need to confirm anything and how they can contact you. Link to the new start-here page, not only to the storefront home page. Keep the old publication available for a transition period if you can, with a notice pointing readers to the new address.
Do not assume that you can. You may be able to export or copy content, but formatting, media, URLs, tags, paid access and email history can require separate work. Inventory the archive first and test a representative sample.
Not safely as a blanket assumption. Export the records you are allowed to use, separate their statuses and check the permission attached to each audience. Explain the change and provide a clear opt-out route.
Only if it still helps the reader and you have the rights and resources to maintain it. A smaller, edited archive with clear dates and series links can be more useful than a complete copy full of broken links or outdated advice.
Build the new reader route, then test it before you invite your archive across.
Start your trialTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



