E-Commerce Nov 19, 2026

Migrating Subscription Customers: Preserve Payment Methods, Prices and the Next Charge

Migrating Subscription Customers: Preserve Payment Methods, Prices and the Next Charge

Time to read: 11 minutes

Content

  1. The migration and reconciliation sheet
  2. Inventory the subscriptions that must survive
  3. Supported token migration or customer re-authorisation?
  4. Map identity, price, schedule and status
  5. Dry-run charges and reconcile cutover exceptions
  6. Verify migration experience and shutdown ownership
  7. Scope the parallel run and retained customer support
  8. Your next step
Bookmark

Imported customer records do not make a subscription migration safe. Each active subscription needs a usable payment method, the agreed price and a next charge that exactly one system will take.

Active subscriptions can move to a new platform without losing the customer's payment method, agreed price or next charge date, but only if three things are true for each subscription. First, the payment method follows the customer through a route the payment provider supports: a processor-to-processor data export and import, a destination platform that can use the existing gateway's stored payment methods, or the customer re-authorising. Second, price, currency, tax, address, frequency, status and next charge date are recreated and reconciled field by field. Third, only one system may charge a subscription at any moment.

That third rule answers the timing question. The old system must stop billing a subscription after it has taken its last charge and before the new system's first scheduled charge for that subscription. In practice that means an agreed cutover per cohort, recorded in a reconciliation sheet, with the old schedule disabled before the new one can fire.

This guide is for established D2C and subscription retailers replacing a subscription app, billing system or commerce platform. It gives you a field-level migration and reconciliation sheet, a cutover timeline, dry-run and cutover acceptance tests, and a scoping worksheet. Provider rules quoted here come from Stripe and Shopify documentation; your source and destination may differ, so confirm the route with your own providers.

The migration and reconciliation sheet

Fill one row per subscription for a pilot cohort before you plan the rest. The example below is illustrative: subscriber C104 pays GBP 20.00 a month including VAT, and the next charge is due on 1 December.

FieldSource (old system)Target (new system)Check before cutoverOwner
Customer IDC104New customer ID from the import mapping fileOld and new IDs linked in the sheetData migration lead
Subscription IDS-5531New subscription or contract IDOne target per source subscriptionData migration lead
Payment method and providerCard stored with the current processorImported method ID, or "re-authorisation pending"Method usable by the new billing system, not just copiedPayments owner
Payment pathProcessor export, same gateway connected, or re-authorisationRecorded per subscriptionPath confirmed by the provider in writingPayments owner
Price and currencyGBP 20.00GBP 20.00Same amount and currency, including any grandfathered pricePricing owner
DiscountNoneNoneRemaining discount cycles carried overPricing owner
TaxVAT includedVAT included, same rateTax-inclusive or exclusive treatment unchangedFinance
Shipping addressCurrent addressSame addressLatest change captured, not the export snapshotCustomer service
FrequencyMonthlyMonthlyInterval and interval count matchSubscriptions owner
Next charge1 DecemberFirst billing date 1 DecemberSame date; no charge earlierSubscriptions owner
StatusActiveActivePaused, cancelled and failed-payment states mappedSubscriptions owner
Source-system cancellationOld schedule cancelled on 24 NovemberNot applicableOld system shows no charge dueBilling owner
Reconciliation resultLast old charge 1 November, GBP 20.00Exactly one GBP 20.00 charge due, in the new systemSigned off for the cohortBilling owner

Do not treat a copied customer record as a usable payment method. If the provider does not support transferring C104's stored card, C104 completes the provider's re-authorisation route first, and the subscription moves only once the new method is attached.

Cutover timeline for one subscriber: final old charge, first new charge Illustrative timeline for subscriber C104, GBP 20 a month. 1 November: last charge taken by the old system. 10 to 14 November: pilot cohort dry run in a sandbox. 18 November: payment path confirmed for C104. 24 November, cutover: old schedule cancelled and new schedule created with first billing on 1 December. 25 November: reconciliation shows exactly one GBP 20 charge due, in the new system only. 1 December: first charge taken by the new system. 2 December: check one order and no old-system attempt. Before cutover only the old system may charge; after cutover only the new system may. Cutover for subscriber C104 Illustrative · GBP 20.00 a month ONLY THE OLD SYSTEM MAY CHARGE ONLY THE NEW SYSTEM MAY CHARGE 1 Nov Last old-system charge GBP 20.00 taken, reconciled 10–14 Nov Dry run: pilot cohort in a sandbox 18 Nov Payment path confirmed: imported or re-authorised 24 Nov CUTOVER Old schedule cancelled; new schedule created, first billing 1 Dec 25 Nov Reconcile: exactly one GBP 20.00 charge due 1 Dec First new-system charge GBP 20.00, one order 2 Dec Check: no old-system attempt
Illustrative cutover for one subscriber. Before cutover only the old system may charge C104; after it only the new system may. The cutover sits between the final old-system charge and the first new-system charge.

