Plan a WhatsApp migration from Twilio to Bird
Move the customer workflow along with the sender. A successful number connection does not prove that templates, automations, events and service operations have migrated.
Prerequisites
Have access to the owning Meta business assets, the current provider setup and the applications receiving messages. Assign a cutover owner and a team that can respond to customers during the transition.
1. Inventory the existing integration
Inventory Content SIDs, Messaging Services, status callbacks, Studio or Flex flows and voice applications. Map each resource to its purpose before replacing an integration.
Record approved languages and template content, sender ownership, webhook destinations, permission and suppression data, and the customer identifiers used by downstream systems. Keep a read-only record of the configuration needed to investigate the move.
2. Choose the sender transition
Review the supported migration or eligible coexistence path for this number and account. Confirm which assets transfer and which need recreation. Coordinate any provider release; do not delete an existing app registration or disconnect the current sender before the path is agreed.
3. Map the customer workflow
Connect the Bird message API, templates and incoming events to the intended business actions. Preserve reply identifiers and application task state. Outgoing metadata does not automatically appear on inbound replies.
| Existing responsibility | What to verify in the Bird evaluation |
|---|---|
| Content and languages | Record each Content SID, approved language and variable. Recreate the intended message in Bird and test the language that actually resolves. |
| Sender selection | Document how your application chooses a sender or Messaging Service. Confirm the connected Bird sender and its WhatsApp Business Account before testing. |
| Callbacks and replies | Translate the event meaning and customer correlation in your handler. A callback URL or provider message ID is not a portable conversation record. |
| Studio, Flex and calls | List the steps and team assignments outside the send API. Evaluate message automation, contact-center work and calling as distinct parts of the migration. |
4. Rehearse the complete exchange
Use an eligible controlled recipient and test an approved template, free-form response, interactive reply and human escalation. Confirm delivery observations separately from the actual business outcome. Rehearse an uncertain send, a closed service window and an unavailable integration.
5. Coordinate cutover and recovery
Agree how queued sends and active conversations are handled. Move traffic through the supported process, observe the sender and callback routes, and keep the team responsible for customer replies available. Define recovery using the actual provider transition constraints rather than assuming an instant reversal is always possible.
6. Reconcile the result
Review message cohorts and application records on both sides of the transition. Reconcile applicable charges through billing records. Check preferences, duplicate business events, missing replies and the support workload before declaring the migration complete.
Prepare the migration with your agent
Copy this prompt into your coding agent. It starts with a read-only inventory and routes each task to the guide that owns it.
Code example
Help me prepare a WhatsApp migration from Twilio to Bird.
1. Check whether Bird MCP is connected or the Bird CLI is installed and signed in. Use either existing surface. If neither is available, follow https://bird.com/docs/ai/set-up-your-agent.md.
2. Read https://bird.com/docs/guides/whatsapp/migrate-from-twilio.md. Use the Markdown versions of the linked guides. Inventory the existing integration and customer workflows without changing them.
3. Read https://bird.com/docs/guides/whatsapp/phone-number-setup.md and identify the supported sender transition. Keep the current registration and routing active.
4. Follow https://bird.com/docs/guides/whatsapp/sending-whatsapp.md and https://bird.com/docs/guides/whatsapp/events.md to prepare a controlled message-and-reply test. Discover the available operations; do not invent commands or fields.
5. Show me the proposed changes, test recipient and expected charges. Ask before submitting templates, sending messages, changing routing or cutting over traffic.
6. After an approved test, report the observed delivery and customer outcome separately. Keep the production cutover pending my approval and describe any unresolved result.Next steps
Related resources
Continue with the documentation, guides and examples for this topic. Resources are in English.
Watch the guideConnecting WhatsApp to Bird: from buying a number to a live channelUnderstand the conceptWhat is the 24-hour customer service window on WhatsApp?Use the toolWhatsApp message builderExplore the capabilityWhatsApp
Try the practice and get an implementation brief