> 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.md). # Migration Move your WhatsApp number to DoubleTick while retaining its business setup. Migration covers moving an existing WhatsApp number between API types or providers while keeping the same phone number — for example, switching your Cloud API number from another provider to DoubleTick, moving between Coexistence setups, or converting a number between Coexistence and Cloud API. Each guide walks you through the exact steps for that migration path, including any mandatory waiting periods, release steps, or warnings specific to that scenario, and notes whether your existing chat history carries over. #### In this section * [API to API migration guide](/get-started-with-doubletick/migration/api-to-api-migration-guide.md) * [Coexistence to coexistence migration guide](/get-started-with-doubletick/migration/coexistence-to-coexistence-migration-guide.md) * [Coexistence to Cloud API migration guide](/get-started-with-doubletick/migration/coexistence-to-cloud-api-migration-guide.md) * [Cloud API to CoEx migration guide](/get-started-with-doubletick/migration/cloud-api-to-coex-migration-guide.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.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.