To migrate your customers into ReCharge, you will need to format your exported data into our Migration Template CSV. A copy of the template can be found here: ReCharge-migration-template.csv The data needs to be in this format for our system to import it correctly.
Please be sure:
- to not include any special or strange characters in the data
- to not remove or change the headers of the file
- to not use zero values for cells with no data and to leave them blank instead
- you’ve added all products that your customers have been subscribed to into the Ruleset in your ReCharge Dashboard. If you don’t want to offer these products anymore, you can make them hidden in Shopify after you’ve added them into your ReCharge Ruleset.
- if you use a filter in Excel, ensure you haven’t inserted blank columns between the default columns we’ve set. If you want to use a filter in Excel before you turn it on, select all data in the spreadsheet. That way, when you sort the data, you will ensure that you won’t mix them up.
(M) refers to a mandatory field and (O) is an optional field. For mandatory fields, please make sure you have entered values in every row of that column.
This is the Subscription Ruleset ID number for the ruleset containing the product in ReCharge. You can find this ID number by clicking on a ruleset in ReCharge. The number appears at the end of the URL.
This is the name of each product the customer has on file. If a customer is subscribed to more than one product then each product should be on a separate row. The name doesn't need to match perfectly, but it should be easy for us to tell which product to look for in ReCharge.
The is the name of the variant for each product. If you do not have variants, you can leave this blank.
The product ID of the original product (not the hidden product).
The variant ID of the original product (not the hidden product). Even if you do not have variants, Shopify still gives each product a default variant ID. You can follow this guide from Shopify on how to find the variant IDs.
How many of each product the customer will order each renewal date (or shipping date for prepaid orders).
The price the customer will pay per item each renewal date. This does not include shipping, taxes, or quantity. It should be the product price per unit without the currency symbol.
You can enter whatever price you want. That price will be used for that subscription until the customer cancels their subscription or changes the product. This price does not have to match the current price of the product on Shopify, if for instance, you want to give certain customers a grandfathered price.
If you charge shipping/tax, it will be added to each recurring order once it is migrated into ReCharge.
This is the type of unit used to schedule charges. There are three options to be added here: month, week, or day.
The number of months, weeks, or days between each charge. If the customer is charged every month, you will enter 1 in this column. If they are charged every 6 months, you will enter 6 in this column, etc.
The same logic is used here as for charge_interval_unit_type. For monthly, enter month, for weekly, enter week, for daily, enter day.
This should almost always be the same number as your charge_interval_frequency, unless this is a prepaid subscription; meaning, you ship more often than you charge. If you have prepaid subscriptions, then you will set the charge frequency to how often you charge, and the shipping frequency to how often you ship. So for a 3-month prepaid subscription that is delivered every month, you will enter a charge frequency of 3 and a shipping frequency of 1.
An optional field for stores who charge every customer the same day each month, regardless of what day they signed up. For example, you charge every customer on the 10th of the month, so you would enter 10 in this column.
The date the customer will be charged for their first recurring payment in ReCharge. This date should never be in the past, and the earliest charge date should be the day after you cancel your old system after importing to ReCharge. The format should be MM/DD/YYYY. It is recommended that you enter these dates well enough into the future. This will allow time for importing that data and data checks.
The list of customers and corresponding Customer IDs you will download from the Stripe/Braintree Dashboard. Please notice that we will need Customer IDs, not tokens.
You can enter both Stripe and Braintree customer IDs in this column. Stripe IDs will always begin with cus_XXX, and Braintree IDs are always all numbers, no letters. In the case that you have moved your customers from Stripe to Braintree, it is possible they have kept their previous IDs (cus_XXX).
For Authorize.Net customers, you will add two additional columns into the CSV, and leave the customer_stripe_id column blank:
You can download your customer list with their customer IDs from the Authorize.net Dashboard. Here is an article that will assist with finding the export.
This is the customer's creation date in your old system. The format should be MM/DD/YYYY.
The email address for the customer's account in ReCharge and Shopify.
The first name of the shipping recipient. Please do not include any strange or special characters.
The last name of the shipping recipient. Please do not include any strange or special characters.
This is the customer's phone number. You can use any data format you want.
The primary street address of the shipping recipient. Please do not include any strange or special characters. Also, ensure you have the address in every row in the case of multiple subscriptions.
The secondary street address of the shipping recipient.
shipping_city, shipping_province, shipping_zip, shipping_country (M)
The city, state, province, zip code, and country of the shipping recipient. Please do not use abbreviations for provinces.
Company name of the shipping address.
billing_first_name and billing_last_name (O)
You can fill this out If the billing name is different from the shipping name. If this is blank, it will default to the shipping name.
billing_address_1, billing_address_2, billing_city, billing_postalcode, billing_province_state, billing_country, billing_phone (O)
You can fill this out If the billing address is different from the shipping address. If this is blank, it will default to the shipping address.
You need to add these columns for specific situations.
For prepaid subscriptions
The date the customer was charged for their current cycle. This will tell our system when their current prepaid cycle began and how many shipments there are before the customer is charged again. This way, we’ll know if the customer is in the middle of the billing cycle, and they won’t be billed for future shipments until the next charge cycle begins.
For customers who are in the middle of their current prepaid cycle please be sure to enter the date in the column named last_charge_date. That is the date the customer was charged for their current cycle. We use this info in conjunction with shipping frequency to indicate when their current prepaid cycle began and how many shipments customer should get before he should be charged again.
If the subscription should renew you will enter the next_charge_date also. If it shouldn't you will add last_charge_date and just ignore next_charge_date. But you will need to add an additional column named number_charges_until_expiration and value of 1.
For inactive/cancelled subscriptions
If the customer has an inactive subscription, you should enter cancelled in this column. Otherwise, leave it blank.
For legacy shipping prices
The name of the legacy shipping rate.
The price of the legacy shipping rate.
NOTE: The shipping rate entered in these columns will be used for all recurring orders for this subscription.
For gift or expiring subscriptions
If you have a gift subscription that expires after the cycle ends, then you would add this column and enter the number of charges that should occur before the subscription expires. So if the customer pays for a gift subscription, then the first payment would count as one charge. If the subscription doesn't renew after this charge, then you would enter 1 in this column.
For custom Line Item Properties
If you have custom properties for products using line items in JSON format in a single row, then we’ll add these to the customer in ReCharge after they're imported.
Note: the entire JSON string needs to be enclosed in quotes.
Here's an example of how it should look for each customer/row:
If you are currently using Spreedly to vault credit cards, we can use this ID to match the customer with their payment data in Spreedly.