> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/migrate-from-other-platform.md).

# Migrate from Other Customer Service Systems to MaiAgent

How to move a LINE Official Account, Facebook Page, or Instagram account from another customer service system to MaiAgent: timing, preparation checklist, steps, and rollback.

If your LINE Official Account, Facebook Page, or Instagram account is already connected to another customer service system (such as Omnichat, Messenger by SHOPLINE, or another LINE management system) and you want MaiAgent to receive and reply to messages instead, follow this page to prepare and switch over. For integration details for each channel, see [LINE](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/line.md), [FB Messenger](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/fb.md), and [Instagram](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/instagram.md). For other channels, see [Publish to Channels](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel.md).

You can decide separately when to migrate and whether to enable AI: move the channels first and have human agents reply, then enable AI later.

## How Long Does the Switch Take, and Will Customers Be Interrupted? <a href="#timing-and-impact" id="timing-and-impact"></a>

**Timing**: With preparations complete, switching all three channels takes about 30 minutes. Allow 1 hour to include time for verification and rollback if needed.

| Item                                                                                      | Estimated time |
| ----------------------------------------------------------------------------------------- | -------------- |
| LINE: create the channel (the Webhook switches automatically at the same time) and verify | 5–10 minutes   |
| Messenger + Instagram: authorize and create the channels                                  | 5–10 minutes   |
| Meta conversation routing: change the default app to MaiAgent                             | 5 minutes      |
| Send one test message through each of the three channels                                  | 5 minutes      |

Moving only LINE takes about 15 minutes.

For example, a retail brand switches after its customer service team finishes work. About 1 minute after creating the LINE channel, it confirms that the Webhook has switched. Messenger and Instagram take about 13 minutes from authorization to completing conversation routing settings. Tests for all three channels finish within about half an hour of starting.

**Almost no interruption for customers**: The LINE Webhook takes effect within about a minute, after which all messages arrive in MaiAgent. Messages customers sent before the switch remain in the old system.

