If you are having issues with your migration, this guide might be able to help. The guide provides common questions and answers around the migration process. For general information, visit Migrating to Recharge.
- How will customers be notified of their new account within Recharge?
- When will my customers start being charged after being imported into Recharge?
- In the Migration Template, how should I set up my Next Charge Dates to ensure I don’t miss any billing dates and none of my customers are charged twice?
- What payment processors are compatible with Recharge? Can I migrate the same account I was using in my previous subscription platform?
- Will Recharge edit or update my Migration File on my behalf if they find any errors?
- Will Recharge notify my customers of changes on their account due to the migration?
- How do my customers update their billing information while my data is being migrated?
- I recently completed my migration, but none of my recurring billing is processing. What’s happening?
- When should I schedule my migration?
- I am already using the Recharge Checkout on Shopify, but I’m setting up a brand new Shopify store and need to move all of my Recharge data into it. How can I do this?
- I am having trouble finding my product’s Variant IDs. Where can I find these at?
- Are there any differences between a prepaid subscription and a normal subscription?
- Does the migration process trigger any webhooks?
How will customers be notified of their new account within Recharge?
Shopify has a Bulk Account Inviter tool available for Shopify Plus stores to accomplish this. If you are not a Shopify Plus store, you can opt to use a third-party application like Bulk Account Invite Sender. Once your customer has accepted the invitation, they will be able to enter a new password and complete their account setup.
When will my customers start being charged after being imported into Recharge?
Customers are charged on their next charge date based on what is inputted into the migration template.
In the migration template, how should I set up my Next Charge Date to ensure I don’t miss any billing dates and none of my customers are charged twice?
In order to migrate your customers seamlessly, you need to determine what date your migration will take place. There should be no charge dates in your migration file that falls before this date as those will be processed by your old system. To be safe, you should move charge dates at least 3 days out from your migration date to ensure you have enough time to complete the post-migration checklist and work with Recharge to remove the hold from your account.
For example, let's say you plan to launch Recharge on January 1st. We recommend you export the data from the old system on or after January 3rd, which gives you a few days to ensure new subscribers are flowing through Recharge correctly. Your official migration date is January 8th, giving you a few days from the 3rd to the 8th to validate your data and ensure the file is set up correctly. Since you will be migrating on January 8th, the absolute soonest you should set your next charge dates in the migration file is January 9th.
Now let's say you have a customer whose next charge date is January 5th. Since this charge falls before the migration date, you should update this line in your file to be the customer’s next charge date, which would be February 5th. Your old subscription platform will handle the January 5th charge, and then this customer will process through Recharge on its February 5th renewal.
What payment processors are compatible with Recharge? Can I migrate the same account I was using in my previous subscription platform?
Recharge currently offers support for Stripe, Braintree, and Authorize.net. Please refer to our Payment Processors and Payment Processor FAQ for more details. As long as you are using one of our supported payment processors, you can connect your existing account to Recharge.
If you are migrating over a Stripe account, make sure there are no Stripe Subscriptions setup. If you see any subscriptions, ensure they are cancelled to prevent double-billing.
Will Recharge edit or update my migration file on my behalf if they find any errors?
Recharge is unable to make any edits or updates to your migration file. If we notice any issues, we will inform you of the changes that will need to be made before the migration can continue.
Will Recharge notify my customers of changes on their account due to the migration?
Recharge will not contact or send any migration specific notifications to your customers. If there are any notices you feel are needed to be sent to customers, it is your responsibility to send that information to them.
How do my customers update their billing information while my data is being migrated?
If your payment processor remains the same between your old system and Recharge, customers will be able to still update their billing information in the old system while the migration is occurring. If you are changing payment processors or the old system is no longer available, they will need to wait until the account is created in Recharge after the migration is completed before updating their billing information.
I recently completed my migration, but none of my recurring billing is processing. What’s happening?
When the migration is finished, a hold is put on your account until the data has been reviewed and written confirmation that the data is correct has been given to Recharge. Once we receive confirmation from you, we will remove the hold from your account and recurring billing will occur as normal. Refer to our Post-migration checklist for more information on this process.
When should I schedule my migration?
Recharge migration experts are staffed Monday - Friday 7:00am PST - 4:00pm PST. We highly advise you to schedule your migration earlier in the week to ensure a migration expert will be able to assist you with any issues you may encounter. We discourage migrations from being scheduled on a Friday to prevent issues from occurring throughout the weekend when migration experts are not staffed.
I am already using the Recharge Checkout on Shopify, but I’m setting up a brand new Shopify store and need to move all of my Recharge data into it. How can I do this?
We highly discourage a Recharge to Recharge migration. This is not as simple as flipping a switch to move your Recharge account to a new Shopify store. Due to the way Shopify handles product IDs, variant IDs, and much more, this action would follow the same process as a normal migration. Refer to our Migrating to Recharge guide for more information on how to initiate this process. Keep in mind, our migration process can’t import order history into Recharge. You will need to manage historical data outside of Recharge.
I am having trouble finding my product’s Variant IDs. Where can I find these?
Recharge Checkout on Shopify
In Shopify, there are a couple of different ways to find the Variant IDs tied to each product.
Using the JSON URL
When logged in to your Shopify Admin page, add /admin/variants.json to the end of the address bar so you navigate to:
Once the URL is loaded, you should see variant data populated in the JSON format on the screen. You can also modify the URL to show you other attributes such as title and product ID:
If you have more than 49 variants, you will also need to append page destinations, such as &page=2, until all variants are accounted for.
You can also find the Variant ID of the product once it is added to the cart on your website. If you navigate to the cart page and append .js to the end of the URL, it will display all of the attributes of the cart item for you.
Are there any differences between a prepaid subscription and a normal subscription?
If a subscription ships more frequently than charged, it is considered a prepaid subscription. Prepaid subscriptions need a little more attention to detail when migrating as fixing issues with prepaid data is more complicated than normal subscriptions. There are three columns to pay extra attention to while creating your migration template when it comes to prepaid subscriptions.
charge_interval_frequency and shipping_interval_frequency
The charge_interval_frequency should be greater than your shipping_interval_frequency. For example, if you have a 6 month prepaid subscription, and the customer receives a shipment every month, the charge_interval_frequency would be set to 6 while the shipping_interval_frequency would be set to 1. This will ensure customers are charged every 6 months, but receive shipments every month.
The last_charge_date represents the date the customer’s current prepaid subscription cycle started. The Recharge system will use this date and the frequencies to figure out how many $0 shipment orders remain and when shipments will be sent.
If customers are charged on a specific day of the month, you will need to ensure the day on your last_charge_date matches your charge on day of month parameter. If you have a cutoff day, you may need to edit the month to coincide with the cutoff shipment.
Does the migration process trigger any webhooks?
Yes, the migration process will trigger the
charge.create webhooks. If you don’t want these webhooks to trigger for imported customers you’ll need to disable any tools or apps using these webhooks while the migration is happening.