Skip to main content

10DLC campaign migration guide

This guide outlines the process for moving existing, active 10DLC campaigns to Bandwidth’s network.

Updated this week

Migration requirements

The migration is allowed only if you meet all of the following requirements:

  • Campaign is active in TCR

  • Campaign is fully approved with your current Connectivity Partner (CNP)

  • Campaign is an eligible 10DLC type (not Sole Proprietor)

  • Only one open migration per campaign

  • User or Manager role permissions in TCR

The migration is not allowed if any of the following applies:

  • Campaign is suspended by MNO or DCA

  • No DCA has accepted the campaign

  • Campaign is currently expired

  • Multiple open migrations for the same campaign

  • Guest or Read‑only TCR account

Migration process

  • If you're currently a Campaign Service Provider (CSP) who registers campaigns directly with TCR, you only need to complete the CNP migration. CNPs are providers that connect message traffic to mobile networks (for example, Bandwidth is a CNP).

  • If you're not currently a CSP and are registering with another provider instead of directly with TCR, you first need to complete the CSP migration and then the CNP migration.

CSP migration

CSP migration is a process created by TCR that allows you to become a CSP and migrate campaigns to your own TCR profile.

  1. Register as a CSP on TCR’s website.

    • There's a one-time CSP registration fee of $200.

    • CSP applications typically take 2-3 weeks and cannot be expedited.

    • For additional questions, please email [email protected].

  2. Request a CSP migration by sending an email to [email protected] with the following details:

    • The old CSP ID (from previous provider), the new CSP ID (recently obtained from TCR), and a primary contact for each.

    • A list of brand IDs and campaign IDs to migrate. Please note that all campaigns of the listed brands will be migrated to your CSP, and you can later decide which CNP a campaign is shared with using the CNP migration process.

  3. TCR’s Business Development Team will issue a Letter of Acceptance to both CSPs.  The migration will begin only after both parties sign and return the letter.

  4. TCR's Support Team will schedule the migration and notify both CSPs of the migration details. Please note that CSP migrations cost $0.50 per campaign, which you're responsible for paying directly to TCR.

Connectivity chain options

Maintain Connectivity Chain (recommended by Bandwidth)

Note: This is the only path for a no-cost CNP migration. If you clear your connectivity chain, your campaigns must go through vetting again.

  • No service interruption occurs.

  • The new CSP is inserted downstream from the old  CSP to retain existing connectivity.

  • The new CSP can perform a CNP migration later if desired (this is when Bandwidth will be added to the flow).

  • You only connect to your previous provider as your CSP until the CNP migration is complete, in order to allow you to maintain service.

Clear Connectivity Chain (not recommended by Bandwidth)

  • Messaging traffic is temporarily interrupted.

  • All upstream partners (CNPs and DCAs) are removed.

  • The new CSP becomes the owning CSP and must  establish new connectivity partners (CNPs).

  • NetNumber Services Registry (nnSR) and reseller  connections are reset.

CNP migration

CNP migration allows you to move your 10DLC messaging campaigns from your current provider to Bandwidth without having to re-vet them, as long as they've been approved with your current provider. This migration is available only to customers who register directly with TCR and import their campaigns into the Bandwidth App. Before initiating a CNP migration, please note the following:

  • If you're initiating a CNP migration or have received a migration denial from Bandwidth, contact the Bandwidth Support Team to ensure your account is configured for CNP migrations.

  • If you’re moving to Bandwidth from a different CNP, ensure there are no phone numbers associated with the campaign.

  • To avoid additional vetting charges, ensure that your campaign has been fully approved for all carriers. Campaigns without approvals for all selected Mobile Network Operators (MNOs) will incur a standard vetting fee.

  • To minimize downtime once your CNP migration is complete, we recommend having a plan on how you'll send traffic to your campaigns. You'll have the option to order new numbers, port your existing numbers, or use Hosted Messaging.

Once you're ready to initiate a CNP migration, you can do it in bulk or individually, either via UI or API:

  1. Navigate to the Working with Campaign Migration Requests in the CSP and DCA Portals section for UI instructions or Appendix D: New and Impacted CSP API Endpoints for API instructions.

  2. Once you've initiated your CNP migration, Bandwidth and its partners will approve it. Your campaign will then appear in the Bandwidth App account associated with its CSP ID. If you encounter any issues with your migration, please see the TCR CSP Portal for details.

Did this answer your question?