HomeDocumentationPricing
    Support
    WazzaBeeWazzaBee
    Sign up

    Moving to WazzaBee from another service

    6 min read
    ·
    3 views
    ·
    Updated 10/13/2026

    🚚 Moving to WazzaBee from another service

    If your company's WhatsApp currently runs through another service, you can switch to us without changing your number or losing your conversations. This article covers every migration path step by step, plus a checklist of what to prepare in advance.

    Step 0. Identify your case

    The migration order depends on two questions: how the number is connected now and where your agents handle conversations.

    Your situationWhat we doWhat happens to the conversations
    The number is connected via WhatsApp Business API at another serviceWe migrate the number to us using the Meta procedureThey stay in your CRM. We can import them from Bitrix24 into your WazzaBee dashboard
    The number runs in the WhatsApp app on a phone and was connected with a QR codeWe connect the number officially via Coexistence, and the app stays on the phoneMeta transfers up to 6 months of one-to-one chats from the phone during connection
    Your agents work in Bitrix24We install the WazzaBee connector on the same Open ChannelThey stay in Bitrix24. Using an inbound webhook, we also import them into your WazzaBee dashboard
    Your agents work in amoCRMWe connect the WazzaBee connector to the same amoCRM accountThey stay in the deal and contact cards in amoCRM

    Most often the cases overlap: for example, the number is on WhatsApp API and the agents work in Bitrix24. In that case, you follow both paths.

    ✅ Checklist: what to prepare

    • A WazzaBee dashboard: sign up at wazzabee.com.
    • Admin access to your company's Meta Business Manager (business.facebook.com).
    • The phone with the number at hand: the verification code will be sent to it.
    • For a number on WhatsApp API: two-step verification PIN removed from the number.
    • For a number in the app: WhatsApp Business version 2.24.17 or later. Coexistence mode does not work in regular WhatsApp, so the number is first moved to WhatsApp Business.
    • For Bitrix24: portal admin access to install the app and, if needed, create an inbound webhook.
    • For amoCRM: account admin access to install the integration.

    Open a ticket from your dashboard and tell us which service and which CRM you use now. We will confirm the order of steps for your case.

    🔄 Path 1. The number is already on WhatsApp Business API

    Migrating a number between providers is a standard Meta procedure. After the migration, you keep:

    • your company name in WhatsApp;
    • quality rating and messaging limits;
    • the blue checkmark, if you have one;
    • approved message templates.

    How we migrate:

    1. Remove the two-step verification PIN from the number. It is usually set by your previous service: ask them to remove the PIN, or turn it off yourself in WhatsApp Manager in your Meta Business Manager if you have access.
    2. In your WazzaBee dashboard, open Channels and start connecting WhatsApp WABA.
    3. Tick "The number already works via WhatsApp API at another service" and go through the checklist.
    4. In the Meta window, choose "Create a WhatsApp Business account" and enter the number manually. Your old account does not appear in the window, and that is expected. The yellow warning about number migration is normal too.
    5. Confirm the number with the code and wait until the channel becomes active in Channels.

    If the Meta window shows a "Couldn't verify" or "network error" message, the cause is almost always a two-step verification PIN that has not been removed.

    Important: Meta does not migrate conversations that were stored only in your previous provider's interface. If your agents worked in Bitrix24 or amoCRM, the conversations are already in your CRM.

    Connection details: Connecting WhatsApp WABA.

    📱 Path 2. The number runs in the WhatsApp app

    If the number was connected to your previous service with a QR code, it keeps living in the app on the phone. We connect such a number officially via Coexistence:

    • the WhatsApp Business app stays on the phone and keeps working;
    • the number works in your WazzaBee dashboard and your CRM at the same time;
    • during connection you can transfer up to 6 months of one-to-one chats from the phone, while group chats are not transferred;
    • files from the history come through only for the last 2 weeks, and older ones remain as file placeholders.

    The decision to transfer history is made once, during connection. You cannot change it later without fully reconnecting the number.

    Coexistence connection in the dashboard is enabled by a WazzaBee manager: open a ticket saying you are moving with a number from the app, and we will turn on this option for your channel.

    Before connecting, disconnect the number from your previous service so that messages do not get split between two systems.

    Step by step: Connecting WhatsApp Coexistence.

    🗂️ Path 3. Your agents worked in Bitrix24

    Conversations in Open Channels belong to your Bitrix24 portal, not to the connector. So after you switch services, old chats stay in Bitrix24 exactly where they were.

    1. Install the WazzaBee app in Bitrix24: Connecting Bitrix24.
    2. In the Contact Center, select for WhatsApp the same Open Channel your agents used before. The queue, distribution and deal creation rules stay the same.
    3. Turn off the previous connector on this channel so that messages are not duplicated.

    Moving old chats into your WazzaBee dashboard

    If you want to see past conversations not only in Bitrix24 but also in the chats of your WazzaBee dashboard, we import them there ourselves. For this we need an inbound webhook for your portal.

    How to create an inbound webhook:

    1. Log in to Bitrix24 as a portal administrator.
    2. Open Applications → Developer resources.
    3. Go to the Other → Inbound webhook tab.
    4. In the access permissions, tick CRM (crm), Chat and notifications (im) and Open Channels (imopenlines).
    5. Click Create and copy the webhook address, which looks like https://ваш-портал.bitrix24.kz/rest/1/xxxxxxxx/.
    6. Send the address to us in a ticket from your dashboard. Do not forward it to open chats or third parties: it gives access to your portal data.

    If there is no "Inbound webhook" option, webhook creation is disabled in the settings. An administrator enables it in Settings → Bitrix24 settings → Security, in the field that controls who is allowed to create inbound webhooks.

    What happens during the import:

    • we only read the portal's conversations and change nothing in Bitrix24;
    • each chat goes to the right customer by phone number, with the original dates and message direction;
    • if you already have a new conversation with the customer in the dashboard, the old messages are placed before it in a single thread;
    • nothing is sent to customers, agents get no notifications, and auto-replies and the AI assistant do not react to historical messages;
    • first we import 2–3 chats for review, and the rest after your confirmation.

    The import time depends on the volume of conversations, and we tell you after an estimate. When the migration is finished, you can delete the webhook in the same Applications → Developer resources section.

    📊 Path 4. Your agents worked in amoCRM

    Conversations that went through your previous service are stored in the deal and contact cards in amoCRM and stay there after you switch services.

    1. Install the WazzaBee integration in amoCRM.
    2. Connect a WhatsApp channel to it. New messages will go to the same cards, and pipelines and Salesbots will keep working.
    3. Turn off the previous integration so that messages are not duplicated.

    💬 Other channels

    Telegram, Instagram Direct and OLX are connected with us from scratch, into the same shared chat as WhatsApp. Keep in mind that Instagram does not provide old messages on connection: the dashboard receives messages starting from the moment the channel is connected.

    ❓ FAQ

    Will customers notice the move?
    No. The number and company name stay the same, and customers write to the same place as before.

    Do we need to stop working during the move?
    Connecting official WhatsApp takes 15 minutes. It is best to pause sending for that time, and we will tell you when you can continue.

    What if the previous service does not respond?
    To migrate a number on WhatsApp API, you need your own access to Meta Business Manager and the two-step verification PIN removed. If the PIN cannot be removed through the previous service, open a ticket and we will look into your case.

    Can conversations from amoCRM be moved to the WazzaBee dashboard?
    For now, conversations from amoCRM stay in amoCRM itself. Open a ticket if you need them moved to the dashboard, and we will assess your situation.