Skip to main content
All CollectionsGetting StartedMigrating to Subify
Migration Data Preparation - Migration Template
Migration Data Preparation - Migration Template

How to Export and Prepare Your Data for Subify

Updated over a month ago

We’re excited to help you transition to Subify! This guide will explain how to fill out the Subify Migration Template to ensure a smooth transition to Subify. When migrating from another platform (e.g., Bold, Appstle, Stay AI), you’ll need to ensure that certain fields in the Subify Migration Template are filled out correctly.

In the Template, the mandatory fields are highlighted in RED to help you easily identify which fields must be completed for each subscription. Optional fields can be left blank, but the columns must still be included in your file to avoid migration errors.


1. Key Fields for Migration

Contract ID and Payment Method ID are key fields for the migration process:

  • Contract ID
    Every subscription contract must have a unique identifier. This could be the Contract ID from your previous app or any other unique number you assign to each contract.

  • Payment Method ID
    The Payment Method ID is critical for migrating subscriptions successfully. Accepted formats are:

    • Shopify Payment Method ID: ebb59d677e10a57b1e11ccc6a9ce505e

    • Stripe ID (begins with cus-): cus_XYZ789012

    • PayPal Billing Agreement ID (begins with B-): B-1A2B3C4D

    If your previous app doesn’t provide these IDs, you can export them directly from your Stripe or PayPal account. Just be sure to match these IDs to your customers using their email addresses when entering the data in the Subify Migration Template.


2. Data Formatting and Template Guidelines

We know formatting can be a bit tricky, but following these guidelines will help ensure that your data is ready for a smooth migration.

Data Formats

  • Numeric Values
    All numbers should be formatted as proper numeric values.

  • Date Format: Dates must be formatted like this: YYYY-MM-DD 00:00:00 (e.g., 2024-10-30 00:00:00).

  • Phone Numbers: Enter phone numbers in this format: +[country code][number] (e.g., +1234567890).

  • Country and Province Codes
    Make sure to use Country Codes and Province Codes instead of full names. For example:

    • US for the United States

    • CA for California

    If you don’t have these codes, you can also refer to these resources:

  • Zip Codes

    Make sure US zip codes are formatted as plain text so leading zeros aren’t removed. For example, 07045 should stay as is, without removing the zero. If necessary, manually check for 4-digit zip codes and add the leading zero back.

  • Shipping Phone Numbers
    Every contract must have a valid shipping phone number. If you don’t have this information for some customers, a common solution is to use your store’s phone number. Ensure the numbers are formatted correctly, like this: +[country code][number] (e.g., +1234567890).

Column Naming

Make sure the column names in your file exactly match those in the template. Any differences, even small ones, can cause errors. Two key columns with asterisks are:

  • customer_id*

  • payment_method_id*

Before you upload the file, remove the asterisks from the column headers to avoid migration errors.

All columns in the Subify Migration Template must be included in your file, even if they don’t contain any data. For example, fields like billing_min_cycles may be empty, but they should still appear in your file.


3. Attention to Detail: Data Sensitivity

The information you enter in the template needs to be precise. The system is sensitive to small variations, especially when it comes to fields like Billing Interval, Status, and other key data points. Here are a few examples:

  • Billing Interval
    The accepted values for the Billing Interval column are:

    • WEEK

    • DAY

    • MONTH

    • YEAR

    Any variation (e.g., “weeks” or “days”) will cause an error, so be sure to enter the exact terms listed above.

  • Status
    For the Status column, use one of the following values:

    • Active

    • Pause

    • Cancelled

    • Expired

    Avoid small spelling differences (e.g., "Canceled" instead of "Cancelled"), as this could cause errors during the migration.


4. Product Variant IDs and Multiple Products in Contracts

Each product in Shopify has a Product Variant ID, even if the product doesn’t have any variants. It’s important that each row in the Subify Migration Template represents one Product Variant ID. If a subscription contract contains multiple products, each one should be listed in a separate row.

In addition to splitting product variants, ensure the following columns are filled out correctly for each product:

  • Line Quantity: Enter the number of units for each product.

  • Line Base Price: The pre-discount price of the product.

  • Line Discount Percent: The percentage discount applied (e.g., enter 10 for a 10% discount).

When migrating from Bold, the export often lists all Product Variant IDs for a contract in a single row. For the migration, you’ll need to split these out so each Product Variant ID is placed in its own row in the template.

And that’s it! With the Subify Migration Template filled out and your data properly formatted, you’re well on your way to a smooth migration. Remember, we’re here to support you at every step, so if you have any questions or run into any challenges, don’t hesitate to reach out.

Did this answer your question?