When changes to the plans add-ons are rollout out only to new subscriptions (for example: when changing their price), grandfathering takes place.

To prevent a SKU sprawl, Stigg allows you to manually migrate each subscription to the latest plan and add-on version.

We've now extended our APIs to allow you to programmatically schedule the migration to take place at the end of the customer's current billing period, in addition to being able to trigger the migration immediately.

The new functionality is supported by the Stigg Node.js SDK v1.17.0 and our GraphQL API.

Support in the Stigg Console UI is also planned.