Migrating from Substack: full 2026 guide (with 1-click importer)

Migrating a newsletter off Substack sounds scarier than it is. The actual export takes about ten minutes. The parts that trip people up are the ones nobody talks about: DNS records that need to age, paid-tier reconstruction so existing subscribers aren't charged twice, redirects so your Google rankings survive, and — if you're in India — the tax and legal handoff nobody at Substack support is going to help you with.

This is the full walkthrough. It assumes you're moving to Fluxeta, but 80% of it applies whichever platform you're heading to.

Before you start: the pre-flight checks

Do these first, in this order, before you touch anything on Substack.

1. Screenshot everything financial. Take screenshots of your current paid subscriber list, MRR, and payout history. If a Substack support ticket ever needs to be filed, you'll want dated evidence.

2. Note your current URLs. Every published post's Substack URL. A quick way: pull your public archive /archive page and save it, or use a crawler. You need these later to build redirects.

3. Check custom domain status. If you're on a custom domain via Substack, note the CNAME target Substack gave you (typically custom-domain-forwarding.substack.com or similar). You'll be pointing this elsewhere.

4. Warn paid subscribers (optional but recommended). A one-line email — "we're moving to a new home, nothing to do on your end" — reduces the number of "did I get scammed" support emails you'll field during the switchover.

Step 1 — Export from Substack

Substack's export is straightforward:

1. Go to Settings → Exports → Create a new export.
2. Wait for the email (usually within a few minutes, up to an hour for large archives).
3. Download the ZIP.

The ZIP contains:

• posts.csv — one row per post with metadata (title, subtitle, publish date, is_published, body HTML).
• A folder of HTML files, one per post — same content, easier to read individually.
• subscribers.csv — free and paid subscribers with email, status, subscribe date, and a paid-tier flag.

Extract it somewhere you'll remember. subscribers.csv is your most important file.

Step 2 — Import posts (the 1-click part)

Fluxeta accepts the Substack posts.csv directly in the admin's Import area. Upload the CSV, pick whether to import as draft or published, and the importer:

• Creates a post per row, preserving title, subtitle (as excerpt), publish date, and body HTML.
• Slugifies titles into URLs, deduplicating collisions with -1, -2 suffixes.
• Queues a background job to download every image referenced from substackcdn.com and rehost it on your Fluxeta storage — so your posts survive Substack shutting down your account or rotating their CDN.
• Skips empty rows and reports the count.

For a typical archive of 50–200 posts, the import itself takes under a minute; image rehosting runs in the background over the next few minutes to an hour depending on archive size.

If you have posts.csv open right now: check the is_published column. If you want everything live immediately, set the importer to publish. If you want to review before republishing (usually smarter for older posts), import as drafts.

Step 3 — Import subscribers

subscribers.csv has three columns you care about: email, subscription_type (free / paid), and subscribed_at.

In Fluxeta's admin, use the Subscriber CSV import. It matches columns case-insensitively, marks unsubscribes as unsubscribed (not deleted — you want to preserve their status so you don't accidentally re-import them next year), and preserves subscribe dates.

Critical: do not send a "welcome to Fluxeta" broadcast to your imported list immediately. Import as-is, keep their status, and just carry on your regular publishing cadence from the new platform. Your list will feel the transition entirely through the "From:" address of your next issue.

About paid subscribers: the CSV contains their email and paid status. It does not contain payment credentials — Substack doesn't (and legally can't) hand over Stripe payment methods to another platform. This is the part that requires a plan. See Step 5.

Step 4 — DNS, custom domain, and the switchover

If you were on newsletter.yoursite.com via Substack, this is the most delicate step because DNS changes are irreversible for the propagation window.

1. Add your custom domain in Fluxeta. In Settings → Domain, add your domain. Fluxeta will show you the required CNAME (or A record).
2. Verify TLS is issued. Fluxeta provisions Let's Encrypt automatically once the DNS record resolves. Wait until you see the green "issued" badge before switching.
3. Update your DNS record. In your DNS provider (Cloudflare, Route 53, GoDaddy — wherever your domain lives), change the CNAME to point at Fluxeta's target instead of Substack's.
4. Watch propagation. Use dig or dnschecker.org to confirm the new record resolves globally. Usually 5–30 minutes; occasionally hours.
5. Test end-to-end. Load your custom domain in an incognito window. Confirm your homepage, an archive page, and a post URL all render.

