Migrating bundle subscriptions to Recharge Bundles
Migrate bundles created in another platform to Recharge Bundles. This guide provides an overview and instructions on how you can migrate bundles to Recharge.
Before you start
- Preset bundles and Customizable bundles with a fixed or dynamic price are supported bundle types for migration.
- All Recharge bundles are represented by a single Shopify product. This bundle product must be active and available on the Shopify online store sales channel.
- Bundles contents or the individual products that make up a bundle must be active and available in the Shopify online store sales channel.
-
Fixed-price customizable bundles: Bundle contents do not have to be added to Recharge, but if they are, those products cannot be configured as subscription only.
-
Dynamically-priced customizable bundles: Bundle contents must be added to Recharge with the same subscription type and frequencies as the parent bundle.
-
- All bundle contents must be added to the Shopify collection that is linked within the Recharge bundle settings.
-
You can import bundle contents for cancelled bundles, but there can be unexpected issues if one of the contents becomes unavailable in the future.
-
If the customer reactivates the bundle, they will be prompted to make updates when they access the customer portal. However, if they don’t make updates prior to the order processing, the charge will either contain old products or there will be a charge error.
-
Migrating bundles from another platform
You can use this process for all bundle subscriptions that were created and exist in an external platform.
To migrate bundles from another platform:
- Complete the migrations intake form and create a new bundle in Recharge with the same structure as the existing bundle setup. You must configure the settings to have the same variants and frequencies.
- Export your data from the external platform and complete the migration CSV template.
- Keep bundle contents and parent bundle products within the CSV when filling out the migration CSV template.
- Pricing for dynamic bundles should be listed as 0 in the migrations CSV. The total price of the bundle will be dictated by bundle contents rather than the parent bundle product.
- If the external platform data has all of the bundle contents grouped by a unique subscription ID, use this ID for the unique bundle ID. Add the Bundle ID in the line_item_properties column on the migrations CSV template with the format
[{“name”:”bundle_id”,”value”:”123456”}]
.- If there is not a subscription ID to use for the unique bundle ID, you will need to assign a unique bundle ID to all items within each bundle and add it to the
line_item_properties
column with the same formatting as above. Each bundle and selection grouping will share a unique bundle ID. - There may be edge cases where customers have more than one bundle and no unique ID to match them. These may need to be handled manually.
- If there is not a subscription ID to use for the unique bundle ID, you will need to assign a unique bundle ID to all items within each bundle and add it to the
- After your data is formatted and the line item properties are added, you must separate the bundle contents into a new sheet so the migrations CSV template only contains the parent bundle product. This new sheet will be converted to the Bundle contents import CSV later.
- Validate the file and once your file is ready, contact the migrations team to complete the import.
- Keep bundle contents and parent bundle products within the CSV when filling out the migration CSV template.
- Once you've completed the customer migrations import, export the bundle subscriptions from Recharge to get the subscription ID and line item property that contains the unique bundle_id.
- Map this file to the separated bundle contents sheet created in the last step and match the data based on the bundle ID line item property created in step 2.
- Format this file to fit the bundles CSV selection template.
- Validate the bundle contents import CSV file using the Bulk Actions Tool.
- Import your file once the validation is complete.
- Complete the post-migrations checklist to ensure your data is reviewed and accurate once the migration is complete.