Migrating from Twilio or Another WhatsApp Provider to lynxbe

Can I keep my existing WhatsApp number when switching providers?

Yes, in the vast majority of cases. Meta supports an official, well-defined "Number Migration" process between different WhatsApp Business API providers (BSPs), so your existing number — and the complete history customers already have and trust with it — stays entirely unchanged. The process requires approval and cooperation from both the outgoing provider and the new host receiving the number.

What happens to my approved message templates during migration?

Approved templates legally and technically belong to the WhatsApp Business Account (WABA) itself, not to the specific provider hosting it, so they generally move together with the number automatically and don't need to be resubmitted for additional approval. It's still explicitly worth confirming this with the new provider before starting the migration, to avoid last-minute surprises.

Will there be downtime during the switch?

A properly planned, well-designed, and correctly scheduled migration typically causes only a brief downtime of a few minutes up to a few hours, while the number officially changes ownership between providers within Meta's systems. It's very important to coordinate the migration window in advance with both sides, and avoid running it during peak customer contact hours to minimize the impact on service.

What should I check before starting a provider migration?

It's important to confirm full, verified access to the Meta Business Manager account that actually holds the number, export and back up conversation history if the outgoing provider doesn't commit to keeping it available after the switch, verify a complete and accurate list of all existing approved templates, and coordinate the precise, detailed schedule with the new provider (e.g. lynxbe) to minimize downtime and any inconvenience to customers.

How long does a full end-to-end migration process take?

From the final decision to the actual switch on the ground, including full coordination with the old provider, official ownership verification with Meta, and transferring all templates — the process typically takes roughly one to three weeks, heavily dependent on how quickly and cooperatively the outgoing provider responds. The downtime window itself is significantly shorter than the overall process and is usually barely noticeable.

What if I don't have API access with my current provider?

Businesses that started out with a provider offering only a closed, simple management interface without open API access can still migrate the number without a problem — the Number Migration process happens entirely at the Meta level and doesn't actually require any API access at the outgoing provider, only their basic cooperation to approve releasing official ownership of the number.

Can I migrate several numbers at once?

Yes, and it's actually strongly recommended for businesses with several active numbers under the same Meta Business Manager account — bundling the entire migration into one concentrated window significantly reduces how many separate times you need to coordinate downtime, and lets you test every flow (bots, templates, various integrations) all at once instead of running separate, repeated checks for each number individually.

Is there a direct cost to migrating providers?

The Number Migration process with Meta itself usually doesn't involve any additional direct payment beyond regular costs, but it's very much worth thoroughly checking your existing contract with the outgoing provider (remaining commitment period, a possible early-exit fee) and confirming exactly what's included in the new provider's pricing — for example, whether transferring templates and the full history is included in the package or considered a separate paid service.

Does the messaging tier move with the number, or do I start over at zero with the new provider?

The messaging tier belongs to the phone number itself at the Meta level, not to the specific provider hosting it — so in most cases the messaging tier is preserved exactly as it was before the migration, with no need to "rebuild" the quality history from scratch. This is actually a significant advantage of an official Number Migration compared to opening a brand-new number, which would require starting at the lowest messaging tier regardless of any prior history.

What happens to my existing bots and automations during the migration?

Bot flows, automations, and custom configurations generally belong to the outgoing provider and don't automatically transfer with the number — they need to be rebuilt with the new provider. That's exactly why it's worth documenting in advance precisely how your existing bots work (the flow diagram, message wording, integrations) before starting the migration, so the new provider's team (like lynxbe's) can reproduce the exact same customer experience instead of starting the design from a blank page.