DVM Billing & Charging is optional. Migration creates the subscription lifecycle structures required by DVM, but consumer charging can remain in your existing systems if that is the agreed operating model.
What gets migrated
Migration preserves the current state of each supported entitlement together with the lifecycle timestamps available for the migration, such as when the entitlement was created, activated, suspended, or terminated. Migration does not recreate the complete historical record of changes that happened before cutover. Keep historical records in your own systems where they are required for reporting, audit, or compliance.Before you begin
Complete these foundations before production migration:1
Onboard and test your DVM integration
Complete DVM onboarding, set up your integration in DVM Sandbox, and complete the relevant testing.
2
Configure the Offers being migrated
Create the Offers in the DVM Offer Catalog that represent the subscriptions being migrated. Each migrated Consumer Offer references a configured
offerId.See Offer model and Configure offer plans.3
Prepare the migration data
Prepare the existing consumer, entitlement, product, status, and lifecycle data needed for migration. Content Provider-specific validation or mapping may also be required.
Choose what you need next
Plan and run a migration
Follow the complete migration journey from preparation through cutover and monitoring.
Prepare migration files
See the migration file structures, example records, validation, and recovery behavior.
Migrate Netflix
Follow the complete Netflix migration journey, including PAI continuity, product mapping, and recovery.
Test before production
Validate your DVM integration and subscription flows in Sandbox.