Subscription Migrations: A Practical Guide

We, at FILDI, have run subscription migrations of all shapes and sizes. From large corporates with millions of active subscribers (FTSE & Nasdaq vibes), and all the way to fast growing DTC scale-ups.

Some migrations have gone without a hitch: methodical, well-resourced, with barely a ripple in churn.

Others have been harder. Much harder.

If a brand moves fast and decides to skip steps, they’ll definitely find out 2-3 months later that entirely avoidable churn has eaten into their subscriber base that they spent years building.

Some brands have migrated onto proprietary technology that they’ve built in-house. Others have moved from one third-party subscription platform to another.

Some moves have been the making of a business. Others have been costly detours that took months to recover from.

It is not easy. But if the move is genuinely the right decision, it will make a world of difference. 

The key phrase, of course, is “genuinely the right decision”.

We wrote this article as a partner contribution to Inspira Digital's Ultimate Shopify Migration Guide, a comprehensive resource that covers whether Shopify is right for your business to the step-by-step migration process, costs, pitfalls and how to maintain growth post migration.

If you're considering a move to Shopify, it's well worth reading in full at inspiradigital.co.uk/shopify-migration-guide.

What follows focuses specifically on the subscription dimension, an area the guide addresses but which deserves its own deeper treatment, given how much is at stake.

Before you migrate: Are you making the right decision?

For many who read this, the subscription migration isn't the primary motivation.

That motivation is moving to Shopify, meaning subscription platform move is a necessary consequence. That's an important distinction, because it changes the nature of the question you should ask.

If you're moving to Shopify, the question isn't whether to migrate your subscriptions, but rather is which subscription platform to move to and how to select the right one for where your business is going. Shopify's subscription ecosystem is genuinely rich: Recharge, Skio, Loop, Firmhouse, Relay, Appstle etc all offer serious capability and choosing between them is worth proper consideration rather than defaulting to the most familiar name.

Take the time to map your requirements, your current subscriber complexity and your growth roadmap against what each platform offers. The disruption of migration is significant enough that it's worth arriving at the right destination.

However, if you're already on Shopify and considering moving from one subscription platform to another, the bar is higher, because the commercial rationale has to stand up to scrutiny

 Before committing to a platform to platform migration, it's worth asking honestly whether you've fully activated what your current system offers. The likelihood of finding under utilised capability in your existing platform is quite high, particularly around retention flows, dunning logic and reporting.

If the limitations driving the migration are genuine ceilings rather than configuration gaps, then you should move.

If not, the disruption to your subscribers will probably outweigh the benefit.

In either scenario, just make sure you're moving towards something clearly better, with a clear-eyed understanding of what the journey will cost your subscriber base along the way.

Subscriptions = Long-term relationships

Migrations = Disruptions

The thing that makes subscription businesses so valuable is the long-term relationship with a customer and that same characteristic is what makes migrations so delicate.

When someone subscribes to your brand, they're trusting you with their payment details, their routine and in many cases, their habits. That trust accumulates over months and years. A customer who joined three years ago might have joined on a plan that probably doesn't exist any more.

A platform migration is a fundamental disruption to the infrastructure underpinning all of those relationships. The trust your subscribers have placed in you over years is, in effect, what's being carried across. Expect some turbulence. Plan for it, account for it and communicate through it.

Your catalogue will be massive

Basically, you're migrating every single plan and SKU you have ever offered that anyone is still subscribed to, not just those that are live today.

Again: Subscriptions are long-term relationships, which means your subscriber base will include customers on pricing tiers, products and promotions that you retired years ago.

• That £19.99/month offer from 2021.

• The “awful” legacy bundle that was discontinued but grandfathered for existing subscribers.

• The quarterly plan that was swapped out for a monthly plan two years ago, but which 50 customers still sit on.

Every one of those plans needs to be accurately mapped, transferred and preserved in the new platform. Migrating your current offer set means you break contracts with a portion of your subscriber base.

