Articles on: Migration

Migrate from Recharge Legacy

  1. Pre-requisites
  2. Connect Payment Provider to Shopify
  3. Migrate from Recharge
  4. White glove migration walkthrough
  5. Need help?



Pre-requisites


  1. Loop widget must be live on the storefront and account page should point to Loop customer portal (guide) (read more)
  2. Payment provider that is connected to Recharge must also be connected to Shopify as secondary (guide)
  3. Share payment platform API token with loop team so that we can fetch payment token information from respective platform (guide)
  4. Share Recharge API key created with write access to all available scopes with Loop team (guide)



Connect Payment Provider to Shopify


In this section, we will guide you through how you can connect your current payment provider on recharge as secondary on Shopify admin.


This is mandatory for a native subscription based platform like Loop to be able to bill the imported payment methods and subscriptions from the Recharge app


Identify which payment provider you are currently using on Recharge


Head over to the Recharge app from your Shopify admin and then go to Settings > Payment. This will land you at the page that is shown below, where you can check which payment provider you are currently using.



Based on the Payment processor listed in your Recharge app → you would need to connect the appropriate payment provider to Shopify as secondary by following this guide.


Note that it is possible to have Stripe and Authorize can be setup as primary providers in your Shopify store instead of Shopify payments.


In such cases → there is no need to connect the payment provider as secondary in Shopify (provided that the same provider is used in Recharge)


Share API tokens from the payment provider


Based on the payment provider that you have connected on your Recharge, the steps will vary. Follow the guides mentioned below to fetch the API tokens and share it with the Loop team.


  1. Authorize (guide)
  2. Stripe (guide)
  3. Braintree (guide)
  4. PayPal (guide)


For Braintree and PayPal - Recharge requires you to connect Braintree to the app. This means that loop team is able to fetch the required information directly from the Braintree API keys shared.


Note that this only applies to recharge and not for other legacy subscription apps / platforms.


If you are using PayPal on Recharge, then you would need to ensure that PayPal is set up on the store with support for the recurring billing feature as well. (Read more)


For Stripe - We would be requiring the Live API secret key to be shared with the Loop team.


--

Migrate from Recharge Legacy


Once you have satisfied the prerequisites mentioned above, the loop team will be able to help you bring subscriptions over from your Recharge app.


Please reach out to us on support@loopwork.co with the required information and our team will help you get things over the line with our dedicated migration for a white glove migration experience on any of our paid plans (starting at $99/month)


To understand more about the options you have while migrating to loop, refer to this article.


Here is a quick email template to kick-start things if you have not been in touch with a team member from Loop already 😉


Subject line : {Brand Name} Migration from Recharge Legacy -> Loop



Email content

Source platform - Recharge Legacy

Recharge API key - {insert Recharge api token}

Payment platform API key - {insert payment platform api token}



Our Onboarding / migrations team will get in touch with you shortly and suggest a few days as per the availability.


--


White glove migration walkthrough


This section details the overall steps taken by the Loop team on the scheduled migration date.


  1. Loop team will take an export from the Recharge API through the shared API tokens.
  2. Once the data has been exported from the APIs, Loop team will convert it into the standard migration data format of Loop.
  3. Once the data has been fetched from Bold, the migration expert will begin the import at the scheduled time.
  4. Post subscription migration completion, Loop team will go proceed with actioning a bulk cancellation action on Recharge through their APIs (reference)
  5. A detailed migration report (reference) will be shared with the merchant, along with a 1:1 mapping between the contracts in both platforms for easy review.
  6. Merchant is then advised to do an overall review by spot checking a few contracts in between and ensuring data parity.
  7. Loop team will wait to hear back on the data review and migration confirmation requested in (6) and any open points on the same.


Point (4) ensures that no customer is doubly charged due to the subscription contract being active on both platforms.


If there are any custom requirements for the migration like price update, variant swapping, bundle migration, prepaid subscriptions etc.


The migration team would need to be informed at least a week in advance so that we can have this accommodated on our end.


Please note that the migrated subscription count will be lower than the count reported in recharge. We group the contracts based on the charge ID property of Recharge to ensure that all products that are to be billed in the same charge are grouped the same in loop. Reasoning → This is because each product that the customer is subscribed to is counted as an individual subscription by the Recharge system. Whereas a subscription can contain multiple products in loop.


Recharge - 1 line item (variants/products) = 1 subscription. Loop - multiple line items (variants/products) in 1 subscription



Need help?


If you are running into any issue while following along on the article (or) you simply have doubts on the same, feel free to block a time with us by clicking here



Alternatively, you can also choose to email us over at support@loopwork.co

Updated on: 25/02/2025

Was this article helpful?

Share your feedback

Cancel

Thank you!