API to API migration guide
Learn how to migrate an existing WhatsApp Cloud API number from another API provider to DoubleTick while keeping the same phone number.
API to API migration is required when you want to move your existing WhatsApp Cloud API number from another API provider to DoubleTick. This process lets you retain the same phone number while changing your API provider.
What's covered
When is API to API migration required?
Use this process if:
Your number is already on WhatsApp Cloud API.
The number is not on the WhatsApp Business App.
The number is not using Coexistence.
You want to move your number from another BSP to DoubleTick.
Where do you start in DoubleTick
Case 1: Fresh DoubleTick account (first number) Log in using your phone number and OTP. The dashboard shows Get Started — clicking it begins onboarding immediately.
Case 2: Existing DoubleTick account (additional channel) Go to Settings, open Manage Channels, and click Add Number in the top-right corner. Once you reach Add Number, the process is the same for both cases.
Step-by-step migration process
Step 1: Start Embedded Signup In your DoubleTick dashboard, click Add number and select your preferred onboarding method.
Step 2: Select the correct onboarding method Choose Connect WhatsApp API number (Cloud API). This selection is mandatory for API-to-API migration.
Step 3: Facebook integration flow Click Continue as [Your Name] to open Meta integration, review the onboarding details, and click Continue.
Step 4: Select Business Portfolio Choose your Meta Business Portfolio and click Next.
Step 5: Select or create WhatsApp Business Account (WABA) Select an existing WhatsApp Business Account (WABA) or create a new one, then click Next.
Step 6: Create WhatsApp Business Profile Enter your WhatsApp Business Account Name (internal name), WhatsApp Display Name (customer-facing), and select your business Category. Click Next.
Step 7: Enter existing API number Enter the exact phone number currently active with your previous BSP. Select your verification method (text message or phone call) and click Next.
Step 8: Migration warning prompt Review the warning indicating that continuing will move the number to DoubleTick and stop messaging on your previous BSP. Click Next to proceed.
Step 9: OTP verification Type the 6-digit verification code sent to your phone number and click Next.
Step 10: Migration complete Verify that the connection status shows Connected. Your number is now active on DoubleTick, and previous BSP access is revoked automatically.
Key takeaways
API to API migration lets you move an existing Cloud API number from another provider to DoubleTick without changing the phone number.
You must disable Two-Step Verification in Meta Business Manager before starting, or migration may fail.
Keep your Display Name and Category identical to your previous setup to preserve templates, messaging limits, and Blue Tick verification.
Migration is irreversible — chat history does not migrate, and templates may need re-sync or re-approval.
Frequently asked questions
Do I need to disable Two-Step Verification before migrating? Yes. Disable it in Meta Business Manager before starting — migration may fail if it's still enabled.
Will I keep the same phone number after migration? Yes. API to API migration is designed to retain your existing phone number while switching your API provider to DoubleTick.
Why does the Display Name and Category need to match my previous setup? Keeping them identical helps message templates, daily messaging limits, and Blue Tick verification (if applicable) transfer correctly. You can change them after migration completes.
Does my chat history transfer during API to API migration? No. Chat history does not migrate during this process.
Is API to API migration reversible? No, migration is irreversible. Make sure you have customer consent and understand the impact before proceeding.
Related topics
Last updated