Skip to Main Content
Get in touch

Migrating to Bango

  2. Migrating to Bango

Overview

Migrate your existing consumer subscriptions and product entitlements onto the Digital Vending Machine® (DVM™).

Once migrated, the DVM™ will help you manage the full lifecycle of your subscription offers, including entitlement management, renewals, billing, and charging. This enables you to standardise subscription management across all your 3rd-party distribution partnerships.

The migration process is simple to use. Migration files follow the same JSON structure as the DVM™ APIs, making it easy to prepare migration data using your existing DVM™ integration model. Import files are validated before processing to ensure the migration can complete successfully.

You can continue provisioning new consumers through the DVM™ while your existing consumers are being migrated. The migration process is fast and efficient, helping minimise disruption for existing customers.

During migration, the current lifecycle state of each subscription and entitlement is preserved. Key timeline information is captured, such as when the subscription was created, activated, suspended, or terminated. The migration imports the current state and key lifecycle dates, but does not include a complete historical record of every change made to the entitlement.

Migration Steps

  • Partnership Onboarding: Ensure you and your distribution partner are both onboarded to the DVM™. We will test your integration in the usual way through our sandbox environment.
  • Offer configuration: Create the Offer(s) that will represent the subscription Product(s) & associated entitlement(s) you’re migrating. This step generates an OfferId in the DVM™ Products & Offers catalogue which must be referenced in the Consumer Offer Migration File.
  • Prepare Migration Files: Prepare two migration input files using the JSON formats provided.
    • File 1: Entitlement Migration file which details each individual entitlement record being migrated.
    • File 2: Consumer Offer Migration file, containing pre-determined ConsumerOffer IDs for each consumer. This is the essential object used for end-to-end subscription offer management via the DVM™.
  • Upload Files: Upload your migration files to an S3 bucket. This can be your own bucket (with read access for Bango) or one we provide. Each file must have a unique name, including reloads.
  • File Import: We will import your files into the migration service and validate their contents. We will notify you if any issues are found.
  • Data Migration: If validation succeeds, the migration service will migrate the entitlement records and create the corresponding Consumer Offer objects.
  • Error Handling: The migration process supports configurable error limits to stop the migration if the error rate becomes too high (for example, a 10% error rate or 10 consecutive failures). This allows issues to be identified quickly.
  • Recovery Process: If any records fail during migration, partially migrated records may be recoverable depending on the stage at which the failure occurred.
  • Post-migration Validation: After migration completes, a validation script is executed to confirm the successful creation of all Consumer Offer records and the correct association of the related Entitlement IDs. A report is generated containing the objects and metadata required to manage your third-party services and subscriptions via the DVM™ APIs.