Inventory the subscriptions that must survive

Start with a count, not a migration script. Export every subscription with its status, then answer a short problem-to-decision note for the project:

Split the inventory by payment provider and method type early. Those two fields decide which subscriptions can keep their payment method and which need the customer to act. Grandfathered prices and provider-specific payment restrictions can change the route for a whole group. At no point should anyone on your side extract or handle raw card numbers: card data moves only between payment providers through their own secure process.

Supported token migration or customer re-authorisation?

A stored payment method is a reference held by a payment provider, and moving it is the provider's process, not a database export. Choose the route per provider and method type.

OptionHard constraintWorkaroundOperating ownerDisqualifying condition
Processor-to-processor payment data importThe old processor must export; lead times vary; not every method type or field transfersRequest the export first; keep charging existing customers on the old processor until import and mapping are donePayments owner with both processorsThe old processor will not export, or the method type is unsupported
Keep the existing gateway and connect it to the new platformThe destination must support that gateway and method type for subscriptionsRe-authorise the methods it cannot useEcommerce platform ownerGateway or method type not supported for recurring billing on the destination
Customer re-authorisationCustomers must act before their next chargeStart early; staged messages; keep the subscription on the old system until it is re-authorised or an agreed end dateCRM and customer serviceNone technical, but the cohort cannot cut over until it is complete
Copy customer records onlyNot a payment routeNone—Always: no usable payment method exists

What the providers' own documentation says:

Subscription apps also publish their own migration-in and migration-out guides; Recharge, for example, has separate articles on migrating to and away from its platform. Read the current version for your exact source and destination, because supported routes differ by provider and change over time.

Map identity, price, schedule and status

Reconcile identity first, then money, then time. Using the sheet above, a pilot cohort should pass these steps in order: inventory subscriptions and payment-method ownership; confirm the provider-supported payment path; map identity, prices and schedules; dry-run; cut over charging; reconcile and disable the old schedule.

Identity, money, timeCard sequence for mapping each subscription: link identity IDs first, then recreate the agreed price and tax treatment, then match the old next charge date, then map every status one to one.Identity, money, timeReconcile each subscription in orderIdentityLink old and new customer,subscription and payment method IDsfrom the import mapping filePriceRecreate the agreed price, remainingdiscount cycles and tax treatmentScheduleThe first charge in the new systemfalls on the old next charge dateStatusMap paused, canceled, prepaid andfailed-payment states one to one

Identity. Link old and new customer, subscription and payment method IDs from the import mapping file. Stripe's subscription import guide says customers you plan to charge automatically need a default payment method, otherwise subscription invoices cannot be collected. Shopify's guide says that for Stripe the payment method ID is required and Shopify "doesn't fall back to the customer's default payment method".

Price. Recreate the price the customer agreed to, not today's list price. Stripe's guide describes a placeholder "legacy plan" product with prices passed per subscription for legacy pricing models. Carry over remaining discount cycles and tax treatment explicitly.

Schedule. The first charge in the new system must fall on the old next charge date. Stripe's guide asks you to make sure the billing cycle anchor and start date reflect where each customer is in their term, and recommends its Subscription Schedules API, which lets subscriptions start at a future date so you can check the import before customers are billed. In Shopify, an imported contract carries a next billing date, and your app triggers each charge by creating a billing attempt ("You need to create billing attempts to trigger the billing schedule of a contract"); each billing attempt takes an idempotency key, which Shopify describes as "a unique key generated by the client to avoid duplicate payments".

Status. Map paused, cancelled, prepaid and failed-payment states one to one. A subscription in a retry cycle on the old system needs a single owner for that retry: finish it there, or move it with its state, but never both.

Dry-run charges and reconcile cutover exceptions

Run the pilot cohort through a sandbox first. Stripe recommends running the import process through a sandbox at least once before live mode, and its test clocks simulate subscriptions advancing through time, so you can watch the first renewal happen. Then use acceptance tests like these for the dry run and again at cutover:

Starting stateActionExpected resultAdverse resultEvidencePass/fail owner
C104 active, next charge 1 DecemberCut over on 24 NovemberOld schedule cancelled; one GBP 20.00 charge due on 1 December, in the new system onlyBoth systems show a charge dueDue-charge report from both systemsBilling owner
Subscription paused in the old systemMigratePaused in the new system; no charge dueReactivated by the importStatus comparisonSubscriptions owner
Customer cancels during the freeze windowMigrate from an earlier exportStays cancelledRevived from a stale snapshotDelta export after freezeData migration lead
Last old charge failed and is in retryCut overRetry owned by one system, as agreedRetried in both systemsPayment logsPayments owner
Customer changes address or frequency during the freezeChange request receivedChange applied once in the new systemLost, or applied to the old record onlyChange logCustomer service
Payment method not transferable; customer has not re-authorisedCohort cutover date arrivesSubscription stays on the old system, or follows the agreed ruleMigrated without a usable method; first charge failsCohort exception listCRM owner
Grandfathered priceMigrateLegacy price preservedCharged at the current list pricePrice comparisonPricing owner
Billing call times outRetry with the same idempotency keyOne chargeTwo chargesProvider charge listIntegration owner

