Migrating to Ordergroove

In this guide, we'll provide an overview of migrating your subscription program to Ordergroove, and what to keep in mind to keep your onboarding quick and painless.

Keep in mind this is meant as a general overview and not a comprehensive list of the technical steps involved. Your implementation manager will help you through the technical aspects unique to your program.



Every migration usually follows five main steps:

  1. Initial Scoping
  2. Store Prep
  3. Export and Cleanup Data
  4. Formatting and Dry Runs
  5. Testing and Wrapup

In the following sections, we'll go through each step and what you can do to keep the migration moving.

1. Initial Scoping

Before migrating over, let's make sure we're a good fit for your subscription program and have a clear plan of action. If you think we're a match, reach out and we'll discuss your subscription goals.

✅ We'll discuss

  • Are you bringing an existing subscription program, or starting from scratch?
  • What kind of subscription program do you run/are you looking to build? 
  • If you have an existing program, what platform is it on, and do you have access to payment information (tokens)?
  • How many subscriptions will you be migrating?
  • What is your ideal go live date to have your new program up and running?


2. Store Prep

With the path forward set, we need to get your store ready. There are a few steps to handle before you start moving data.

Action Steps

  • If you haven’t already, create a few subscriptions in your current subscription program that are associated to you or users at your company. You'll need them to run an end-to-end test for the Ordergroove migration.
  • Depending on the eCommerce platform you are on, or migrating to, there may be additional steps to set up payment information. Double-check with your integration specialist to see if any steps apply to your store. For example:
    • Shopify may require you to set up a secondary gateway
    • BigCommerce may require you to import the payment tokens into the customer’s wallet before migration
  • If you're migrating eCommerce platforms, you'll need to set up your store, customers, and products first.
  • You must migrate your customers and products into your store before you create the Ordergroove migration file in Step 3. 


3. Export Data

Most of the manual labor of a migration is pulling your data out of your existing subscription platform, and sometimes your payment processor as well. The data will need to match Ordergroove's formatting and headers before you can import it in, which we'll tackle in the next step.

The process will look a little different based on your current eCommerce platform, payment processor, and subscription platform. 

  • Migrating from Recharge? There are a few extra requirements, take a look at our Managed Recharge Migration Guide
  • Coming over from a different platform? You're set, continue to Step 4.


4. Formatting and Dry Runs

The next step is to format the raw data from your eCommerce platform, or payment processor, to match Ordergroove. We use a newline delimited JSON file, you can read more about it our View migration file structure information guide.

We highly recommend setting up a test sandbox installation and running several migration tests while you're still setting up your storefront. Ordergroove has a toggle for test migrations you can use. Test as often as you feel comfortable; it'll make the final import much smoother.


5. Import and Testing

The final step is to go through with a live import, double check that everything looks right, and put at least one test transaction in.

The Import Process Be sure to Test
  1. Deactivate your existing Subscription Provider
  2. Activate Ordergroove
  3. Split out your migration doc, single out one customer
  4. Run a test import
  5. Looks good? Import the full file(s)


Let's Chat

If you're thinking about moving over to Ordergroove, reach out and we'll be happy to help. Whether it's migration specifics, or if we're a good fit for your goals at all, we'll help in any way we can.