Overview
The following document contains the requirements and process for moving your existing subscriptions into Submarine.
If your existing platform uses Shopify and Shopify Payments this process may be as simple as providing us access to your existing Subscription platform, if you are migrating from an external platform then we will need to review what information is available and how we can move the payment methods.
Prerequisites
- Submarine app installed on your Production store
- Submarine Subscription Plan Groups have been created
- Customers created in Shopify
- Access to existing Subscription data
- Access to existing payment methods
Required data
Identifier - We need each subscription to be provided with a uniqueID. Each row of data for a subscription must include the same value in the UniqueID field.
Customer email - This email must match a customer email in Shopify that already exists.
Next delivery at - We need to know the next delivery date that is scheduled for this customer.
Subscription status - We support active, paused, or cancelled.
Shipping method - The shipping method for the customer that aligns to a shipping method in Shopify.
Products - Each item in the subscription will need a single line with the variant ID from Shopify and a quantity.
Product or Variant SKU -
Qty -
Subscription group plan ID—To allocate this subscription to the right Submarine group and plan, we will need to know the plan ID to match it. This can be done inside the CSV, or we can map them as long as you provide the frequency for the Subscription.
Optional data
Created at - If you would like to backdate the creation date of your Subscription, then you can provide a UTC timestamp here.
Delivery address—If you want to provide a different address than the default address on the Shopify customer, please do so in separate columns.
Columns to include: delivery_address_1 delivery_address_2 delivery_city delivery_postcode delivery_province_code delivery_province_name delivery_country_code
Upcoming order cycle state - If your current system supports skipping upcoming orders then we need a way of translating that into Submarine. To do this we ask the data is provided as a
cycle 1 = skipped, cycle 2 = scheduled
Discount codes - existing discount codes that are attached to a customer Subscription
Custom attributes - if you would like to pass additional data into the Subscriptions custom attributes, you will need to provide these to us.
Payment Migrations
- Each payment migration differs depending on your current platform. When you reach out to us, we’ll set up a time to discuss the process for your current payment gateway.
Sample CSV files
Below you can find links to templates with example data inside.
Process
- Reach out to us via help@getsubmarine.com about getting started with your migration
- We’ll set a call or ask for further information and review the current data
- After that, we will provide any outstanding information that is required for us to perform a test migration
- Once we have confirmed the test migration we will schedule a time to do the full production migration
- Please note we have limited space available for these as we like to ensure each migration has enough prep before and monitoring time after.
- If you are actively processing subscriptions in your previous application then we will need to set specific timings to turn on Submarine process to avoid double charging your customers.