Migration Prerequisites {#rb-subs-migration-0-prereqs}
======================================================

Before migrating subscriptions to `Cybersource` Recurring Billing, ensure these prerequisites are met.

Understanding of Recurring Billing Subscription Management
:
Understand Recurring Billing subscription management in the `Cybersource` system. Review these guides for details:

    * [Recurring Billing Developer Guide](https://developer.cybersource.com/docs/cybs/en-us/recurring-billing/developer/all/rest/recurring-billing-dev/recur-bill-dev-intro.md "")
    * [Recurring Billing User Guide](https://developer.cybersource.com/docs/cybs/en-us/recurring-billing/user/all/rest/recurring-billing-user/recur-bill-services-intro.md "")

:

`Cybersource` `Token Management Service` is Configured with a Token Vault
:
Recurring Billing requires that you have a `Cybersource` account with a properly configured `Token Management Service` (`TMS`) at the transacting MID level and with a configured token vault. For details, see the [Token Management Service Developer Guide](https://developer.cybersource.com/docs/cybs/en-us/tms/developer/ctv/rest/tms/tms-overview.md "").
:

Customer Tokens from Your Current Provider Are in the `Cybersource` `TMS`
:
`Cybersource` Recurring Billing uses only the **customer token** type. The customer tokens from your current subscriptions provider must be in `Cybersource` `TMS` before you begin to migrate subscription data from that provider to the `Cybersource` system.
:
> IMPORTANT
> Token migration from a system outside the ` Cybersource ` system is a separate process that requires coordination with your ` Cybersource ` Account Manager.

: