Skip to Content
Your subscription data now goes where you need it: the Curobi Developer API feeds your warehouse, ERP or CRM, and webhooks tell you the moment something changes — read the API docs →
TutorialsImport Subscriptions From Another App

Import subscriptions from another app

If you’re switching to Curobi from another subscription app, this tutorial walks through moving your existing subscribers over without asking them to re-subscribe.

Available on the Pro plan. See Pricing & Plans. Background reading: Import & Migration.

1. Export from your current app

Export your active subscriptions to CSV from wherever they currently live. At minimum you’ll want each row to include:

  • The customer (email or Shopify customer ID)
  • The product/variant
  • Billing frequency
  • Current price / discount
  • Next billing date
  • A stable external ID from the source system (used to prevent duplicate imports)

Exact column names vary by source app — the importer isn’t tied to one specific competitor’s export format.

2. Set up matching plans first

Before importing, make sure a Curobi subscription plan exists for each frequency/discount combination your import will need. The importer maps each row to an existing plan — it won’t create new plans for you.

3. Run a dry run

  1. Open the Import tab in the Curobi admin and choose to import / migrate subscriptions.

    Choosing to import and migrate subscriptions from another app

  2. Download the sample CSV to see the exact expected columns, then upload your prepared file.

    Download the sample CSV and upload your own file

  3. Curobi validates every row without creating anything yet — you’ll see which rows will succeed and which have problems (unmatched product, invalid frequency, missing customer, etc.).

    Uploading the CSV and reviewing the validation result

  4. Fix your CSV and re-upload if there are errors, or proceed if the dry run looks clean.

4. Commit the import

  1. Once the dry run is clean, click Import to commit.
  2. Curobi creates a real Shopify subscription contract for each row via Shopify’s own contract-creation API — these are genuine subscriptions, not a look-alike Curobi-only record.
  3. Re-running the same file is safe — imports are deduplicated on the combination of your store and each row’s external ID, so nothing gets created twice.

5. Verify

  1. Spot-check a handful of imported subscriptions in Subscriptions — confirm frequency, price, and next billing date match the source.
  2. Confirm the customer sees the subscription in their Manage subscriptions portal.
  3. Let the first post-import billing cycle run and confirm it charges correctly before fully decommissioning your old subscription app.

Protected Customer Data approval (a Shopify-side review) is required before this can run against real customer data on a live store — development stores work without it while you’re testing the process.

Last updated on