> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ada.cx/docs/channels/messaging/migrating-to-messaging/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ada.cx/_mcp/server.

# Migrating to Messaging

## Overview

Move an existing integration to [Messaging](/docs/channels/messaging) with your Ada team and developers. Record the transition date for each AI Agent.

## Limitations

[Messaging](/docs/channels/messaging) requires a generative AI Agent. Changing the integration package and enabling Messaging are separate parts of the transition.

A dashboard label does not prove that every installed mobile app or bundled package has been upgraded.

## Capabilities & configuration

Identify how your current [Chat](/docs/channels/chat) integration loads before you choose a migration path.

| Existing integration              | Required preparation                                                                                          |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Hosted web script tag             | Keep the script tag. The loader selects Messaging when your AI Agent transitions.                             |
| `@ada-support/embed2` npm package | Replace the package with the Messaging loader. A server-side transition does not upgrade bundled legacy code. |
| iOS, Android, or React Native SDK | Follow the platform migration guide and release an updated application.                                       |
| Custom interface                  | Review bridge or headless integration contracts and implement the required interface behavior.                |

## Implementation & usage

Use the [Messaging](/docs/channels/messaging) migration guides for the exact code changes.

**To migrate an integration:**

1. Inventory the websites, apps, packages, and custom interfaces that connect to your AI Agent.
2. Review the [web migration guide](/messaging/web/getting-started) or the [mobile integration guides](/docs/channels/messaging/messaging-configuration/installation).
3. Check the [security requirements](/messaging/web/security-best-practices), including content security policy and custom app origins.
4. Configure [appearance](/docs/channels/messaging/messaging-configuration/appearance-settings), [launch options](/docs/channels/messaging/messaging-configuration/launch-options), and [persistence](/docs/channels/messaging/messaging-configuration/data-controls).
5. Test anonymous users, identified users, account switching, and sign-out.
6. Test human support, file handling, notifications, language selection, and surveys.
7. Coordinate production enablement and rollback with your Ada team.
8. Record the transition date and compare [reporting differences](/docs/channels/messaging/reporting-and-surveys).

## Best practices

Validate [Messaging](/docs/channels/messaging) on the actual host website or mobile app. Dashboard tests do not validate your site's security policy or application lifecycle.

Review metadata limits and identity failures before production. An identity-token failure can continue the session anonymously.

Keep legacy installation details available while older applications remain in use. Confirm each integration separately before you retire its setup instructions.

---

Have any questions? Contact your Ada team, or email us at [](mailto:help@ada.cx?subject=Help%20Docs%20inquiry).