GoCardless to WooCommerce Subscription Migration

Hey Cian, Can you confirm which WooCommerce GoCardless integration is currently in use, and whether it supports linking imported subscriptions to existing GoCardless mandate references without creating new mandates?

- Which WooCommerce subscription and GoCardless integration plugins are currently being used? Could you please confirm the exact WooCommerce Subscriptions plugin and GoCardless payment gateway/plugin currently installed on the website?

- Do you have a complete list of subscription plans and how they map between GoCardless and WooCommerce?

- How many active subscriptions are expected to be migrated, and are there any paused, failed, cancelled, or pending subscriptions that should be excluded?

Before getting started I have a few technical questions that will help me plan the migration accurately and avoid any assumptions going in.
1. Which GoCardless integration is currently installed on WooCommerce?
There are several plugins that handle this — the official GoCardless extension, Subscriptions by Prospress, and a few third-party options. How the mandate token is stored at database level differs between them and determines the entire import approach.
2. Is there a staging environment in place, and is GoCardless sandbox connected to it?
This is needed before the testing phase can be properly planned. If sandbox isn't configured on staging, that's something we'd need to set up or work around before any renewal testing can happen.
3. Do the GoCardless-only subscribers exist as WooCommerce users at all, or are they completely absent from the site?
If they have no WordPress user account linked, customer records will need creating before subscriptions can be imported. That's manageable but worth confirming early as it affects the order of work.
4. How many distinct subscription plans are there, and are the pricing amounts consistent between GoCardless and WooCommerce?
If a plan exists in GoCardless at one amount but is listed differently in WooCommerce, that needs resolving before any mapping begins. Even small discrepancies can cause issues post-migration.
5. Are any subscribers currently paused, in arrears, or carrying a failed payment in GoCardless?
Those records need to be handled separately from the main migration. Importing a subscription tied to a troubled mandate creates problems from day one and they're better identified and isolated early.
6. Who on your side will be available to make decisions on edge cases during the data cleaning phase?
Duplicates, ambiguous records, and mismatched entries will come up. Having a clear point of contact who can give quick sign-off keeps the project moving without unnecessary delays.
Happy to get started as soon as I have clarity on these — they'll allow me to plan each phase precisely and flag anything that needs addressing before the migration begins.

Are the GoCardless-only subscribers associated with existing WooCommerce customer accounts, or will new customer accounts need to be created?

Before providing a final migration plan, I have a few questions:

• Which GoCardless integration/plugin is currently being used with WooCommerce?

• Approximately how many of the 1,000+ subscribers exist only in GoCardless and not in WooCommerce?

• Are there multiple subscription products/plans, or a small fixed set of plans?

• Do monthly and annual subscribers have different billing logic, pricing, or renewal rules?

• Do you have a staging environment where migration testing can be performed safely?

• Are all existing mandates active and linked to customer records that can be exported from GoCardless?

• Do subscription start dates, next payment dates, and billing history need to be preserved in WooCommerce?

• Are there any customers with multiple active subscriptions that need special handling?

• What version of WooCommerce Subscriptions and WordPress are you currently running?

• Would you prefer a fully automated migration script that can be reused, or a one-time controlled migration process with validation checkpoints?

• Is there a specific maintenance window available for the final migration to minimize billing risks?

Before providing a final migration plan, I have a few questions:

• Which GoCardless integration/plugin is currently being used with WooCommerce?

• Approximately how many of the 1,000+ subscribers exist only in GoCardless and not in WooCommerce?

• Are there multiple subscription products/plans, or a small fixed set of plans?

• Do monthly and annual subscribers have different billing logic, pricing, or renewal rules?

• Do you have a staging environment where migration testing can be performed safely?

• Are all existing mandates active and linked to customer records that can be exported from GoCardless?

• Do subscription start dates, next payment dates, and billing history need to be preserved in WooCommerce?

• Are there any customers with multiple active subscriptions that need special handling?

• What version of WooCommerce Subscriptions and WordPress are you currently running?

• Would you prefer a fully automated migration script that can be reused, or a one-time controlled migration process with validation checkpoints?

• Is there a specific maintenance window available for the final migration to minimize billing risks?

Cian, do you currently have a complete and reliable mapping of each subscriber to their GoCardless mandate ID (and is that data consistent across all records), or will part of the mandate-to-customer matching need to be rebuilt from transaction history or exports?

Which WooCommerce subscription and GoCardless integration plugin are you currently using, and have you already confirmed that it supports attaching subscriptions to pre-existing GoCardless mandates without customer re-authorisation?