Prerequisites
Read the migration overview and ensure the pre-requisites are in place.How migration works
1
Prepare your migration files
Migration data is submitted as two JSON files, structured to match the DVM API format. If you already have a DVM™ integration, the data model will be familiar.File 1 — Entitlement Migration FileContains one record per entitlement being migrated. Each record describes the entitlement’s current state and key lifecycle dates.File 2 — Consumer Offer Migration FileContains pre-determined
Either
externalEntitlementId or entitlementId must be provided. At least one is mandatory. If you provide externalEntitlementId without an entitlementId, the migration service will auto-generate a UUID for it. We recommend providing entitlementId upfront as a UUID v4, so you have a known reference before migration runs. Note that dateCreated must be before dateActivated.consumerOfferId values for each consumer. The Consumer Offer is the core object used for end-to-end subscription management via the DVM APIs. Getting this right is essential.consumerOfferId must be a UUID v4 generated by you prior to migration. offerId must reference an Offer already configured in the DVM Offer Catalog. The file links each entitlement to its Consumer Offer via the entitlementIds array.2
Upload your files to cloud service storage
Upload both files to an cloud service storage (AWS s3), either your own (with read access granted to Bango) or one provided by Bango. Each file must have a unique name, including any reloads or resubmissions.
3
DVM imports and validates
DVM imports your files into the migration service and validates their contents before any data is written. If any issues are found, you will be notified so they can be resolved before migration proceeds.
4
Data migration runs
Once validation passes, the migration engine processes each record, migrating entitlements and creating the corresponding Consumer Offer objects in the DVM.The migration includes configurable error limits to catch problems early. For example, if the error rate exceeds a defined threshold (such as 10% of records, or 10 consecutive failures), the migration pauses automatically so issues can be investigated before continuing.
5
Post-migration validation
After migration completes, a validation script confirms the successful creation of all Consumer Offer records and verifies that the related Entitlement IDs are correctly associated.A report is generated containing the objects and metadata you need to manage your subscriptions via the DVM APIs going forward.