Skip to main content
You can import subscriptions and their completed orders from your previous system via API so that those records are accessible in the Admin UI and future orders can be fulfilled through Kibo. Subscriptions must be linked to a customer record, so you should import customers first if they are not already in your Kibo system. Likewise, price list codes and subscription product data are also required upon import and should be configured in your system before importing subscriptions. Only Cancelled, Paused, Errored, and Active subscriptions can be imported. Before importing, ensure that you are providing any required subscription attributes. If any required attributes are missing, then an error will be returned and the subscription will not be imported.

​
Customer API Field

You can use the migrationRequired flag on customer accounts in the Customers API to indicate whether or not their historical subscription data is going to be migrated into Kibo. This is false by default, but Kibo can assist you with updating the flag in bulk across your applicable customers via a script. Setting the flag to true means that the migration has not happened yet and the subscriptions tab will not be visible in account details in the Customers UI. This example is an excerpt from the Add Account request that includes the migration flag:
You can also filter the Customer API by this flag to find customers whose subscriptions need to be migrated:
Once you import your historical subscriptions (as shown in the next section), you should switch the flag back to false via the Update Account call or the B2B equivalent. The tab will then appear in the Customers UI and all of the customer’s subscription data will be displayed.

​
Import via Subscriptions API

To import subscriptions, make a call to the Create Subscriptions API detailing the items in that subscription, payment and fulfillment information, and price list code. Imported subscriptions should be flagged with isImport=true in the request body, and may also support an External Subscription ID that allows them to remain accessible via their ID created by a system other than Kibo. The subscription mode and frequency should be defined as attribute properties, using the same format as the example below:
This example shows a full sample request to import a subscription:
Upon importing, validation will be performed on that required customer, price list, and product data. The validation will also check the fulfillment method and item-level pricing fields to ensure that order totals match up, and that the subscription frequency is supported.

​
Import Completed Orders

After importing the subscription information, you can upload any historical orders and their fulfilled shipments through the Create Order API. Follow the instructions in that API guide, which will include enabling a site setting to creating shipment records for imported orders and supporting returns, refunds, and credits.