Substack to WordPress

WordPress hosting for publications leaving Substack.

The posts are the easy part. The paying subscribers and the sending that reaches them are the publication, and neither transfers by itself.

Paid subscribers carried deliberatelySending rebuilt before launchFree migration
Free migrationSubscriber migration planNewsletter sending rebuiltDaily backupsFree SSL24/7 support
The list is the business

What actually has to move from Substack.

Content exports easily. The audience and the money attached to it need a plan made before anything changes.

Paid subscribers and their billing

Free subscribers export as a list. Paid ones have a live billing relationship, and carrying that across is a deliberate exercise rather than an import.

Stripe relationship planned first

Sending, rebuilt before you need it

Substack sends your posts as email as part of the product. WordPress does not, so the capability has to be chosen and tested before the first post goes out here.

/p/ URLs redirected

Substack post URLs carry the search traffic and the inbound links a publication has accumulated, and they match no WordPress permalink structure without a rule for each.

Posts and their formatting

The content export is straightforward. What needs attention is embeds and paywall markers, which mean something specific on Substack and nothing at all once imported.

Paywalled archives stay paywalled

Posts that were subscriber-only have to remain gated after the move, which is a membership decision rather than a content one.

Migration

The money first, the archive second.

Posts can be re-imported if something goes wrong. A broken billing relationship with paying subscribers cannot, so that gets settled before anything else moves.

  • Subscriber and billing approach agreed before the move
  • Sending tested before the first send
  • Cutover at a time you choose
  • Substack left live until you confirm
Free subscribers
Imported
12,400
Paid subscribers
Billing carried
830
Newsletter sending
Tested
ready
DNS cutover
Awaiting your go-ahead
scheduled
Performance

Subscriber pages, which cannot be cached.

A paid publication delivers most of its value to signed-in readers, and no page cache helps there. What decides it is the object cache and the database behind it.

Free
migration, done by us
Redis
object cache, on by default
14
edge regions
MagicWP135 ms
Untuned membership site830 ms
No object cache410 ms

Illustrative comparison of a signed-in subscriber request after migration. Your numbers depend on membership plugin and archive size.

Configuration

What this move needs that a host migration does not

Substack is a narrow product doing several jobs at once, and each of them becomes an explicit choice in WordPress.

SettingWhat we doWhy
Paid subscribersMigrated with the billing relationship planned before anything else movesFree subscribers are a list; paid ones are a live payment relationship, and that is the part of a publication that cannot be recreated if it breaks.
Newsletter sendingChosen and tested before the first post is published hereSubstack sends email as part of the product, so a publication that emailed every post loses that entirely unless it is rebuilt first.
Post URLsEvery /p/ address redirected to the new permalinkThose URLs carry the accumulated search traffic and inbound links, and they match no WordPress permalink structure without an explicit rule.
Paywall markersTranslated into real membership rulesA paywall marker in exported content means nothing after import, so subscriber-only archives become public unless the gating is rebuilt deliberately.
EmbedsReviewed rather than trusted to carrySubstack-specific embeds and buttons export as markup that refers to a platform the site is no longer on.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Can I bring my paying subscribers?
Yes, but it is planned rather than imported. Free subscribers are a list; paid ones are a live billing relationship, and moving that deliberately is the whole difference between a smooth transition and losing revenue.
What sends my newsletter afterwards?
Something chosen and tested before your first post goes out here. Substack sends email as part of the product and WordPress does not, so it is the capability most often discovered missing at the worst moment.
Will my old post links keep working?
Yes, with a redirect for each. Substack's /p/ URLs carry the search traffic and inbound links the publication has built up, and none of them map to a WordPress permalink structure automatically.
Do my subscriber-only posts stay private?
Only if the gating is rebuilt, which is part of the move. Paywall markers in an export mean nothing once imported, so without that step the whole paid archive becomes public.
Can I run both for a while?
Yes, and it is a sensible way to do it. The WordPress site is built and reviewed on a temporary domain while Substack keeps publishing, so nothing switches until you are ready.

Leave Substack and own the list, the archive and the sending.

Free migration, billing carried deliberately, and newsletter sending working before your first post.