This is one of the most data-intensive and painstaking aspects of any migration. It requires a full audit of your historical subscription architecture: what was ever launched, who is still on it and how it needs to be reconstructed on the new platform.

Legacy promotions: also massive

Related to the above but deserving its own attention: your promotional history needs careful handling.

Your brand may well be carrying discount codes, early-adopter pricing and one-off offers that were created years ago and have since been forgotten, but are still actively running for a subset of subscribers. These customers have quietly come to rely on these benefits as part of their relationship with you.

If migration causes any of those benefits to disappear, trust breaks immediately.

• Customer service volumes spike.

• Churn follows.

These customers didn't choose to leave; your migration pushed them out.

Every active promotional structure must be audited, mapped and either deliberately preserved or deliberately retired with appropriate communication before go-live.

I’m afraid there is no workable middle ground.

A subscriptions migration isn’t an opportunity to "clean up" your subscriber base

This point needs stating clearly, because the temptation is real.

A migration feels like a natural moment to rationalise your subscriber base: retire legacy plans, phase out old pricing, consolidate SKUs, remove promotional anomalies, etc. Resist it. That is a separate project that belongs on a separate timeline.

A successful subscription migration causes the least friction. Your goal is to create a like-for-like ecosystem for your existing subscribers on the new platform. The migration is primarily about improving your operational capabilities and unlocking greater functionality.

Reshaping the customer experience is valid and important work, but it belongs in the roadmap after a stable migration, not during one.

Cleaning up your subscriber base and migrating your subscriber base at the same time amplifies risk significantly and makes it much harder to diagnose problems if things go wrong.

Payment continuity will decide everything

If there is one technical area that will determine whether your migration succeeds or fails, it is payment continuity.

