Switching from Intercom to Chatting: what to move and what to keep

Start with the work you want to keep

Switching from Intercom to Chatting makes sense when your team mostly answers website questions and wants a shared inbox without maintaining a larger support platform. It becomes a different project if Intercom also runs your campaigns, automated support, or internal ticket processes. List those jobs before you remove anything. A lower software bill will not help if customers lose a way to reach you.

Make the decision around actual recent conversations. Pick a purchase question, an existing customer problem, a message received outside working hours, and a conversation handed to another teammate. Write down where each started, who replied, and how it ended. Those four examples provide a much better replacement checklist than a screenshot of the old feature menu.

Separate the new inbox from the old archive

Adding a new website widget does not transfer your Intercom history. Those are separate operations. Intercom documents contact and reporting exports as well as conversation exports through its API or Amazon S3. The format matters: a report showing conversation counts is not the same thing as a readable transcript with every message and attachment. Check what you downloaded before cancelling access.

Do not assume an Intercom export can be imported directly into Chatting. This guide does not promise a native transcript importer. Keep an accessible archive and decide who can use it when an older customer returns. Check that a teammate can find a sample customer's complete thread without relying on the original agent's laptop or personal account.

Check whether you are replacing more than chat

A team may think it is buying a chat button while depending on several other systems. Review any Fin answers, outbound messages, product tours, forms, help articles, and rules you actually use. Record the customer outcome each produces. If an automation sends a promised follow up, either keep that process running or replace it deliberately before changing the visitor entry point.

Chatting is strongest when a visitor asks a question and a person needs enough context to answer. Assignments, saved replies, visitor context, and email follow up support that work. They do not establish that every Intercom automation has an equivalent. If an essential process depends on functionality you cannot replace, retaining Intercom can be the sensible choice.

Pilot the conversations before changing the website

Use a staging page or another controlled installation to try the new widget. Send a question as a visitor, reply as the primary agent, and ask the backup agent to take over. Repeat with the team unavailable. Read the visitor's experience from beginning to end, including the wording that explains when a person will reply. Do not treat seeing a launcher as proof that support is ready.

For a small team, the useful result is concrete: the second person can see what the first person already said, the visitor knows who is responding, and an unfinished question has a named owner. Walk through the shared inbox with those examples. Record any missing step while the existing support channel is still available.

Finish open conversations where customers started them

Give every open Intercom conversation an owner before the switch. Some can finish there while new website conversations begin in Chatting. Others need a direct message explaining the next contact method. Do not silently drop a customer into a fresh thread and expect them to repeat their issue. Keep the old inbox available for the agreed transition period where your subscription permits it.

A hypothetical software team might move new sales questions first while its support agent closes outstanding technical cases in Intercom. That is a staged transition, not a claim that the tools synchronize. Decide who checks each inbox during the overlap and when the overlap ends. Otherwise the migration creates the multiple inbox problem you wanted to remove.

Change one visitor entry point at a time

Find every place the old script loads. Check your website template, tag manager, plugins, and application layout. Removing one copy does not remove another copy installed elsewhere. Before enabling the replacement on a page, confirm the old launcher no longer appears there. Two visible widgets give visitors an unnecessary choice and divide new messages between inboxes.

Keep the previous installation settings so the change can be reversed if the pilot exposes a missing requirement. Reversing the website installation will not merge conversations created in the replacement inbox, so keep an owner watching those too. Start with the Intercom replacement comparison if you have not yet decided what you can give up.

Compare the ongoing bill after the move

Calculate the tools you will still pay for after moving website chat. A separate campaign tool, archived inbox access, or retained automation may change the saving. Use the existing Intercom pricing breakdown to identify seat and usage categories, then compare the current checkout for your account. A migration budget should include the overlap period rather than assuming every old charge stops immediately.

Chatting Growth is $20 per month with three team members included, with additional members at $6 each per month. That is useful for a small group rotating website replies. Compare current plans against the number of people who actually need access. Choose the move when the pilot proves the new inbox handles your customer conversations and the remaining tools still justify the total bill.

Sources checked on 25 October 2026

intercom.com source 1

Try it with your own website

Recommended next steps

FAQ