Migrating 10DLC numbers to Infobip

Complete guidance for migrating 10DLC numbers, brands, and campaigns from your current provider to Infobip. The right migration path depends on your role and whether you manage your own Net Number ID (NNID).

Choose your migration type

Standard number migration

Before you start [#before-you-start-standard-number-migration]

• Active 10DLC numbers: You must have 10DLC numbers currently active with another provider
• Current provider details: Know who your current provider and CSP (Campaign Service Provider) are
• TCR registration info: Understand your current registration structure (Direct CSP, DCA, etc.)
• Campaigns and brands: Document all brands and campaigns you want to migrate

Migration feasibility [#migration-feasibility-standard-number-migration]

10DLC number migration can appear complex as there are multiple migration paths depending on your unique circumstances. The specific path you follow depends on:

• Whether you are a Direct CSP (Campaign Service Provider) with your own NNID
• Whether you need to retain your existing number or can accept a new number
• Whether you are using Infobip's ID or your own ID
• Your current registration structure with The Campaign Registry (TCR)

Contact your account representative or solutions engineer early. They will assess your specific situation and provide you with the appropriate migration process suited to your needs.

Information Infobip needs to assess feasibility:

1. Current provider details:

   • Who is your current 10DLC number provider?
   • Who is your current connectivity provider?

2. Registration structure:

   • Did you register brands and campaigns directly with The Campaign Registry (TCR) as a Campaign Service Provider (CSP)?
   • Did you select a Direct Connect Aggregator (DCA) for connectivity?
   • Or does your current provider handle both registration and connectivity?

3. Migration volume:

   • Number of brands to migrate
   • Number of campaigns to migrate
   • Number of 10DLC numbers
   • Numbers per campaign distribution

Migration process [#migration-process-standard-number-migration]

If migration is confirmed as feasible, Infobip Support will perform the migration on your behalf.

Requesting number import [#requesting-number-import-standard-number-migration]

To initiate 10DLC number import through the Infobip web interface:

1. Log in to your Infobip account
2. Go to Channels and Numbers > Numbers
3. Select Import number
4. On the number details form, provide the following information:
   • Available countries: Select United States (+1)
   • Number type: Select Long Code (10DLC is classified as long code)
   • Numbers are in use and require a migration: Check this box if your 10DLC number is currently in use with another provider
     • If checked, you will see an additional field: Preferred date of migration - specify when you would like the migration to occur
5. Enter your 10DLC number(s) in the format +1-NPA-NXX-XXXX (for example, +1-212-555-0123)
   • You can enter a single number or multiple numbers separated by commas
6. Provide details about your current setup and provider in the form
7. Submit your import request

After submission:

Infobip Support will contact you with:

• Confirmation of feasibility
• Migration timeline and approach
• Additional information needed (if any)
• Next steps and timeline

Campaign migration using Infobip NNID

These migration steps are for Campaign Service Provider (CSP) and Connectivity Network Provider (CNP) customers who want to migrate their 10DLC campaigns to Infobip using the Infobip Net Number ID (NNID). Infobip manages the NNID and Operator Service Record (OSR) updates during this process.

Eligibility [#eligibility-campaign-migration-using-infobip-nnid]

Before you begin, ensure you meet the following eligibility criteria:

Prerequisites [#prerequisites-campaign-migration-using-infobip-nnid]

Complete the following prerequisites before starting the migration process. Only begin the migration after Infobip completes and confirms all items.

• Number import enablement. Your account must be enabled for self-service number import before you can use the Numbers API. Request this enablement through your account manager.

• Number pools (if applicable). If your campaign uses number pooling, contact your account manager, as this requires an additional revision for your campaign. Number pools are managed by Infobip.

• Migration API enablement. Your account must be enabled for API access to the migration service. Request this enablement through your account manager. Once enabled, you can trigger migration requests as described in the migration steps below.

Migration steps [#migration-steps-campaign-migration-using-infobip-nnid]

The migration follows a six-step process. Your campaign moves through the following statuses:

1. Import your numbers into Infobip

Import all numbers associated with the campaign into the Infobip platform. This ensures the numbers are available for selection during the migration request.

Use the following Numbers API endpoint to import your numbers:

Example request:

Request parameters:

2. Elect campaign to Infobip through TCR

Initiate the migration in TCR by calling the following endpoint:

3. Call the Infobip migration API

After electing the campaign to Infobip in TCR, trigger the Infobip migration endpoint:

Example request:

Request parameters:

Example response:

Response fields:

4. Continue sending through current provider

After submitting the migration request, your campaign transitions to the In Migration status (confirmed by "stage": "IN_MIGRATION" in the API response). During this phase, continue sending traffic through your current upstream provider. You do not need to take any action while Infobip processes the migration.

5. Infobip updates the OSR record

Infobip attempts to override the NNID on the OSR records for your numbers automatically. If your numbers belong to a provider that does not allow automatic OSR overrides, the Infobip Registrations team requests formal approval of the OSR update using the LOA you provided.

For more details about this step, discuss with your account manager and use the shared list of the numbers you plan to migrate. You can also reach the Registrations team directly.

If your campaign is stuck in the In Migration status for an extended period, contact the Registrations team to process the OSR update for your numbers.

6. Switch traffic to Infobip

Infobip automatically accepts your campaign from TCR, provisions it with the carriers, and notifies you through a webhook event. The webhook payload includes:

• campaignStatus=REGISTERED
• The associated Infobip UUID

Once all numbers from the campaign are assigned to the Infobip NNID, the campaign moves to REGISTERED status.

Subscribe to webhook events [#subscribe-to-webhook-events-campaign-migration-using-infobip-nnid]

To receive campaign status change notifications, subscribe through one of the following:

• Infobip web interface: See Subscriptions documentation
• Subscription API: See Subscriptions API documentation

Best practices [#best-practices-campaign-migration-using-infobip-nnid]

• Start small. Begin with a few low-volume campaigns to learn the process and enable Infobip to quickly resolve any issues.

• Share in advance. Provide Infobip with a list of campaigns and associated numbers you plan to migrate ahead of time.

• Coordinate OSR updates. Since Infobip manages the NNID and OSR updates, ensure your LOA is current (not older than 30 days) and that you have communicated the full list of numbers to your account manager.

Campaign migration using your own NNID

These migration steps are for Campaign Service Provider (CSP) and Connectivity Network Provider (CNP) customers who want to migrate their 10DLC campaigns to Infobip while continuing to host their own numbers under their own Net Number ID (NNID).

Eligibility [#eligibility-campaign-migration-using-your-own-nnid]

Before you begin, ensure you meet the following eligibility criteria:

Prerequisites [#prerequisites-campaign-migration-using-your-own-nnid]

Complete and confirm the following before starting the migration:

• NNID setup and carrier configuration
• Number import enablement
• Number pools (if applicable)
• Migration API enablement

NNID setup

Provide Infobip with the NNID you want to use, along with the following:

• A signed Letter of Authorization (LOA)
• A completed T-Mobile NNID request form

Infobip forwards the request to the carriers for NNID configuration. Lead time is approximately 1 month.

Get enabled for number import

Since you manage your own NNID, you can import numbers yourself using the Infobip API. Your account manager must first enable self-service number import on your account.

Number pools (if applicable)

If your campaign does not use number pooling, skip this section.

All number pools must be pre-configured and imported into the Infobip platform before migration. Number pools are not migratable, so you must create new pools before migrating.

Submit number pool requests through Infobip. To request a number pool, fill out the Number Pool Request Form (provided by your account manager) and submit it to the Infobip team for processing.

Migration API enablement

To call the Infobip campaign migration API endpoint, your account must be enabled for API access to the migration service. Request this enablement through your account manager. Once enabled, you can trigger migration requests as described in the migration steps below.

Sole proprietors [#sole-proprietors-campaign-migration-using-your-own-nnid]

Sole proprietor campaigns require additional setup before following the standard migration process.

TCR requirements

Before migrating any sole proprietor campaigns, Infobip must verify that the CSP meets the following TCR requirements:

• One number per sole proprietor campaign
• Maximum of 1,000 messages per day

Registration

Infobip registers the CSP with T-Mobile and creates a default campaign. This default campaign is the parent for all migrated sole proprietor campaigns from the CSP.

1. The CSP shares one sole proprietor campaign to Infobip through TCR.
2. Infobip creates the default campaign and assigns a number pool.
3. All subsequent sole proprietor campaigns link to this default campaign.

Once the default campaign setup is complete and confirmed, follow the migration steps below.

Migration steps [#migration-steps-campaign-migration-using-your-own-nnid]

The migration follows a six-step process. Your campaign moves through the following statuses:

1. Import your numbers into Infobip

Import all numbers associated with the campaign into the Infobip platform. This ensures the numbers are available for selection during the migration request.

Use the following Numbers API endpoint to import your numbers:

Example request:

Request parameters:

2. Elect campaign to Infobip through TCR

Initiate the migration in TCR by calling the following endpoint:

3. Update your OSR record

Verify and update the OSR record for your numbers with the correct:

• NNID
• Campaign ID
• SubID (if applicable)
• Context

4. Call the Infobip migration API

After electing the campaign to Infobip in TCR and updating your OSR record, trigger the Infobip migration endpoint:

Example request:

Request parameters:

Example response:

Response fields:

5. In migration

After submitting the migration request, your campaign transitions to the In Migration status (confirmed by "stage": "IN_MIGRATION" in the API response). Your numbers are offline during this phase. No action is needed from you while Infobip processes the migration. This typically takes a few minutes.

6. Switch traffic to Infobip

Infobip automatically accepts your campaign from TCR, provisions it with the carriers, and notifies you through a webhook event. The webhook payload includes:

• campaignStatus=REGISTERED
• The associated Infobip UUID

Subscribe to webhook events [#subscribe-to-webhook-events-campaign-migration-using-your-own-nnid]

To receive campaign status change notifications, subscribe through one of the following:

• Infobip web interface: See Subscriptions documentation
• Subscription API: See Subscriptions API documentation

Best practices [#best-practices-campaign-migration-using-your-own-nnid]

• Start small. Begin with a few low-volume campaigns to learn the process and enable Infobip to quickly resolve any issues.

• Share in advance. Provide Infobip with a list of campaigns and associated numbers you plan to migrate ahead of time.

• Verify OSR. Review your OSR records before initiating each migration batch.

Learn more

• Understanding 10DLC. 10DLC concepts and use cases
  
• Understanding brands. Brand creation and management
  
• Understanding campaigns. Campaign creation and management