Migration Template for Bold Subscriptions

Overview

If you are interested in migrating your current subscription customers to Bold Subscriptions on BigCommerce, please ensure that you request this through the Bold Sales team.

Once you are ready to migrate to Bold Subscriptions V2, please download and complete the Bold Subscriptions V2 Import Template CSV File (2 KB). Our Migrations team will be able to review this information, and import it to our app.

Please also note that full or partial migrations cannot be performed without the help of our Migration team. To fill out the form, please see our detailed explanation of the import template CSV columns, here:

 


 

A - order_id

Unique subscription identifier used for grouping line items together. Has to be unique, except where multiple lines should be part of the same subscription. In that case, they would be required to have the same group ID. 

Note: If multiple rows have the same order ID, then all entries in those rows should be the same except for the product information. (For example, platform_product_id, price, quantity, etc)

This information is required.

 

B - line_item_id

The line item id must be unique. Used to identify a row within the CSV. Best to be used in ascending order (1, 2, 3, etc)

This information is required. 

C - first_name

First name of customer who will be receiving the subscription. This information is required.

 

D - last_name

Last name of customer who will be receiving the subscription. This information is required.

 

E - company

This information is not required. When your customers input a company name within the checkout, this information could be added here. 

 

F - customer_email

Email address for the customer. Needs to be the same email address provided for the billing_email column. This information is required.

 

G - address1

This information is required.

 

H - address2

This section can be used for your customers apartment number, or other shipping information that was entered within the order. This information is not a requirement for the template.

 

I - city

This information is required.

 

J - province

This information is required for countries that ask for province/state during the BigCommerce checkout process.

Note: Do not abbreviate American states or Canadian provinces; they must be the full province or state name.

 

 K - country

This information is required.

Note: Do not use abbreviations. The full Country name should be filled out. (For example, Canada instead of CA) Here

 

L - zip

This information is required.

If you are in the US and your Zip code is 9 digits long, please put a dash in between. For example, 64735-1234

 

M - phone

This information is not required unless you require phone numbers for your orders in BigCommerce.

 

N - billing_first_name

This information is required. First name on the customer's credit card.

 

O - billing_last_name

This information is required. Last name on the customer's credit card.

 

P - billing_company

This information is optional. The company included with the billing information.

 

Q - billing_address1

This information is required, as the spreadsheet has to match the address stored on file for the customer's credit card.

 

R - billing_address2

This information is optional, but has to match the address stored on file for the customer's credit card.

 

S- billing_city

This information is required, and has to match the address stored on file for the customer's credit card.

 

T - billing_province

This information is required for countries that ask for province/state during the BigCommerce checkout process, and has to match the address stored on file for the customer's credit card.

Note: Please do not abbreviate American states or Canadian provinces, as the spreadsheet must be the full province or state. Has to match the address stored on file for the customer's credit card.

 

U - billing_country

This information is required. Has to match the address stored on file for the customer's credit card.

Note: Do not use abbreviations. All Countries should be written out in full. (For example, United States instead of US.)

 

V - billing_zip

This information is required. Has to match the address stored on file for the customer's credit card.

If you are in the US and your ZIP code is 9 digits long, please put a dash in between. For example, 64735-1234

 

W - billing_phone

This information is not required unless you require phone numbers for your orders in BigCommerce.

X - subscription_group_id

This information is required. Our migration specialists will help provide this information to fill out the template.

 

Y - platform_product_id

This information is required.

 Example

This information can be located within the URL, here:
Product_ID_Location.png

Please navigate to Orders > View > "Export All" > select "Default" template > Export. From here, search for the "Product Details" column. This information can also be found within the BigCommerce Importing & Exporting Products article

 

Z - platform_variant_id

This information is required. To find this information, please follow these steps:

  1. Within the BigCommerce admin, navigate to Advanced Settings > Storefront API playground.
  2. Select the Paginate products tab.
  3. Replace the payload on the right hand side with the following information:
    # Get a few products from the catalog 
    # Stores in pre-launch or maintenance mode may reject queries.
    # Access from Control Panel > Advanced Settings > Storefront API Playground
    # or browse privately and query against https://buybutton.store/graphql
    query paginateProducts(
    $pageSize: Int = 3
    $cursor: String 8
    # Use GraphQL variables to change the page size, or inject the endCursor as "cursor"
    # to go to the next page!
    ) {
    site {
    products (first: $pageSize, after:$cursor) {
    pageInfo {
    startCursor
    endCursor
    }
    edges {
    cursor
    node {
    # this entityId will be platform_product_id
    entityId
    name
    variants {
    edges {
    node {
    # this entityId will be platform_variant_id
    entityId
    # will need to cross reference SKU here
    sku
    }
    }
    }
    }
    }
    }
    }
    }
  4. Select the play button to run the query. 

    Note: This will return however many results pageSize is. For example, if you have 10 products the payload should havee $pageSize: Int = 10)

  5. Please see screenshot, below:
  6. Screen_Shot_2021-05-05_at_11.57.53_AM.png

  7. Use the SKUs found to map back to the product SKU found in the order export.

