Migrate campaigns 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

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

Prerequisites

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.

Migration steps

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

1. Import your numbers into the Infobip platform

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:

POST https://api-ny2.infobip.com/numbers/2/numbers/import

Example request:

curl --location 'https://api-ny2.infobip.com/numbers/2/numbers/import' \
--header 'Content-Type: application/json' \
--header 'Authorization: App {apiKey}' \
--data '{
    "numbers": [
        "19546899283"
    ],
    "country": "US",
    "type": "VIRTUAL_LONG_NUMBER",
    "capabilities": [
        "SMS",
        "MMS"
    ],
    "skipOsrUpdate": true
}'

Request parameters:

2. Elect campaign to Infobip through TCR

Initiate the migration in TCR by calling the following endpoint:

POST /campaign/{campaignID}/migrateCnp/{upstreamCnpID}

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:

POST https://{baseUrl}/number-registration/1/campaigns/migrate

Example request:

curl --location 'https://{baseUrl}/number-registration/1/campaigns/migrate' \
--header 'Content-Type: application/json' \
--header 'Authorization: App {apiKey}' \
--data '{
    "name": "migrateCampaignCOJD655",
    "externalCampaignId": "COJD655",
    "numberPoolID": "INFOBIP23",
    "numbers": ["19168361160"],
    "isClientManageNnid": true
}'

Request parameters:

Example response:

{
    "id": "44e8c5fc-1f17-4f4c-9519-6606c907075f",
    "referenceId": null,
    "applicationId": "default",
    "entityId": null,
    "name": "migrateCampaignCOJD655",
    "createdDate": "2026-03-04T09:08:43Z",
    "lastModifiedDate": "2026-03-04T09:08:43Z",
    "stage": "IN_MIGRATION",
    "priority": null,
    "campaignFeedback": null,
    "externalCampaignId": "COJD655",
    "numbers": null,
    "externalDocuments": [],
    "numberKeys": [],
    "numberPreviews": [],
    "type": "EXTERNAL_TEN_DIGIT_LONG_CODE"
}

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. Migration complete: 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

Sole proprietors

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 standard Migration steps outlined above.

Subscribe to webhook events

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

• Infobip web interface: See Subscriptions documentation
• Subscription API: See Subscriptions API documentation (opens in a new tab)

Best practices

• 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. Double-check your OSR records before initiating each migration batch.