The sign-off for each cohort is the reconciliation sheet: every subscription has a last old charge, a cancelled old schedule, a first new charge date and exactly one charge due. Both providers say to stop the old billing: Stripe says to cancel previous subscriptions as soon as the new ones become active "or you'll bill your customers twice", and Shopify strongly recommends pausing billing in the current application during migration to avoid double billing. None of this guarantees zero payment failures; issuer declines and customers who do not re-authorise will still need handling.

Cohort sign-offCard diagram of a cohort sign-off: every subscription shows a last old charge, a canceled old schedule, a first new charge date and exactly one charge due.Cohort sign-offRecorded in the reconciliation sheetLast old chargeRecorded for every subscription inthe cohortOld schedule canceledThe old system shows no charge dueFirst new charge dateThe old next charge date, in the newsystemExactly one charge dueOnly one system may charge asubscription at any moment

Verify migration experience and shutdown ownership

Ask any partner, including us, for a next-charge reconciliation record from a dry run, not a statement that subscriptions "were migrated". Then ask who switches off the old schedule, when, and how they would prove that no old charge is still queued. Check each claim in an evidence ledger:

ClaimSourceContributionResult definitionLimitDate
Customer and order data moved to a new platformDinarys Zebrapack caseMagento 1.9 to 2.4.1 migration; the page says customers, products and order history were transferred "without disruption"The case page's own descriptionNo subscriptions or stored payment methods describedPublic page, checked November 2026
Post-migration data inconsistencies reconciledDinarys Prostor caseERP data synchronisation in early sprints produced inventory inconsistencies that needed manual reconciliation; they were resolved in the first month by adjusting sync frequency and adding a validation layerThe case page's own descriptionInventory data, not billingPublic page, checked November 2026
Payment integration built for commerce platformsDinarys ConnectPay casePayment modules for Magento and Shopware: new payment method at checkout, authorisation flow after the order, payment status via APIThe case page's own descriptionPayment acceptance, not migration of stored methodsPublic page, checked November 2026
Partner has migrated subscription billingPartner's own case or a reference you can callAsk for the source and destination, the payment path and their part in itA reconciliation record with one charge per subscriptionAsk permission to speak to the referenceYour check

Our public case pages show data migration, post-migration reconciliation and payment integration work. They do not describe a payment-token migration or a subscription billing cutover, and we make no churn or billing-result claim for this kind of project. Judge us, and anyone else, on how a pilot cohort's reconciliation sheet looks.

Scope the parallel run and retained customer support

"Parallel run" should mean both systems live while cohorts move, never both systems charging the same subscription. Scope the project with this worksheet, and mark any unknown as unavailable rather than zero:

ItemWhat to recordTypical owner
Provider supportExport or import route per provider and method type; written lead time; feesPayments owner
CohortsOrder of cohorts, cutover dates, the next charge dates they coverSubscriptions owner
Cohort exceptionsPaused, prepaid, in retry, grandfathered price, unsupported methodData migration lead
Customer re-authorisationWho must act, messages, deadline, what happens if they do notCRM and customer service
Dry runsSandbox runs, test-clock renewals, pilot cohort sign-offQA and billing owner
Cutover operationsFreeze window, old schedule disabled, new schedule enabled, reconciliation reportBilling owner
Retained supportDecline monitoring after the first renewals, customer questions, refund rule for any double chargeCustomer service and finance
UnknownsItems not yet answered, marked unavailableProject owner

Two adjacent decisions belong elsewhere: how the subscription lifecycle should work after the move (see our guide to ecommerce subscription management), and whether to replatform at all (see ecommerce replatforming).

Your next step

Take your subscription export and fill the sheet for ten subscriptions: some active, some paused, one in a failed-payment retry, one on a grandfathered price, one with a payment method your destination may not support. Ask each payment provider in writing which route they support. Mark every field you cannot yet reconcile. That is your migration brief.

If you would like a second view, send it to Dinarys. Our ecommerce replatforming consultancy team will review the sheet against your source and destination, mark which subscriptions can keep their payment method and which need re-authorisation, and propose a cohort and cutover plan with the reconciliation checks it depends on.

Let professionals meet your challenge

Our certified specialists will find the most optimal solution for your business.

Please enter valid name
Please enter valid company
Please enter a valid phone
Please enter valid E-mail
Message is too short

    Your message has been successfully sent. We will be in touch shortly! Success icon