How to Migrate from Substack to WordPress (Without Losing Subscribers or SEO)

To migrate from Substack to WordPress without losing subscribers, export your posts and subscriber list from Substack, import the posts with the free Substack Importer plugin, and load the subscriber CSV into a WordPress email tool. Move paid readers through Stripe without pressing Substack’s Disconnect Stripe button, which refunds and cancels every paid subscription. A custom domain and one redirect rule for Substack’s /p/ post addresses keep your old links working.

For the new site itself, InstaWP Studio can design a WordPress site from your Substack address and publish it on InstaWP, the AI-native WordPress cloud with managed hosting, so your posts land in a finished design. InstaWP tested Studio on real Substack newsletters on 29 and 30 October 2026, and every Substack fact below was checked against Substack’s help centre on 30 October 2026.

Substack to WordPress at a glance

The whole move takes seven steps. InstaWP Studio handles the design step. The other six use Substack’s own export, a free WordPress.org plugin, your email tool and your domain registrar.

Read the table top to bottom: the order matters. Designing first means each imported post lands in its final layout. Moving paid subscribers before you touch the domain means nobody is billed twice or refunded by accident.

What moves from Substack to WordPress, and what doesn’t?

Posts, images, podcasts and your email list move cleanly. Your design, your yourname.substack.com addresses, Substack’s Recommendations network and paid subscriptions do not move as they are, so plan for each one before you start.

The rows marked “No” are the ones readers notice. Plan the redirect and the announcement around them.

How do you migrate from Substack to WordPress?

Design the new WordPress site first. Then export from Substack, import the posts, move free and paid subscribers, switch the domain with redirects, and announce the move. Doing it in this order lets you check every imported post in its final layout before a reader sees it.

Step 1: Design your new WordPress site with InstaWP Studio

InstaWP Studio is InstaWP’s chat-based AI website builder. You paste your Substack address or describe the newsletter, and it designs a real WordPress site from native blocks on a block theme. The full walkthrough is in InstaWP’s guide on how to build a website with AI.

To rebuild your Substack as a WordPress site in Studio:

1. Open InstaWP Studio and click Bring over your website.
2. Paste your Substack address, for example yourname.substack.com.
3. Click Or rebuild it with a fresh design, choose what comes over. Do not press Copy my site for a Substack (see the warning below).
4. Studio shows what it found: the newsletter’s name and description, the homepage text, photos and colours. Untick anything that should not come over.
5. Add any changes you want on the way, then press Prepare my hero. Studio builds the top of the homepage first so you can check it, and you ask for the rest of the site in chat.
6. Refine the pages in chat, by clicking any part of a page, or in the WordPress editor. Then publish the site to InstaWP. It goes live on a free instawp.site address with SSL, ready for the import in Step 3.

Prefer to start from a blank WordPress site?

If you already have a theme in mind, or you migrate clients from a saved template, create the site from the InstaWP dashboard instead. The steps after this one are the same.

1. Log in to InstaWP and click Add Site on the Sites page. New to InstaWP? Create an InstaWP account first.

2. Choose how to start. From Scratch is a fresh install, From Snapshot reuses one of your saved site templates, From Store starts from a ready-made template, and From AI uses an AI builder such as Kadence AI or ZipWP (InstaWP’s Kadence AI guide walks through that route). Then pick the WordPress version, PHP version, server location and site name.

3. Click Next Step to add plugins during setup, grouped by category: Page Builders, Security, eCommerce, Forms, Speed and more.

4. Pick a plan. Sandbox ($2 a month) is for testing the import. Move to a production plan (Starter at $5 a month or above) before readers arrive. Then click Create Site.

5. Open the new site from the Sites list. Magic Login signs you in to its WordPress dashboard with one click.

Step 2: Export your posts and subscribers from Substack

Substack puts everything in one ZIP. Its help centre article on exporting your posts (updated 24 October 2026) says the export contains your posts, subscriber list and related statistics.

1. Log in to Substack and open your publication’s Settings page.
2. Click Exports in the left navigation.
3. Click Create new export.
4. Substack emails you when the ZIP is ready. Download it from the same Exports section and keep it somewhere safe.