If you have any questions about these steps, please reach out to our Merchant Success team.

AA - price

Price, no decimals in cents. This information is required, and should be the exact price you want to charge the imported customer for the product. 

Please incorporate any automatic discounts your previous platform would have applied to the product price. The price you enter can be different than the current BigCommerce listed price if the migrated customers are on a legacy plan.

Taxes and applicable shipping will be calculated based on the settings created in BigCommerce.

 

 Example

If you had an item that is sold for $200.00, then it would show in cents as 20000. If you offered a 50% discount on this product, then it would be entered as 10000

 

AB - charged_currency

For example, CAD, USD, GBP, etc.

 

AC - base_to_charged_exchange_rate

The intended exchanger rate between the shop's base currency and charged_currency provided.

 

AD - quantity

This information is required. This numerical value is how many of that specific product they had subscribed to.

 

AE - next_ship_date

This information is required for all subscribers. This is the date for their first BigCommerce order to be processed by Subscriptions. This always needs to be a date in the future, scheduled at least the following day after the import has been completed.

Formatting for these dates is key. The required date format is YYYY-MM-DD 00:00:00 and must be converted to UTC.

 

AF - gateway_customer_id

If you used Stripe on your previous platform, we require a custom token or customer ID for each subscriber. This is typically formatted as cus_123456ABC67.

 Alert

If you are migrating from Braintree or Authorize.net, please leave this section blank.

If you are currently using Bold Checkout with a payment processor that is not Stripe, Braintree, or Authorized.net and are looking to import your subscribers into Bold Subscriptions, please contact our Merchant Success team to discuss this process further.

 

AG - gateway_payment_id

The customer's payment method token from the payment gateway. This information is optional when migrating from Stripe, and only identifies which payment method to use if a customer has multiple payment methods in Stripe.

If migrating from Braintree, please ensure that the Customer ID is added to this section.

 Example

If migrating from Authorize.net, please ensure that it is formatted like this:

<Customer Profile ID>-<Payment Profile ID>

 

AH - shopify_customer_id

This information is not required. Please leave this spot blank.

 

AI - purchase_date

Original subscription date. This information is required.

Formatting for these dates is key. The required date format is YYYY-MM-DD.

 

AJ - internal_notes

Plain text of internal notes on the subscription. This information is not required.

 

AK - active

This information is required.
Inactive means that the subscription is archived and inactive.

Active means that this is an active subscription, and should generate orders moving forward.

Paused means that this subscription has not been archived, but is currently not being processed.

 

AL - is_prepaid

This column should be 0.

 

AM - prepaid_duration

Please leave this column blank.

 

AN - prepaid_current_recurrence_count

Please leave this column blank.

 

AO - prepaid_continue_as

Please leave this column blank.

 

AP - interval_number

This is not required if an RRULE was provided. What number will associate with the frequency. For example: The number in the following: Every (1) week, every (15) days, every (3) weeks.

 

AQ - interval_type

This information is required if an RRULE is not already provided. Needs to be one of these values: day, week, month, year.

 

AR - interval_name

Any value the merchant would like to represent what the subscription frequency will be. This is text, and can be named anything and will display to the customer what their frequency is. Notable examples would be "Monthly Club", or "Shave weekly", etc.

AS - week_type

We will populate this field.

 

AT - week_day

We will populate this field.

 

AU - month_type

We will populate this field.

 

AV - month_day

We will populate this field.

 

AW - month_occurrence

We will populate this field.

 

AX - month_occurrence_day

We will populate this field.

 

AY - year_type

We will populate this field.

 

AZ - year_month

We will populate this field.

 

BA - year_occurrence

We will populate this field.

 

BB - year_occurrence_day

We will populate this field.

 

BC - note

This value is optional.

 

BD - order_rrule

This field is only required if no values were given for the interval fields.

The value provided here must include a DTSTART separated with a line break from the rest of the RRule. A timezone (TZID) is required, otherwise the subscription will be processed in UTC time.

          DTSTART;TZID=Europe/London:20190506T000000
RRULE:FREQ=DAILY

 

Was this article helpful?
0 out of 0 found this helpful