# Migrate Apple Messages from Infobip

Inventory the Apple business connection, Infobip channel settings, Answers flows, Conversations routing, native templates and optional integrations. Identify where customer identity, payment, booking and outcome reporting are implemented before translating the journey.

## Prerequisites

Prepare authorized access to both platforms, the team managing the Apple business connection, representative devices and the owners of your service integrations. Confirm the supported provider-change procedure and account access before changing production traffic.

## 1. Record the existing journey

Infobip exposes optional Apple Pay, authentication and custom app settings for the business account. The payment configuration includes the merchant and gateway relationship, and its guidance describes additional callbacks and a fallback destination. Evaluate the actual merchant integration alongside the message authoring experience.

Follow a real service task from entry point to resolution. Record the original business, conversation, native interaction and business-operation references. Keep customer account identity distinct from channel-specific identifiers.

## 2. Prepare the receiving experience

Connect the intended Bird business and test path. Translate native content and returned answer meaning into the documented receiving structure. Recreate the required identity, preference, routing and human support behavior.

Treat Invitation Messages separately: inventory their approval, templates and consent evidence instead of assuming ordinary conversation migration transfers invitation permission.

## 3. Verify the task and its recovery

Test a complete native interaction on representative devices. Confirm the actual booking, account or payment outcome in the system that owns it. Exercise an unavailable choice, refused access, unexpected free text and human handoff.

Test an uncertain response before relying on retries. Retain the original operation identity and inspect its state so a lost reply does not create duplicate customer contact or business actions.

## 4. Coordinate the change

Agree the business/provider transition with the responsible teams and complete any required Apple review. Define which system owns new conversations and how existing service requests continue. Preserve historical records and useful identity mappings.

Open a bounded set of entry points when the operating team is ready. Check the correct business, route, native content and outcome reporting. Keep a clear pause and recovery decision for unexpected behavior.

## Verify the migration inventory

Map the Apple business, entry points, native templates, Answers branches, Conversations routing and application callbacks used by your current service. For each item, record the receiving Bird configuration and the person who will verify it. Test a complete request before changing the customer-facing route.

| Test case                                           | Action                                                                           | Expected result                                                                                     |
| --------------------------------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| A native option uses a provider-specific identifier | Map its business meaning and receiving response handling explicitly.             | The same customer choice reaches the intended business action.                                      |
| A conversation needs a person after automation      | Test the receiving queue, assignment and handoff context.                        | The service team can continue the customer’s request.                                               |
| The cutover check fails                             | Use the agreed fallback and keep the current service usable while investigating. | Customers retain an appropriate contact route and the migration owner can identify the failed step. |

## Troubleshooting

If the wrong team receives a conversation, inspect entry-point context and the receiving route. If an interaction returns unusable data, review choice and page identifiers. If payment is uncertain, reconcile the payment record before initiating another charge.

## Provider references

- [Infobip Apple Messages setup](https://www.infobip.com/docs/apple-messages-for-business/get-started).
- [Infobip Apple Messages documentation](https://www.infobip.com/docs/apple-messages-for-business).
- [Infobip optional integrations](https://www.infobip.com/docs/apple-messages-for-business/manage-optional-configurations).

## Next steps

- [Compare Bird and Infobip](/products/apple-messages/compare/bird-vs-infobip).
- [Register the business](/docs/guides/apple-messages/registration).
- [Integrate Apple Messages](/docs/guides/apple-messages/api).
- [Measure the journey](/docs/guides/apple-messages/analytics).

## Related resources

- [What is Apple Messages for Business?](/explained/apple-messages/what-is-apple-messages-for-business) (answer)
- [Apple Messages for Business](/products/apple-messages) (product)

[Get an implementation brief](/learn/workspace?topic=apple-messages)