If you're running a subscription box or recurring product business on WordPress, you've probably felt the friction: a WooCommerce store, a subscription plugin, a payment gateway, a theme and a stack of extra plugins for caching, security and backups, all of which have to keep working together every time something updates.
This is a practical guide to moving that store to Subbly. It covers every stage — from the pre-migration audit to going live — including the part most guides skip: keeping your search rankings while the URLs change.
Key Takeaways
A WordPress subscription store is usually several moving parts (WooCommerce, a subscription plugin, a payment gateway and supporting plugins). Subbly puts billing, checkout, customer portal and storefront in one platform.
The hardest part of any migration is the payment token transfer. If your subscribers' cards live in your own Stripe account, this is straightforward. If they're stored with PayPal or a plugin-specific vault, plan for more time.
Only active subscriptions migrate. Past orders do not, so export your order history before you close anything.
Redirects protect your SEO. Map every old URL to its new equivalent with a permanent (301) redirect before you switch DNS.
Do not cancel anything on the old store until the Subbly migration is confirmed complete.
Why Subscription Brands Leave WordPress
WordPress and WooCommerce are flexible, and plenty of subscription businesses start there. The trouble is that recurring billing is not what the platform was built around. It is added with plugins, and every plugin is another thing to configure, update and debug.
A typical WordPress subscription setup includes:
WooCommerce for products and checkout
A subscription plugin for recurring billing, renewals and subscriber management
A payment gateway connected to the subscription plugin
Hosting you size, secure and keep fast yourself
Supporting plugins for caching, security, backups, forms and email
The result is a stack where a plugin update can break a checkout or a renewal, and where a slow page is a hosting, theme or plugin problem that you have to diagnose yourself.
Subbly is built subscription-first: recurring billing, customer portal, subscriber management and storefront are part of the core platform, not bolted on. That is why most of the plugin stack simply disappears after migration. See Subbly's WooCommerce comparison before you decide.
Before You Migrate: The Pre-Migration Audit
Don't touch anything in Subbly until you've done this audit on your current store.
1. Export your subscriber list
From WooCommerce or your subscription plugin, export every active subscriber. You need: name, email, shipping address, subscription product, billing frequency, next billing date and current status.
2. Check where payment tokens live
This is the single most important question in any subscription migration. Ask yourself: are your subscribers' payment methods stored in Stripe customer profiles in a Stripe account you control?
If yes — your migration is fast and nearly seamless. Subbly can import using the Stripe customer IDs, and subscribers won't need to re-enter payment details.
If no (PayPal, a custom gateway, or a payment method tied to a plugin) — you'll need to plan for a longer migration. Subbly has a dedicated process for this situation, covered below.
3. Document your products, plans and coupons
List every subscription product, billing interval, trial period, discount code, shipping rule and add-on. You'll recreate these in Subbly exactly, including pricing and shipping.
4. List every URL that ranks
Crawl your site or export your sitemap and note every product, category, blog post and landing page URL. Pull your top pages from Google Search Console so you know which ones matter most. This becomes your redirect map.
5. Export your order history
Past orders do not migrate to Subbly. Export them from WooCommerce so you keep your records, and keep the old store accessible until you're sure you don't need it.
Setting Up Your Subbly Store
Once the audit is done, set up your Subbly account before touching anything else.
Step 1: Connect Stripe and recreate your products
Connect the same Stripe account you use today, then recreate each subscription product from your audit list. Key settings to get right:
Billing frequency (weekly, monthly, quarterly, annually, or custom)
Trial periods and first-order discounts
Shipping zones and rates
Coupons you want existing subscribers to keep
Step 2: Build your storefront
The storefront needs at minimum: a homepage, a product or subscribe page, a checkout flow and a customer portal. These drive the most revenue and the most support tickets, so get them right first.
One thing that simplifies a WordPress migration: in our builds, the call-to-action buttons on product pages link straight to Subbly checkout for that specific product. There's no cart plugin in the middle, so the path from product page to payment is shorter.
Step 3: Build your redirect map
For every old URL on your list, decide where it should go on the new site. Use a permanent (301) redirect, and point each old URL at the closest equivalent page, not just the homepage. Where you implement the redirects depends on your site setup, but they must be live on the day you switch DNS.
Step 4: Set up your domain and emails
Connect your custom domain in Subbly, but don't point DNS yet — do that last, right before launch. Then configure and test Subbly's transactional emails (order confirmation, billing reminder, failed payment, cancellation) and reconnect your email marketing tool.
Migrating Your Subscribers
This is where most founders get nervous. The process is more straightforward than it looks.
If your payment data is on Stripe
Contact Subbly to request a migration. The team sends you a CSV template. Subbly's Help Center explains exactly what to check.
Fill in the template exactly as provided. For each subscriber you need the email, name, a Stripe customer ID, shipping address, next payment date and shipping method. Use a separate CSV for each subscription product.
Send the CSV to Subbly. They check the format and run the import, normally within 48 hours (excluding weekends).
When it's done, Subbly sends you a CSV of generated passwords, or customers can simply reset their own.
Do not cancel subscriptions on your old store until you have confirmation from Subbly that the import is complete.
Important: only active subscriptions migrate, not past orders. Subscribers who are paused need a future renewal date. If anyone has a prepaid order pending, decide whether to fulfil it from the old store or create it manually in Subbly. The full migration process is documented here.
If your payment data is not on Stripe
Contact Subbly's migrations team directly. They run a process called Subscription Switch™ for this situation: subscribers receive a link to re-add their card, and Subbly reports that up to 84% are back on billing within 11 days. It takes longer than a Stripe migration, but it is far less disruptive than asking everyone to start over.
Suppress cancellation emails
Before the import runs, pause automated email notifications on your old store. When subscriptions are cancelled there as part of the switch, you don't want subscribers receiving "your subscription has been cancelled" emails and panicking.
Keeping Your SEO: Redirects and URLs
A platform change can quietly cost you your rankings if old URLs return 404 errors. Most of the damage is avoidable:
Redirect every old URL that has traffic or links to its closest new page with a 301 redirect.
Keep the content the same on pages that rank. Don't rewrite a page that brings in traffic at the same moment you move it.
Keep titles, descriptions and headings on key pages unless you have a reason to change them.
Submit your new sitemap in Google Search Console on launch day.
Check Search Console for 404s daily for the first two weeks and add any missed redirects.
Speed often improves on its own: with no plugin stack to load, the new site has far less to render. Check the result with Google PageSpeed Insights before and after so you can see it.
Going Live: Launch Checklist
Run through this before switching DNS:
All subscription products created and priced correctly in Subbly
Checkout tested end-to-end with a real test transaction
Customer portal tested — can subscribers skip, pause and update their payment method?
Transactional emails configured and tested
Subscriber import confirmed complete by the Subbly team
301 redirect map live and spot-checked for your top pages
DNS pointing to the new site
Old WordPress site kept accessible (don't delete it yet — keep it for at least 30 days)
Google Analytics and tracking confirmed firing on the new store
New sitemap submitted to Google Search Console
What Actually Breaks During Migrations
Based on real migrations, here are the failure points to watch for:
Features that lived in plugins. Memberships, restricted content, custom checkout fields, wholesale pricing and special shipping rules were all provided by plugins. List every plugin before you start and decide how each function is replaced, or whether you still need it.
Missing redirects. The most common cause of lost traffic after a WordPress migration. Old product and blog URLs return 404s, and rankings drop within weeks.
CSV formatting errors. Subbly's migration CSV is strict. Do not add or remove columns, and do not change header capitalization. Subbly won't edit the file after the import, so double-check it before sending.
Discount codes that don't carry over. Any subscriber on a legacy discount needs it recreated in Subbly. Pull a list of these before migrating.
Email flows pointing to the old store. Automations tied to WooCommerce events need to be reconnected to your Subbly integration. This is usually discovered on the first billing cycle when a win-back email doesn't fire.
How Long Does a WordPress to Subbly Migration Take?
A realistic plan for a straightforward migration where payment data is on Stripe:
Pre-migration audit and URL inventory: 2–3 days
Subbly product setup and storefront build: 1–2 weeks, running in parallel
Subscriber CSV preparation and submission: 1 day
Subbly import processing: up to 48 hours (excluding weekends)
Redirect testing, QA and DNS switch: 1–2 days
Plan for roughly 2–3 weeks from start to live. If your payments are not on Stripe, add time for Subscription Switch™. The storefront build, not the subscriber import, is usually what sets the timeline.
Should You Do This Yourself or Hire Someone?
The subscriber import is handled by Subbly's team, so you don't build that part. What takes time and expertise is:
Running an accurate pre-migration audit, including the plugin inventory
Rebuilding the storefront to a conversion-ready standard, not just a functional one
Configuring products, shipping, taxes and portal permissions correctly
Building and testing the redirect map
Reconnecting email flows and tracking
Founders who do this alone usually underestimate the redirect work and get the product configuration wrong on the first attempt, which causes billing errors after launch.
If you'd like to see what a WordPress migration looks like in practice, read the Alpha Traditions case study. And if you'd like a second pair of eyes before you start, book a free strategy call — we'll review your current setup and tell you exactly what the migration looks like for your store.
Moving from a different platform? See our guides for Shopify to Subbly and Cratejoy to Subbly.
The Subscription Agency builds and migrates subscription storefronts on Subbly. If you're planning a migration, book a free 30-minute strategy call and we'll scope the work before you commit to anything.
Free Strategy Call
Ready to Launch Your Subscription Store?
Book a free 30-minute strategy call with our team. We will review your current setup, identify growth opportunities, and outline a clear plan for your Subbly launch.
Book your strategy callBook your strategy call