Subscription revenue lives and dies by payment success rates. Payment tokenisation (the encrypted credentials that allow your platform to charge a customer's card without storing the raw card data), does not automatically transfer between platforms.

If this process is mishandled, well… yep.

Their bank rejects a transaction, your payment retry flows fail and their subscription cancels, even though they didn’t want to.

This is the most damaging form of churn because it's invisible until it shows up in your revenue. By then, the damage is done.

A well-orchestrated migration ensures billing schedules remain intact, dunning and retry logic functions from day one and subscribers don’t feel any disruption to their payment rhythm. This is revenue protection at its utmost and it deserves Founder attention. This is not a technical detail to be delegated. 

Mandates, tokens and payment notifications: IMPORTANT.

Payment methods behave very differently during a migration and it's worth understanding the distinctions clearly.

UK Direct Debit: If any mandate details change as part of the migration, including the service user number or payment originator, you are legally required to notify affected customers in advance under the Direct Debit scheme rules. In our experience, that notification will prompt c2% of affected customers to cancel, regardless of how well it's written.

The communication triggers a reconsideration: someone who has been subscribing passively for two years reads a "your Direct Debit is changing" email, decides now is as good a time as any to review and cancels. Plan for this and factor it into your migration business case.

SEPA Direct Debit: The same principle applies across European markets. SEPA mandates are tied to a Creditor Identifier, a unique ID that identifies the entity collecting the payment. If that Creditor ID changes as part of a migration (which it typically does when changing payment processor or subscription platform), a new mandate must be obtained from the customer. That means a notification and re-authorisation flow, carrying comparable incremental churn risk to UK Direct Debit. If you have a meaningful European subscriber base paying via SEPA, this is a material consideration in your migration planning.

Credit and Debit Cards: Cards don’t require customer notification. That said, the encrypted payment token must be carefully transferred between systems, as a broken token transfer leads to cards failing silently and customers churning without wanting to. So no customer communication is needed, but the technical execution of the token transfer is technical and super-important.

The practical takeaway is that your migration timeline and communications strategy need to be planned around your payment method mix. The approach won’t be the same for every business.

Please pause any new acquisitions in the weeks before a migration

One of the most practical steps in migration preparation is also one of the easiest to sort: pausing subscription acquisitions for at least one week before migration takes place.

The reason is straightforward: your subscriber database constantly moves around. New customers join, payments process, retries occur and behaviours change every single day. Migrating a fluid database will dramatically increase complexity and reconciliation risk.

Pausing new subscription acquisitions helps create a stable, defined dataset to work with. It makes the migration itself cleaner, reduces the likelihood of data mismatches and lowers the chance of post-launch surprises. Yes, you will lose a week of new subscriber volume, but that is a small, entirely recoverable cost compared to the alternative.

Subscriber migration is hyper-sensitive work

The data transfer at the heart of a subscription migration is extraordinarily precise. You’re transferring years of subscriber history, billing dates, plan details, payment credentials, promotional entitlements, add-ons, pauses, address changes and order history, for potentially thousands of customers, all of whom need to land on the new platform in exactly the right state.

The margin for error is zero. A small data mapping mistake at scale = a large customer service problem, or a churn event, or a billing failure. This requires meticulous planning, detailed QA processes and the right specialist resource.

Your operations need to move too

Customer data is the most visible part of the migration, but it is only one layer of a move.

Alongside the subscriber transfer, a comprehensive migration requires careful thought about how your customer service team will work in the new system: their access, their tooling and their processes for handling changes, cancellations and issues. It also requires thinking through how your financial data will be structured, exported and fed into your accounting systems and whether your revenue reporting will remain consistent across the transition.

Operationally, you need to map out payment processing and optimisation on the new platform, including how dunning will work, what retry logic looks like and how failed payments will be managed. Your "My Account" customer portal will likely change in appearance and function (and destination), which requires clear communication and potentially new pages.

Winback flows, cancellation prevention journeys, reporting pipelines, SKU setup, pricing structures, customer service system integrations: all of it needs to be audited, rebuilt and tested before a single subscriber is moved.

Treating the operational readiness review as equally important as the technical migration plan is what separates migrations that land cleanly from those that uncover gaps in the weeks after go-live.

The Shopify ecosystem makes the prize worth having

It's worth being clear about why this migration is worth the effort for the right brand.

Shopify's subscription technology ecosystem is genuinely strong. Recharge, Skio, Loop, Firmhouse, Relo and Appstle all offer serious recurring revenue capabilities, with flexible billing models, sophisticated retention tooling, cancellation flows, deep analytics and integrations with the rest of your Shopify stack. The breadth of choice available within the Shopify ecosystem is a material step up from most legacy platforms.

That wider Shopify migration landscape is covered in considerable depth by Inspira Digital's migration guide, which brings together expertise from a range of specialist partners covering everything from SEO and search readiness to loyalty data, compliant invoicing, payment methods, CRM and operational readiness. If subscriptions are one piece of your migration puzzle, the guide covers the rest: inspiradigital.co.uk/shopify-migration-guide.

And here’s FILDI’s specific contribution to the guide: https://www.inspiradigital.co.uk/blog/partner-insight-avoiding-churn-during-a-shopify-subscription-migration---fildi 

Get the subscription foundations right: stable data transfer, payment continuity, operational readiness and a like-for-like experience for your existing subscribers.

Do that and the new platform becomes a genuine growth engine. The investment can be significant, but so is the return.

Ready to Audit Your Subscriptions Business?

Get your FILDI Subscription Performance Audit and identify exactly what's costing you money, with a clear roadmap to fix it.

A subscription migration is a natural inflection point to take stock of how your recurring revenue is actually performing. Before you move platforms, it's worth knowing precisely what you're working with.

The FILDI Subscription Performance Audit conducts deep analysis across your subscription data to present a comprehensive performance picture. Our proven methodology examines customer lifetime value, acquisition costs, growth efficiency and retention patterns across your full subscriber base, including the historical cohorts that tend to get overlooked.

More importantly, you'll receive specific, actionable recommendations based on our findings. We don't just identify what's broken; we prioritise what to fix first, so you arrive on your new platform with a clear growth plan and not just a clean data transfer.

Find out more at fildi.co