> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md). # Coexistence to coexistence migration guide Learn how to migrate a WhatsApp number that's in Co-existence mode with another provider to Co-existence mode on DoubleTick, including chat history transfer. This guide is for you if your WhatsApp Business phone number is already connected to another BSP (Business Solution Provider) or API provider, is currently working in Co-existence mode (both the WhatsApp Business App and the API are active together), and you want to migrate the same number to DoubleTick, again in Co-existence mode. #### What's covered * [Overview of the migration process](/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md#overview-of-the-complete-process) * [Releasing the number from your existing BSP](/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md#step-1-release-the-number-from-the-existing-bsp-mandatory-step) * [Starting Embedded Signup on DoubleTick](/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md#step-2-start-embedded-signup-on-doubletick) * [Facebook login and Business Portfolio selection](/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md#step-3-facebook-login-and-business-portfolio-selection) * [Chat backup and final connection](/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md#step-4-chat-backup-and-final-connection) * [Key takeaways](/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md#key-takeaways) * [Frequently asked questions](/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md#frequently-asked-questions) #### Overview of the complete process The migration is divided into four parts, each of which is mandatory: * Releasing the number from the existing BSP using the **Change Phone Number** feature in the WhatsApp Business App. * Starting Embedded Signup inside DoubleTick. * Completing Facebook login and business verification. * Transferring chat history and finalizing the connection. #### Step 1: Release the number from the existing BSP (mandatory step)
* Since your number is already connected to another BSP, WhatsApp must first "release" it using the **Change Phone Number** feature inside the WhatsApp Business App. * Open the **WhatsApp Business App** and go to **Settings → Account → Change Phone Number**. Enter your existing WhatsApp Business number as the old number and a fresh number that isn't active on WhatsApp as the new number. * Verify the fresh number using the OTP and complete the process, then repeat the same steps to change the number back to your original WhatsApp Business number. Once completed, your original number will be released and ready to onboard on DoubleTick. {% hint style="warning" %} If this step is skipped, the number cannot be connected to DoubleTick. {% endhint %} #### Step 2: Start Embedded Signup on DoubleTick * Log in to DoubleTick using your phone number and OTP — if this is your first time onboarding, click **Get Started** afterwards; if you're adding an additional number, you'll land directly on the Dashboard. * Then go to **Settings → Manage Channels → Add Number**, select **Add Number using Embedded Signup**, choose **Connect your existing WhatsApp Business number**, and click **Confirm and Proceed**. {% hint style="warning" %} Do not select Cloud API onboarding — this guide is specifically for Coexistence to Coexistence migration. {% endhint %} #### Step 3: Facebook login and Business Portfolio selection * Log in with Facebook — if you're already logged in, your account is auto-detected; otherwise, log in, click **Continue**, then click **Get Started**. Choose your verified Business Portfolio (business name, website, and country details auto-fill) and click **Next**. * You'll again see two options, **Cloud API** or **Connect existing WhatsApp Business App** — select **Connect existing WhatsApp Business App** and click **Next**. Enter your WhatsApp Business phone number and verify it using the 5-digit code sent to you, select your correct time zone, and click **Next**. Finally, review the permissions requested by DoubleTick and click **Continue**. #### Step 4: Chat backup and final connection * This is the final and most important part of the process. A QR code will appear on your screen — click **Scan QR Code**, then select **Share chats** from the pop-up options (not **Don't share chats** or **Cancel**); this allows the last 6 months of chat history to transfer to DoubleTick. * You'll receive a message in your WhatsApp Business App from Facebook Business — open it, click **Scan QR Code**, and scan the code on your screen. Chat backup begins automatically, and once it finishes you'll see a confirmation that the number is connected with DoubleTick — click **OK** to complete the migration. Your Co-existence to Coexistence migration is now complete. Your phone number stays the same, your WhatsApp Business App remains active, up to 6 months of chat history transfers, and the number continues working in Coexistence mode. #### Key takeaways * You must release the number from its existing BSP using **Change Phone Number** in the WhatsApp Business App before DoubleTick can connect it — this step cannot be skipped. * Always select **Connect existing WhatsApp Business App** during Embedded Signup, not Cloud API onboarding. * Selecting **Share chats** during the QR scan step transfers up to 6 months of chat history to DoubleTick. * After migration, your phone number, WhatsApp Business App, and Co-existence mode all continue working as before — only the API side is now connected to DoubleTick. #### Frequently asked questions **Why do I need to release my number from the existing BSP first?**\ WhatsApp requires the number to be released using the Change Phone Number feature before it can connect to a new BSP like DoubleTick. Skipping this step means the number cannot be onboarded. **Which onboarding option should I choose during Embedded Signup?**\ Select **Connect existing WhatsApp Business App**, not Cloud API onboarding — this guide is specifically for Coexistence to Coexistence migration. **Will my chat history transfer to DoubleTick?**\ Yes, if you select **Share chats** during the QR code scan step. This transfers up to 6 months of chat history. **Does my WhatsApp Business App still work after migrating?**\ Yes. Your number continues working in Co-existence mode — the WhatsApp Business App remains active alongside the API connection through DoubleTick. **What if the fresh number used in Part 1 is already registered on WhatsApp?**\ Make sure the fresh number you use to temporarily replace your original number isn't already registered on WhatsApp or the WhatsApp Business App, or the release step will fail. #### Related topics * [Getting Started with Co-Existence](/co-existence/getting-started-with-co-existence.md) * [Onboard an additional WABA on Coexistence](/get-started-with-doubletick/onboarding/onboard-an-additional-waba-on-coexistence.md) * [How to Manage Channels](/settings/how-to-manage-channels.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.doubletick.io/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.