# Migrate Apple Messages from LivePerson

Inventory the business connection, Structured Content templates, metadata, Conversation Builder flows, skills or queues, authentication provider and business integrations. Preserve the meaning of page, choice and account references when translating the experience.

## 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

LivePerson models Apple interactions through Structured Content templates and metadata. Its authentication template connects to the business’s own OAuth service, while its form template defines native pages and answer structure. Compare how your team authors those experiences and handles the returned input.

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, Structured Content templates, conversation routing, bot behavior and application integrations your current service uses. Record the receiving Bird experience and a verification owner for each item. Keep business identity and provider-specific content identifiers distinct during the move.

| Test case                                                    | Action                                                                               | Expected result                                                                             |
| ------------------------------------------------------------ | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
| A Structured Content template has provider-specific behavior | Rebuild the intended native interaction and verify the returned response.            | The customer can complete the same decision in the receiving journey.                       |
| A request moves from automation to an agent                  | Verify the destination team, collected context and exclusive conversation ownership. | The person helping the customer can continue the original task.                             |
| A connected payment or identity flow fails after cutover     | Inspect that integration’s configuration and apply the agreed service fallback.      | The customer receives a usable next step while the migration owner resolves the dependency. |

## 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

- [LivePerson Apple templates](https://developers.liveperson.com/apple-messages-for-business-templates-introduction.html).
- [LivePerson form template](https://developers.liveperson.com/apple-messages-for-business-templates-form-message-template.html).
- [LivePerson Apple authentication](https://developers.liveperson.com/consumer-authentication-authenticate-in-apple-messages-for-business-overview.html).

## Next steps

- [Compare Bird and LivePerson](/products/apple-messages/compare/bird-vs-liveperson).
- [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)