This guide explains the process of migrating from Bold V1 to Recharge. Your migration process depends on whether the payment processor in-use is Stripe, PayPal or Braintree, or Authorize.net.

Prep for migration

Follow the instructions for getting started with Recharge to prepare for your migration. This ensures that your store continues operating throughout the migration process, allowing all new subscribers to flow through the Recharge platform, while also eliminating the possibility of missing customers during the data pull from your old platform.

Be sure to fill out the Migration Questionnaire (click “Migrate to Recharge” at the top or bottom of the page) when setting up your store for the first time. Submitting this form informs our team that you are in the preparatory phase and will be migrating your existing data soon.

Stripe

Use the migration template to format your data from Bold V1 and Stripe. This ensures that there are no issues when importing the data into Recharge.

Formatting support

Recharge is not able to offer formatting support.

How to migrate

When migrating from Bold V1 with Stripe to Recharge complete the following steps:

1. Plan your ideal go-live and migration date. The go-live needs to happen first, and migration afterward. If you prefer a quick transition, work towards both in parallel.
2. Create a duplicate theme in Shopify. This is the theme that is published when you go-live with Recharge.
3. Reach out to Bold support and request the removal of all their code from the duplicate theme.
4. Reach out to Recharge support to get the Recharge code added to the duplicate theme.
5. Publish the subscription widget and your duplicate theme in Shopify when you are ready to go live with Recharge.
6. After Recharge is live, pull the final data export to prepare for migration. This includes a combination of customer data, subscription data, and payment processor data.
7. Disconnect Stripe from Bold and connect it to Recharge. If Stripe is left connected to both tools at once, Stripe could create a duplicate account in Recharge and cause errors with the migration import.
   
   
   Note: If you are on the Shopify Checkout Integration version of Recharge, you will need to contact Recharge Support to turn on the ability to link legacy payment processors for migrated customers.
8. Validate your formatted migration file through the Recharge Bulk Actions tool. If your file is:
• More than 500 rows: Reach out to your Recharge Implementation contact to process the import.
• Less than 500 rows: Click process and finish the migration on your end. 

PayPal or Braintree

Use the migration template to format your data from Bold V1. This ensures that there are no issues when importing the data into Recharge.

To migrate subscribers on the payment processor side from either Braintree or PayPal, Braintree customer IDs are required. Make sure to confirm with Bold that you have access to the customer IDs.

About Braintree vs PayPal:

Recharge supports PayPal via Braintree, a subsidiary of PayPal. If your existing PayPal subscribers are not in Braintree, the Braintree and PayPal teams may be able to help migrate your PayPal subscriber information into Braintree. Reach out to PayPal and Braintree directly to request they import your PayPal payment data into Braintree. Specify that the payment data is used for Recharge recurring subscription billing and not transferring recurring information.

If the Braintree and PayPal teams determine the transfer is not possible or you are unable to get access to those Braintree IDs for your existing subscribers, there are two options to proceed with the Recharge migration:

• Leave PayPal/Braintree subscribers in Bold: You can encourage these customers to re-subscribe on your site, or allow them to churn naturally. Their Bold customer portal will no longer be accessible and they will have to contact your customer support team to update their subscription.
• Cancel all PayPal subscribers in Bold: Encourage these customers to re-subscribe on your site.

Formatting support

Recharge is not able to offer formatting support.

How to migrate

If you are migrating from Bold V1 with Braintree to Recharge or do not have API access with Bold, complete the following steps:

1. Plan your ideal go-live and migration date. The go-live needs to happen first, and migration afterward. If you prefer a quick transition, work towards both in parallel.
2. Create a duplicate theme in Shopify. This is the theme that is published when you go live with Recharge.
3. Reach out to Bold support and request the removal of all their code from the duplicate theme.
4. Reach out to Recharge support to get the Recharge code added to the duplicate theme.
5. When you are ready to go live with Recharge, publish the subscription widget and publish your duplicate theme in Shopify.
6. After Recharge is live, pull the final data export to prepare for migration. This includes a combination of customer data, subscription data, and payment processor data.
7. Disconnect Paypal/Braintree from Bold and connect it to Recharge. If Paypal/Braintree is left connected to both tools at once, Paypal/Braintree could create a duplicate account in Recharge and cause errors with the migration import.
   
   
   Note: If you are on the Shopify Checkout Integration version of Recharge, you will need to contact Recharge Support to turn on the ability to link legacy payment processors for migrated customers.