The ZIP holds your post content for Step 3 and a CSV of your subscribers for Steps 4 and 5.

Step 3: Import your Substack posts into WordPress

Use the free Substack Importer plugin from WordPress.org. Version 1.2.0 reads Substack’s export file and imports posts and images, podcasts, author information, and comments on publicly accessible posts.

1. Log in to the WordPress dashboard of the site from Step 1.
2. Go to Tools, Import and install the WordPress Importer if it is not there yet.

3. Install and activate the Substack Importer plugin.

4. On the Import screen, find Substack and click Run Importer.

5. Upload the Substack ZIP. Enter your newsletter’s URL if you want comments and author information too.

6. Assign authors: map the posts to an existing WordPress user or create a new one.

7. Tick Download and import file attachments so images are copied into your media library, then click Submit.

Then open Posts, All Posts and spot-check titles, images and formatting.

Agencies can clean up formatting, author names or slugs before launch with InstaWP’s Code Editor and DB Editor, both in the site’s more-actions menu.

Step 4: Move your free subscribers to a WordPress email tool

Your subscriber CSV goes into any email tool that imports contacts. Pick one, import the file, and send a welcome email from the new sender.

1. Unzip the Substack export and find the subscriber CSV. It has email addresses, subscription dates and plan type.
2. Choose an email tool that works with WordPress, such as MailPoet, FluentCRM, Constant Contact or Kit.
3. Use the tool’s import option, upload the CSV and map the email column.
4. Put migrated readers in their own list or tag, so you can track how they engage after the move.
5. Before the switch, send one last Substack post that says where the newsletter is moving and which address it will come from. Readers who expect the new sender are less likely to mark it as spam.
6. Set up a welcome email in the new tool that links to the new site.

Test signup forms and email workflows on an InstaWP WordPress sandbox before the domain goes live, so nothing reaches real readers until it works.

Step 5: Move paid subscribers without refunding them

Paid subscribers are where most Substack migrations go wrong. Substack bills them through the Stripe account you connected under Settings, Payments. Its Disconnect Stripe button (Settings, Danger Zone) refunds and notifies all your paid subscribers by email, cancels all paid subscriptions and revokes Substack’s access to your Stripe account, according to Substack’s help article on turning off paid subscriptions (updated 29 October 2026).

Two routes work with a WordPress membership plugin:

1. Carry access over, then bill on renewal. Filter the export to paid subscribers and import them into matching membership levels. Set each member’s end date to the end of their current Substack billing period, and email them before that date to add a payment method on your site. Stop their Substack renewal so nobody is charged twice. Paid Memberships Pro documents this route. Expect some readers not to re-subscribe.
2. Ask Substack support for a Stripe hand-over. The subscriptions sit in your own Stripe account. Ask a human at Substack support to remove Substack’s access without cancelling active subscriptions, then use a membership tool that can take over existing Stripe subscriptions. Confirm both halves of that with Substack and with the plugin before you rely on it.

While you switch, Pause subscription billing (Settings, Payments) freezes billing cycles, stops new paid sign-ups and stops existing paid subscribers from being charged. You can schedule a date to unpause, as Substack explains in Can I pause payments?.

Step 6: Point your domain to WordPress and redirect old links

Old links keep their search value only if their addresses keep working. If your Substack runs on a custom domain, move that domain to the new site and redirect Substack’s post addresses. If it runs on yourname.substack.com, those addresses stay on Substack.

Release the domain on Substack first. In Substack, open the Domain section of your settings and select Disable Custom Domain. Then remove the record that points your domain at Substack at your DNS provider. You can still reach your Substack settings at yourname.substack.com/publish/settings, as Substack’s custom domain help article explains.

Then map it on InstaWP:

1. Open the site in the InstaWP dashboard, expand Domains in the site menu and click Map Domain, then the Map Domain button.

2. Enter your domain and choose Primary for the main address or Alias for an extra domain that points at the same site. Copy the CNAME target the dialog shows.