During propagation some readers may hit Substack, some may hit Fluxeta, briefly. This is expected and harmless.

Step 5 — Reconstructing paid subscriptions

This is the part that requires human touch. There is no legal way to migrate active payment credentials from Substack to another platform. Your options:

Option A (recommended for India-facing lists) — invite paid subscribers to re-subscribe via UPI Autopay. Send a personal, well-written email explaining you're moving, thanking them, and offering:

• A grace period (e.g., 30–60 days of free access on the new platform regardless).
• A one-click UPI Autopay checkout link at their existing price, or better — a small discount for the friction.

Because UPI Autopay is a smoother re-subscribe than a card checkout, conversion is usually better than migrating creators fear. Realistically, expect 60–80% of active paid readers to re-subscribe within the grace period if you write the email honestly and make checkout easy.

Option B — run parallel until natural churn. Keep Substack paid subscriptions active until they lapse, and publish new paid content only on Fluxeta. Slower migration but zero friction for the reader. Fine if your ARR isn't your primary income.

Option C — hybrid. Announce a hard cutover date (say, 90 days out), keep both live until then, offer discounted annual on the new platform to accelerate re-subscribes.

Substack does not natively support "cancel my subscriptions on my behalf on this date" as a bulk action. You'll need to disable new signups on Substack manually and communicate the wind-down.

Step 6 — Redirects (the SEO safety net)

If Google was sending traffic to your Substack URLs, you want that traffic to arrive at the new URLs.

Best case: you were on a custom domain. When you flip DNS to Fluxeta, your URLs stay identical (yoursite.com/post-slug) and rankings carry over cleanly. This is the whole point of using a custom domain from day one.

Trickier case: you were on yourname.substack.com. Substack does not let you set 301 redirects from those URLs to your new domain. You have three options:

1. Meta refresh via Substack post edits. Edit each post to just say "this content has moved to <new URL>" with a big link. Ugly but honest, and Google usually re-indexes to the new URL over 2–3 months.
2. Substack's built-in "URL redirect" for individual posts — as of 2026, Substack allows a single global forwarding URL for the whole publication (Settings → Redirect). This forwards yourname.substack.com root traffic but does not per-post 301 redirect. Better than nothing.
3. Accept the SEO hit. For most newsletters that get 80% of traffic from email and social, this is not a career-ending event. Rankings recover as the new URLs get indexed.

Whichever route: submit the new sitemap to Google Search Console immediately after switchover. Fluxeta generates and pings the sitemap automatically on publish.

Step 7 — Tax and legal handoff (India-specific)

The bit no one talks about:

• GST invoicing. If you were above the GST threshold and Substack was raising invoices via their US entity to your Indian buyers, that's already a slightly grey compliance area. On Fluxeta with Razorpay, GST-compliant invoices are generated per subscription automatically, using your GSTIN. Enter your GSTIN in Settings → Billing.
• Income category. Newsletter subscription income is treated as business income in India, not royalties. Substack payouts arrived as USD wire transfers; Razorpay payouts arrive as INR bank transfers with cleaner reconciliation.
• TDS. As of 2026 the platform-fee TDS regime for digital creators is still evolving. Fluxeta issues Form 26AS-compatible summaries; your CA can slot them straight into your return.
• Old data retention. Under DPDP Act, keeping subscriber data on Substack "just in case" after you've fully migrated is not a defensible processing basis. Once your migration is verified, request a full data deletion from Substack support in writing.

After the switch

Give yourself a first-issue-from-new-home moment. Write a short post naming the move, thanking the readers who came along, and setting expectations for what changes (nothing much, ideally). This is your best-performing issue of the year, statistically — people open it.

Closing thought

The mechanical part of migrating from Substack is a weekend. The paid-tier reconstruction is a month. The relief of owning your domain, your list, and your revenue rail is permanent.

Fluxeta ships with a Substack CSV importer, native UPI Autopay for the paid-tier re-subscribe flow, and free custom domains — because these were the three parts of the migration that hurt the most for the creators we talked to. Free up to 1,000 subscribers if you want to import and try before deciding. Start free, or read Fluxeta vs Substack for the fuller comparison.