8. Validate your formatted migration file through the Recharge Bulk Actions tool. If your file is:
• More than 500 rows: Reach out to your Recharge Implementation contact to process the import.
• Less than 500 rows: Click process and finish the migration on your end. A hold will not be placed on your store if you process from your end.

Authorize.net

Use the migration template to format your data from Bold V1. This ensures that there are no issues when importing the data into Recharge.

Bold and Recharge both use a service called Spreedly to vault payment details via Authorize.net. This adds an extra step to the migration process, for Spreedly to migrate their tokens from Bold’s environment to Recharge’s environment.

The transfer of Spreedly tokens can take between one to two weeks. In order for the Spreedly transfer to contain all subscriber information, it is important to wait and make this request when you are ready to push Recharge live. Spreedly will not allow you to migrate interim subscribers’ payment data if you gain additional subscribers in Bold after the initial transfer request.

Formatting support

Recharge is not able to offer formatting support.

How to migrate

If you are migrating from Bold V1 with Authorize.net to Recharge complete the following steps:

1. Plan your ideal go-live and migration date. The go-live needs to happen first, and migration afterward. If you prefer a quick transition, work towards both in parallel.
2. Create a duplicate theme in Shopify. This is the theme that is published when you go-live with Recharge.
3. Reach out to Bold support and request removal of all their code from the duplicate theme.
4. Reach out to Recharge support to get the Recharge code added to the duplicate theme.
5. When you are ready to go-live with Recharge, publish the subscription widget and publish your duplicate theme in Shopify.
6. Reach out to Bold to request the transfer of Spreedly tokens.
   • Request the Spreedly tokens be transferred to Recharge’s environment, confirmation sent to migrations@rechargeapps.com.
7. Reach out to the Recharge Migrations team at migrations@rechargeapps.com, notifying them to expect the upcoming transfer.
8. Spreedly will send Recharge the export file, and a member of the Recharge Migration team will forward it to you. The file Recharge receives includes the old Spreedly token and the new Spreedly token. Your exports from Bold need to include the old Spreedly token to action the mapping file. At this step, also ensure that you have Authorize.net configured in Recharge so that migrated customers can be charged successfully.
   
   
   Note: If you are on the Shopify Checkout Integration version of Recharge, you will need to contact Recharge Support to connect Authorize.net for migrated customers.
9. Pull the final customer and subscription data exports from Bold to format them and the Spreedly tokens into the Recharge CSV template.
10. After formatting with the new Spreedly token, validate the migration file through the Recharge Bulk Actions tool. If your file is:
    • More than 500 rows: Reach out to your Recharge Implementation contact to run the import.
    • Less than 500 rows: Click process and finish the migration on your end. 

For two weeks between go-live and migration, new subscribers will go through Recharge while existing subscribers renew in Bold. Your Bold subscribers will not have access to their customer portal through the Shopify account section. Advise them to send subscription update requests by email to your support team.

FAQs

I don’t understand how to keep Bold and Recharge running on my store at the same time. Can you walk me through how this works?

You can install Recharge on a duplicate theme in Shopify, on a copied theme in BigCommerce, or on the active one. If you choose to use a duplicate theme, you will need to prepare to make the theme live before migration. This way, new customers will go through the Recharge checkout. Current customers in Bold will continue processing in the Bold system. If you choose to install Recharge on your active theme, you must uninstall the Bold code. That way Bold will not be present on your front-end storefront, but still continues processing the orders in the back-end. New customers will be able to sign up through Recharge. Bold will need to be cancelled entirely after the migration. It is highly recommended you reach out to Bold to ensure the processing does not continue.

What happens to the customers who already have a Shopify account?

If the customer already has an account in Shopify, they will be able to use the same account in Recharge as long as it is the same email address. They will also be able to use the same password as before.

See more information and frequent questions regarding the migration process in Migrations FAQ.