> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bango.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migration overview

> Overview of migrating existing subscriptions and entitlements to DVM.

## What is a migration?

If you are a Reseller with an existing consumer base that you want to manage through the DVM, migration is the process of bringing those consumers and their active subscriptions across without disrupting their service or requiring them to re-subscribe.

Once migrated, the DVM takes over the full subscription lifecycle for each consumer: entitlement management, renewals, billing, and charging. This lets you standardize subscription management across all your third-party distribution partnerships through one place.

<Info>
  You can continue provisioning new consumers through the DVM™ while your existing consumers are being migrated. The two processes run in parallel without conflict.
</Info>

***

## What gets migrated

The migration process imports the **current state** of each subscription and entitlement — preserving key lifecycle information such as when it was created, activated, suspended, or terminated.

<Note>
  Migration captures the current state and key lifecycle dates of each entitlement. It does not include a complete historical record of every change made to the subscription prior to migration.
</Note>

***

## Before you begin

Two things need to be in place before you start a migration:

<Steps>
  <Step title="Complete partnership onboarding">
    Both you and your distribution partner must be onboarded to the DVM. Bango will run integration testing through the sandbox environment in the usual way before any migration begins.
  </Step>

  <Step title="Configure your Offers">
    Create the Offer(s) in the DVM™ Offer Catalog that represent the subscription products and entitlements you are migrating. Each Offer generates an `offerId` which must be referenced in your Consumer Offer Migration File.

    If you haven't built an Offer yet, see [Build an Offer](/offer-management/create-offer).
  </Step>
</Steps>

***

## Summary

<CardGroup cols={2}>
  <Card title="Non-disruptive" icon="shield-check">
    Existing consumers keep their active subscriptions throughout. New provisioning continues in parallel during migration.
  </Card>

  <Card title="State-preserving" icon="clock-rotate-left">
    Current entitlement state and key lifecycle dates are carried over. Consumers continue exactly where they left off.
  </Card>

  <Card title="Familiar format" icon="code">
    Migration files use the same JSON structure as the DVM APIs. If you're already integrated, the data model requires no new learning.
  </Card>

  <Card title="Validated before processing" icon="circle-check">
    Files are validated before any data is written. Issues are caught early, before they affect your consumer base.
  </Card>
</CardGroup>