10DLC Migration Options Overview

There are a few different ways you can migrate your existing 10DLC messaging campaigns to Sinch. How you migrate your 10DLC message program to Sinch depends on how your brands and campaigns are registered and whether you are a CSP (Campaign Service Provider) or not. 

• You are NOT a CSP. This means your previous provider registered your brands and campaigns in TCR (The Campaign Registry) on your behalf. Your previous provider was your CSP. 
• You are a CSP. This means you have registered your brands and campaigns directly in TCR. 

Your migration options also depend on whether you want to keep your existing number or get a new number. 

• Hosting: This means that you want to migrate only the messaging service for your number to Sinch and keep your voice service with your current carrier. 
• Porting: This means that you will migrate both voice and text service for your number to Sinch. Sinch will be the new carrier for your number. 
• Buy a new number: This means that you will buy a new number from Sinch to use for your existing 10DLC message program.

If you are NOT a CSP

You cannot migrate your existing registered brands and campaigns to Sinch from your other vendor, but you can still move your 10DLC messaging to Sinch. Because your previous vendor registered your brands and campaigns on your behalf, you will need to register new brands and campaigns with Sinch to migrate your 10DLC message program. You will incur fees for any new registrations. After you create new brands and campaigns with Sinch, you can port or host your existing number with Sinch, or get a new number from Sinch. 

To migrate your 10DLC messaging to Sinch, you will do the following:

1. Create your 10DLC brand If your brand was previously vetted, you can import your brand's vetting score for your new brand. 
    
2. Create your 10DLC campaign.
    
3. Port or host your existing number with Sinch or get a new number from Sinch (via Sinch Build Dashboard or Numbers API). 

Sinch will do the following:

1. Review brand and campaign information you provided and then register the brand and campaign in TCR on your behalf. If your brand was previously vetted, Sinch will import the vetting score for your new brand.  
    
2. Publish the 10DLC number in industry routing databases and provision in carrier platforms. 
    
3. Provision number for messaging in Sinch's platform. 

If you are a CSP

You can migrate your existing campaigns to Sinch. You will elect Sinch as your new CNP (Connectivity Partner) in TCR. Depending on how you get numbers for your 10DLC campaigns, you have two options to migrate your 10DLC messaging to Sinch. 

Option 1: You are the CSP and port or host your existing numbers with Sinch, or get new numbers from Sinch 

To migrate your 10DLC messaging to Sinch, you will do the following: 

1. Revoke your existing CNP election (reach out to TCR for more information on this process).  
2. Select Sinch as your new CNP. 
3. Port or host your existing number with Sinch or get a new number from Sinch (via Sinch Build Dashboard or Numbers API). 

Sinch will do the following: 

1. Review and accept the CNP election. 
2. Publish the 10DLC number in industry routing databases and provision in carrier platforms. 
3. Provision number for messaging in Sinch's platform. 
    

Option 2: You are the CSP and import existing numbers that you own to Sinch 

This is a special case that does not apply to most customers – you must have your own NNID (the NNID must be different than the NNID you have provisioned with your current provider) and complete the NNID provisioning process with Sinch. See the Importing Numbers article for more info.  

To migrate your 10DLC messaging to Sinch, you will do the following: 

1. Revoke your existing CNP election (reach out to TCR for more information on this process). 
2. Select Sinch as your new CNP. 
3. Update the OSR number record with the NNID that is provisioned with Sinch. 
4. Import your number to Sinch (via Sinch Build Dashboard or Numbers API). 

Sinch will do the following: 

1. Review and accept the CNP election. 
2. Provision number in carrier platforms. 
3. Provision number for messaging in Sinch's platform. 

Note: As a CSP, you can only elect Sinch as your new CNP if you are the last “hop” before your current DCA (Direct Connect Aggregator). If you are a CSP that elects an upstream CNP that is not a DCA, then you cannot elect Sinch as your new CNP. TCR is working on supporting this capability via a new migration tool that will be available by the end of Q1 2024. For more information, refer to TCR’s Campaign CNP Migration Tool documentation. 

• Example 1: CSPA --> CSPB --> DCA1. CSPB can elect a new CNP, but CSPA cannot.  
• Example 2: CSPX --> DCA1. CSPX can elect a new CNP. 

Visit the Sinch 10DLC Product Page to learn more about Sinch 10DLC or if you need more help with 10DLC or have any questions, contact Sinch, who will be happy help!