3. At your registrar or DNS provider, add a CNAME record that points your domain at that target. If your provider does not allow a CNAME on the root domain, use an ALIAS or ANAME record, as InstaWP’s guide to mapping a root domain when the registrar blocks CNAME explains. If you use Cloudflare, turn the proxy off while you map.

4. Go back to the dialog in InstaWP and click Map Domain. Once DNS propagates, InstaWP issues SSL for the domain automatically.

The full reference is InstaWP’s guide to connecting a domain, its domain documentation and the InstaWP Domains page.

Then redirect Substack’s post addresses. Substack posts live at /p/post-name. Set WordPress permalinks to Post name under Settings, Permalinks, then add one regex redirect in a plugin such as Redirection or Rank Math’s Redirections module: source ^/p/(.*), target /$1, type 301. Before you announce, open five old post links from Google Search Console and confirm each one lands on the right post.

Step 7: Announce the move and finish the site

Send the announcement once the domain resolves and the redirects pass your spot-check. Then add the pages Substack never gave you: an About page, a Start here page for new readers, a Contact page and a Privacy Policy. On a Studio site you can ask for each one in chat. Keep the Substack publication online until the redirects have been live for a few weeks.

Agencies that migrate several newsletters can save the finished site as a template. Open the site’s more-actions menu on the Sites page and choose Save Template/Snapshot, as described in InstaWP’s snapshot guide. The next client’s site then starts with the same plugins and pages.

What usually breaks in a Substack migration?

Five things break most often, and each one has a documented cause. Check this list before you announce the move.

Why move from Substack to WordPress?

Writers move to WordPress to own the platform, not just the list. Substack keeps 10% of paid subscription revenue, and Stripe charges its own fees on top (Substack’s pricing help article, updated 29 October 2026). Every Substack publication shares the same layout, and selling anything beyond a subscription means going off-platform anyway. InstaWP compares the two in more depth in Substack vs WordPress for creators and agencies.

Read the table as a trade: Substack is quicker to start, and WordPress gives you control over design, revenue and integrations once the newsletter is a business.

How do you make money from a WordPress newsletter?

Install a membership plugin, create your plans and restrict paid posts to members. On WordPress the payment processor takes its fee and there is no platform cut.

• Install a WordPress membership plugin such as MemberPress or Paid Memberships Pro.
• Create plans, for example a free tier, a monthly paid plan for premium posts and a discounted annual plan.
• Restrict posts, pages or newsletter issues to paying members.
• Add more income where it fits: courses, ebooks, templates, consulting or affiliate links.

Test membership tiers and checkout on an InstaWP sandbox before you go live.

How can agencies turn Substack migrations into a repeatable service?

Build one newsletter site, save it as a template, and start every new client from it, so each migration begins with the plugins and pages already in place. A saved InstaWP snapshot can hold a newsletter theme, an SEO plugin, a membership and forms setup, and default pages such as About, Contact and Privacy Policy. For a client who wants the design to start from their own Substack, rebuild it in InstaWP Studio instead and import the posts as in Step 3.

Pair this with InstaWP’s Website as a Service tools to sell hosted newsletter sites on a subscription, so each migration turns into recurring revenue.

Can you host your newsletter site on InstaWP?

Yes. InstaWP is a managed WordPress hosting provider that bills each site by the day. A site built in Studio publishes there directly, and a site created from the dashboard moves from sandbox to production without a migration.

Prices are from InstaWP’s pricing page on 30 October 2026. Every plan includes SSH, SFTP, WP-CLI and free SSL. Adding a card unlocks $25 in credits, and production plans carry a 14-day money-back guarantee.

Conclusion

Migrating from Substack to WordPress moves your newsletter onto a platform you own: your design, your revenue model and your list. Four steps protect your subscribers and rankings: the export, the importer with attachments ticked, a careful hand-over of paid subscribers, and a custom domain with a /p/ redirect. InstaWP Studio shortens the part Substack cannot export, the design, by rebuilding your newsletter as a WordPress site before the first post arrives.

Frequently asked questions