After you change Meta conversation routing, **new conversations** go to MaiAgent immediately. However, for Messenger/Instagram conversations still active in the old system at the time of the switch, subsequent messages continue to be handled by the old system. They move to MaiAgent only when the old system releases the conversation or the customer has not sent another message for about 24 hours (the old system may extend this to up to 7 days). Entry points assigned to the old system for ads or dedicated links may also continue routing conversations there. Have staff monitor both systems for the first few days after the switch. See [FB Messenger: Configure Conversation Routing](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/fb.md#conversation-routing).

{% hint style="warning" %}
Active conversations and conversation history in the old system will not be transferred to MaiAgent. Export any records you need to keep before switching. Choose an off-peak time and tell your customer service team in advance when the switch will happen and where to reply afterward.
{% endhint %}

## Preparation Checklist <a href="#preparation-checklist" id="preparation-checklist"></a>

Check each item one business day before switching:

**MaiAgent**

* An organization owner account, or an account with <mark style="color:blue;">Channel Permissions</mark> to create and edit channels. See [Role and Permission Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/roles/role-permission.md)
* Customer service staff have joined the organization, have their roles and channel permissions configured, and know how to claim conversations with <mark style="color:blue;">Take Over</mark> in the <mark style="color:blue;">Unassigned</mark> tab. They also understand that Messenger/Instagram replies can only be sent within 24 hours of the customer’s last message. See [Human Agent Handoff and Replies](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/human-handoff-operations.md)
* Decide whether to enable AI. If you will not use AI, leave <mark style="color:blue;">AI Assistant</mark> unselected when creating the channel, then immediately disable AI automatic reply hours for all seven days. See [Use Only Human Agents, Without AI](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/web-chat/website.md#human-only-mode)

**LINE**

* You are an Admin for the Provider/Channel in [LINE Developers](https://developers.line.biz/console/). Invitations must be accepted within 24 hours; if one expires, ask the sender to invite you again
* Confirm the Messaging API <mark style="color:blue;">Channel ID</mark>
* A long-lived <mark style="color:blue;">Channel access token</mark> already exists in the Console. Reuse it and **do not click Reissue**. See [Move from Another Management System to MaiAgent](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/line.md#migrate-from-other-line-service)
* Be aware that MaiAgent automatically switches the Webhook as soon as you create a LINE channel, so schedule channel creation for the planned switch time
* Turn off <mark style="color:blue;">Auto-response messages</mark> in LINE Official Account Manager. Decide in advance whether to keep the <mark style="color:blue;">Greeting message</mark> for new friends

**Meta (Messenger/Instagram)**

* A Facebook account with full control of the Page and access to <mark style="color:blue;">Settings</mark> in the business portfolio’s Meta Business Suite (to change conversation routing). See [FB Messenger: Pre-integration Checklist](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/fb.md#pre-integration-checklist)
* Instagram is already a professional account linked to the Page. See [Instagram: Pre-integration Checklist](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/instagram.md#pre-integration-checklist)
* Decide whether to keep or disable Meta’s native automatic replies, such as away messages. See [Customers Still Receive Automatic Replies](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/fb.md#faq-meta-auto-reply)

**Old system**

* Record the original LINE Webhook URL and the original default app for Meta conversation routing (record “not configured” if none was set). You will need these for rollback
* Ask your old provider whether ads that click through to Messenger/Instagram or dedicated links are assigned to the old system. If so, switch them to MaiAgent or disable them during the migration. Also ask whether the provider can release active conversations at the time of the switch. If not, arrange for staff to keep monitoring the old system for a few days afterward
* Inform the old provider of the switch time

**Testing**

* Prepare one personal account each for LINE, Facebook, and Instagram. Add the Official Account as a friend and follow the Page and Instagram account in advance

For example, a customer service manager reviews this checklist the day before the switch and discovers that the colleague responsible for LINE has not accepted the LINE Developers Admin invitation, which expired after 24 hours. They request a new invitation and accept it that day. They also save a screenshot of the current default app for Meta conversation routing, so they will not need to find permissions or look up the original settings during the switch that evening.

## Order of Operations <a href="#switch-order" id="switch-order"></a>

For each channel, the sequence is “**create first, disable AI, then switch traffic**”. LINE is the only exception: the Webhook switches automatically as soon as you create the LINE channel in MaiAgent, so creation and traffic switching happen in the same step. If you will not use AI, leave <mark style="color:blue;">AI Assistant</mark> unselected during creation. Messenger/Instagram traffic switches only after you change conversation routing; creating the channels does not affect customers.

{% stepper %}
{% step %}

### LINE <a href="#switch-line" id="switch-line"></a>

1. Record the current Webhook URL in LINE Developers Console
2. At the planned switch time, create a LINE channel in MaiAgent and paste the existing Channel access token from the Console (do not Reissue). If you will not use AI, leave <mark style="color:blue;">AI Assistant</mark> unselected. The Webhook switches automatically to MaiAgent as soon as you click Create. See [Move from Another Management System to MaiAgent](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/line.md#migrate-from-other-line-service)
3. If you will not use AI, open the channel’s <mark style="color:blue;">Automatic Reply Settings</mark>, disable all seven days, and click <mark style="color:blue;">Update</mark>
4. Confirm that the success screen says “Webhook URL automatically configured and verified”. If it does not, follow the on-screen instructions to configure it manually in the Console and click <mark style="color:blue;">Verify</mark>
5. Confirm that <mark style="color:blue;">Auto-response messages</mark> is off, then send a test from your personal LINE account after about a minute
   {% endstep %}

{% step %}

### Messenger and Instagram <a href="#switch-meta" id="switch-meta"></a>

1. In MaiAgent, authorize using the Page administrator’s Facebook account and create the Messenger and Instagram channels separately (leave <mark style="color:blue;">AI Assistant</mark> unselected if you will not use AI). See [FB Messenger](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/fb.md#start-integration) and [Instagram](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/instagram.md#start-integration)
2. If you will not use AI, disable automatic reply hours for all seven days on both channels
3. In Meta Business Suite’s <mark style="color:blue;">Conversation Routing</mark>, set MaiAgent as the default routing app separately for the Page and the Instagram account. See [FB Messenger: Configure Conversation Routing](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/fb.md#conversation-routing)
4. Switch any active ads or dedicated links assigned to the old system to MaiAgent, or disable them
5. Send a test from a personal Facebook account and a personal Instagram account that have not sent messages before the switch. If you have ad or link entry points, send a test through each one as well
   {% endstep %}

{% step %}

### Verify the Results <a href="#switch-verify" id="switch-verify"></a>

Open <mark style="color:blue;">All Conversations</mark> in MaiAgent and confirm that all three test messages arrived and that AI replies match your earlier decision. For Messenger/Instagram conversations already active in the old system before the switch, subsequent messages may still arrive there. Have staff monitor both systems for the first few days until no new messages arrive in the old system. When AI is disabled, conversations stay in <mark style="color:blue;">Unassigned</mark>, and the status bar shows “Outside AI reply hours · Awaiting customer service”.

If customers still receive messages such as “Our team will reply during business hours”, these are automatic replies from Meta or LINE itself, rather than MaiAgent. See [Customers Still Receive Automatic Replies](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/fb.md#faq-meta-auto-reply) and [Receiving LINE Auto-response Messages](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/line.md#line-auto-response).
{% endstep %}
{% endstepper %}

For example, a brand using only human agents follows this sequence: when creating LINE, it leaves AI Assistant blank and immediately disables automatic reply hours. The screen confirms that the Webhook was configured automatically. After creating Messenger and Instagram and disabling their reply hours, it changes conversation routing in Business Suite. All three test messages appear in “Unassigned” with the status “Outside AI reply hours · Awaiting customer service”. Staff click “Take Over” to reply, and customers receive no AI replies throughout the process.

## Rollback <a href="#rollback" id="rollback"></a>

To return to the old system after switching:

* **LINE**: Change the Webhook URL back to the original URL you recorded before switching, then click <mark style="color:blue;">Verify</mark>
* **Messenger/Instagram**: Change the default routing app back to the original app. If no default app was configured before, select the app that originally handled replies. Restore any ad or link entry points you changed as well. New conversations return to the original system immediately, but subsequent messages in conversations already active in MaiAgent continue to arrive in MaiAgent until the customer has not sent another message for about 24 hours. Have staff keep replying in MaiAgent during that period

You can keep the MaiAgent channels after rollback. To switch back later, simply repeat the traffic-switching step (for LINE, change the Webhook back to the MaiAgent URL in the Console and Verify; for Meta, change conversation routing).

For example, after switching, the customer service team finds that it still needs the old system’s order lookup feature for a while, so the manager decides to roll back. They restore the original LINE Webhook URL recorded beforehand and click Verify, then change the default app for conversation routing in Business Suite back to the old system. A few customers were already mid-conversation in MaiAgent that day, so their subsequent messages continue to arrive there. Staff finish replying in MaiAgent, and from the following day onward, Messenger and Instagram messages all return to the old system. The three MaiAgent channels remain in place. Once a replacement for the old system’s feature is available, the team follows the same steps to switch back to MaiAgent.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/migrate-from-other-platform.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
