Campaign Migration

Process at a Glance

Interaction Flow

Port-in Numbers

Port-in requests can be submitted before the campaign migration.

⏱ Timing: The process typically takes ~1-2 days, but may take longer. All messaging continues to flow through your previous CNP during porting.

Full request details: POST /v1/Phones/port-in

ℹ️ Note for 10DLC traffic:
Under normal conditions, calling POST /v1/Phones/port-in without specifying a MessagingConfig that is linked to an active TCR campaign will result in an error.

However, if Campaign Migration is enabled on the account, this validation is temporarily bypassed: numbers can be ported with a MessagingConfig that isn’t linked to a campaign yet. Once the campaign is migrated and the TcrCampaignImported webhook is received, link the MessagingConfig to the campaign to activate the numbers.

After you submit POST /v1/Phones/port-in, Telgorithm begins sending phoneNumberStatusChanged webhooks as the order progresses. The first status is PendingPortIn, which arrives immediately and confirms that Telgorithm has accepted the port-in order. No action is required at this point. When numbers are successfully ported in, the status becomes PendingTcrCampaignAdd. They remain in this status until you complete the campaign migration in TCR and attach the MessagingConfig to the imported campaign.

Initiate CNP Migration in TCR

Once the numbers have been ported in, the final step is to migrate the active campaign from the previous Connectivity Partner (CNP) to Telgorithm.

This action is performed in TCR. Once complete, the campaign becomes fully managed by Telgorithm, and you can attach a MessagingConfig to it.

⏱ Timing: The migration typically takes a few minutes to be fully accepted by all downstream carriers and Telgorithm.

There are two ways to trigger the migration:

Using the TCR CSP Portal

1. Log in to the TCR CSP Portal.
2. Open the campaign you wish to migrate.
3. Click Initiate Migration.
4. Select Telgorithm Inc as the new CNP.
5. Submit the request.

Using the TCR API

Copy
https://csp-api.campaignregistry.com/v2/campaign/{campaignId}/migrateCnp/SQTIJSW

1. Replace {campaignId} with the campaign you want to migrate.
2. Use SQTIJSW as Telgorithm’s upstream CNP ID.

When the migration is completed, the campaign will appear in your Telgorithm account and the TcrCampaignImported webhook will be triggered.

Activation After Campaign Migration

Once the campaign migration in TCR is approved and the campaign appears in your Telgorithm account, you will receive a TcrCampaignImported webhook. To complete activation, attach your existing MessagingConfig to the newly imported TCR campaign and ensure the phone numbers are linked to that MessagingConfig.

When both associations exist, each number’s status transitions to Active (this typically takes 5-10 minutes). Once a number is Active, outbound traffic can flow. If a number is linked to a MessagingConfig that is not connected to a campaign, it will remain in PendingTcrCampaignAdd status.

Cutover & Traffic Flow (step-by-step)

1. You submit the port-in request

   • Inbound: flows via the previous CNP.
   • Outbound: flows via the previous CNP.
   • Timing: port-in processing typically 1–2 days (you'll receive PhoneNumberStatusChanged webhooks).

2. Port completes

   • Inbound: flows via Telgorithm immediately after port completion.
   • Outbound: paused — messages cannot be sent while the number is not in Active status.
   • Timing: numbers remain in PendingTcrCampaignAdd until you complete the migration.

3. Migrate and Attach the Campaign

   • Inbound: flows via Telgorithm.
   • Outbound: flows via Telgorithm.
   • Timing: TCR migration is usually accepted within a few minutes; numbers typically become Active within 5–10 minutes after you link the campaign and phone numbers.

Overall cutover: If the campaign migration completes without delays on your side, expect a 7–10 minute outbound outage; inbound traffic is not interrupted.