Subscription Migration Requirements

  • Resolved Digital Duck

    (@digitalduckplugins)


    9 months, 3 weeks ago

    Hi,

    Hope you’re having a great week.

    I’ve got a site that’s been using the Brainstorm Force Stripe plugin. We’re looking to migrate to your one, but am wondering what steps we’d need to take.

    We’re a subscription based site, and realistically, I’d just need to know what the meta keys/values would need to be set to, to make payments continue working.

    My guess so far is,
    Change the meta_key in usermeta to set the stipe customer id,
    Change the gateway_id in the payment_tokens

    If you could let me know what the values would need to be changed to, and if there’s any other things I’d need to look into changing that would be great.

    Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moses M. (woo-hc)

    (@mosesmedh)

    9 months, 3 weeks ago

    Hi @digitalduckplugins,

    Thanks for reaching out, and I hope you’re having a great week too.

    Migrating from the Brainstorm Force Stripe plugin to the official WooCommerce Stripe gateway—especially on a subscription-based site—is a bit more complex than simply updating meta keys. Subscriptions rely on saved payment tokens, customer IDs, and tight integration with the payment gateway. Modifying these values manually isn’t officially supported and could lead to failed renewals or unexpected behavior.

    Typically, when a customer subscribes using the official Stripe plugin, WooCommerce saves their Stripe customer ID in the user meta (_stripe_customer_id), and their payment method token is stored in the wp_wc_payment_tokens table with the gateway_id set to stripe. This token is then linked to the subscription. However, since Brainstorm Force’s plugin uses a different structure, the tokens and customer IDs may not be fully compatible with the official plugin’s expectations.

    If you’re still considering a manual migration, you would need to make sure the Stripe customer ID is correctly saved in user meta, and that the wp_wc_payment_tokens table contains the necessary token details, including the gateway ID, brand, last four digits, and expiry. The subscription must also be linked to this token. But again, this is not a supported or safe path without developer oversight.

    The safest approach would be to set up a staging site and test thoroughly. Another option is to ask customers to re-enter their payment information upon renewal, which avoids backend complications. Alternatively, consider hiring a WooExpert or a developer from Codeable to assist with a secure and reliable migration.

    If you’d like more tailored guidance or support with this, I recommend opening a ticket with WooCommerce.com: https://woocommerce.com/my-account/create-a-ticket/. They can help clarify what is feasible with your current setup and subscription data.

    Plugin Support Feten L. a11n

    (@fetenlakhal)

    9 months, 2 weeks ago

    Hi there,

    Since we haven’t heard back, I’ll mark this as resolved for now. We’re here if you need us!

    Apart from this, mind leaving a quick review? 😊 https://ww.wp.xz.cn/support/plugin/woocommerce-gateway-stripe/reviews/#new-post

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Subscription Migration Requirements’ is closed to new replies.