Migrating an existing WhatsApp Coexistence number from WATI to Make

Beginner Questions
1

:bullseye: What is your goal?

Hey everyone,

I want to connect my existing WhatsApp Business App number to Make’s WhatsApp Business Cloud integration using Coexistence. The same number is currently connected to Cloud API through WATI using Coexistence. I want to replace WATI with Make while keeping the same number and WhatsApp Business App active.

:thinking: What is the problem?

During Make’s Coexistence setup, my existing number appears but is marked “Not eligible”, presumably because WATI is currently its Cloud API/Coexistence partner.

Before disconnecting WATI, I need to know the supported migration procedure. Does Make support migrating an already-active Coexistence number from another provider?

Most importantly, if I disconnect WATI, could the number become temporarily ineligible for Coexistence, require re-registration, or have a cooldown/waiting period before Make can connect it?

I cannot risk disconnecting WATI first and then discovering that the number cannot immediately be connected to Make.

:test_tube: What have you tried so far?

I tried connecting the number through Make’s WhatsApp Business Cloud integration using Coexistence. During Meta’s onboarding flow, my existing WhatsApp number appears, but it is marked “Not eligible.”

I confirmed in Meta Business Settings that the number is currently connected through WATI as a partner. I have not disconnected WATI or deleted/re-registered the number, because I want to confirm the safe migration procedure first.

2

Hey Dan, I’d be very careful about disconnecting WATI first. Since the number is already active on WhatsApp Business App + Cloud API through Coexistence, the “Not eligible” status in Make is likely related to the number already being associated with another WhatsApp Business Solution Provider (WATI).

I would not delete, unregister, or re-register the WhatsApp number just to try to make it eligible, because that could potentially change the current Coexistence state.

The safest approach would be:

  1. Confirm with Make Support whether they support migration of an existing Coexistence number from another provider such as WATI.

  2. Ask Make specifically whether WATI needs to be disconnected from the WhatsApp Business Account/number before Make’s onboarding can recognize it.

  3. Before removing WATI, get confirmation on whether the number remains eligible for Coexistence immediately after the provider is removed.

  4. Confirm whether any re-registration, verification, waiting period, or cooldown is involved.

  5. Ideally, have Make confirm that they can initiate/complete the Coexistence onboarding before you remove WATI.

The important distinction here is that you’re not trying to connect a completely new WhatsApp number to Make. You’re trying to move an already-active Coexistence setup from one provider to another while keeping the WhatsApp Business App active.

So I wouldn’t treat “disconnect WATI and try again” as a safe migration procedure unless Make or Meta explicitly confirms that this is supported.

If I were handling this, I’d ask Make Support one very specific question:

“My WhatsApp Business App number is currently active in Coexistence with WATI. Make’s Coexistence onboarding shows the number as ‘Not eligible’. Does Make support migrating an existing Coexistence number from WATI to Make without unregistering or re-registering the WhatsApp number, and what exact steps should I follow to avoid losing Coexistence eligibility?”

That should force them to give you the actual migration procedure rather than a generic WhatsApp Cloud API setup guide.

3

The “Not eligible” status makes sense if the number is still actively connected to WATI as the current Coexistence/Cloud API provider.

I would avoid disconnecting WATI until the migration path is confirmed, because removing the existing provider could potentially affect the number’s current Cloud API configuration. The safest approach would be to confirm with Make/Meta whether the existing Coexistence registration can be transferred directly or whether WATI must first release the number.

It would also be useful to know whether Make supports a provider-to-provider migration without requiring the WhatsApp Business App number to be re-registered.

4

Not eligible is Meta treating the number as still owned by WATI, not a Make setup miss. Two BSPs cannot hold Coexistence on the same number. Make Support can confirm they will accept it; they cannot release it. That ask goes to WATI: release or change BSP without unregistering the WABA or killing the WhatsApp Business App.

Have they already given you a written release path, or only a disconnect-the-integration button?

5

If the number is currently active through WATI’s WhatsApp Coexistence setup, I’d definitely avoid disconnecting WATI until the migration path is confirmed.

The “Not eligible” status could indicate that Meta still considers WATI the active provider for that number. The important question is whether Make can take over the existing Coexistence registration directly, or whether WATI must first release the number through Meta’s system.

I’d recommend confirming this with Make Support before making any changes, specifically asking whether disconnecting WATI will preserve the existing WhatsApp Business App registration and whether there is any re-registration or cooldown period. That way, you can avoid putting the existing number at risk during the migration.