Importing your existing data into Stigg is a key milestone in the integration process. This guide will walk you through the process step-by-step, ensuring a smooth transition and uninterrupted operations.
Data should be imported to Stigg according to the above order.
Create a file called customers.json
that contains all the customers that will be imported to the environment.
The file should be in the following schema:
Initiate the bulk import process:
Using the importCustomerBulk
endpoint.
Before importing subscriptions, ensure that the relevant customers have been imported to Stigg.
To migrate subscriptions to free plans, create a file called free-subscriptions.json
that contains all of the subscriptions that should be imported.
The file should be in the following schema:
Initiate the bulk import process:
Using the importSubscriptionBulk
endpoint.
To migrate subscriptions to paid plans, repeat the below process for each subscription:
billingInformation.isBackdated: true
property. Doing so will create the subscription as backdated in the billing provider and ensure that customers will be billed again for the subscription starting from the next billing period. You may optionally sync additional metadata for the subscription that’s synced to the billing provider to indicate that this is a migrated subscription by passing the billingInformation.metadata
property when provisioning the subscription Stigg.To migrate subscriptions to custom plans, create a file called custom-subscriptions.json
that contains all of the subscriptions that should be imported.
The file should be in the following schema:
Initiate the bulk import process:
Using the importSubscriptionBulk
endpoint.
Importing feature usage is supported only for metered features with a Calculated Usage meter type.
Before importing feature usage, ensure that the relevant customers have been imported to Stigg.
Create a file called usage.json
that contains all the features’ up-to-date usage.
The file should be in the following schema:
Initiate the bulk import process:
The import function is idempotent; therefore, attempting to import usage multiple time will yield the same result.
Leverage the reportUsageBulk
endpoint while passing the updateBehavior: UsageUpdateBehavior.SET
property in each of the usage reports.
Importing your existing data into Stigg is a key milestone in the integration process. This guide will walk you through the process step-by-step, ensuring a smooth transition and uninterrupted operations.
Data should be imported to Stigg according to the above order.
Create a file called customers.json
that contains all the customers that will be imported to the environment.
The file should be in the following schema:
Initiate the bulk import process:
Using the importCustomerBulk
endpoint.
Before importing subscriptions, ensure that the relevant customers have been imported to Stigg.
To migrate subscriptions to free plans, create a file called free-subscriptions.json
that contains all of the subscriptions that should be imported.
The file should be in the following schema:
Initiate the bulk import process:
Using the importSubscriptionBulk
endpoint.
To migrate subscriptions to paid plans, repeat the below process for each subscription:
billingInformation.isBackdated: true
property. Doing so will create the subscription as backdated in the billing provider and ensure that customers will be billed again for the subscription starting from the next billing period. You may optionally sync additional metadata for the subscription that’s synced to the billing provider to indicate that this is a migrated subscription by passing the billingInformation.metadata
property when provisioning the subscription Stigg.To migrate subscriptions to custom plans, create a file called custom-subscriptions.json
that contains all of the subscriptions that should be imported.
The file should be in the following schema:
Initiate the bulk import process:
Using the importSubscriptionBulk
endpoint.
Importing feature usage is supported only for metered features with a Calculated Usage meter type.
Before importing feature usage, ensure that the relevant customers have been imported to Stigg.
Create a file called usage.json
that contains all the features’ up-to-date usage.
The file should be in the following schema:
Initiate the bulk import process:
The import function is idempotent; therefore, attempting to import usage multiple time will yield the same result.
Leverage the reportUsageBulk
endpoint while passing the updateBehavior: UsageUpdateBehavior.SET
property in each of the usage reports.