How to Replace Intercom Without Losing Data

Published on February 25, 2026 by Antoni

What "Data" Are We Actually Talking About?

When people worry about losing data in a migration, they usually mean one of three things:

1. Help Center articles — the documentation, FAQs, and guides your customers use for self-service
2. Conversation history — past support tickets and chat logs
3. Widget and chatbot configuration — your tone settings, routing rules, saved replies

The good news: all of these can be preserved. The effort required varies by type. Here's exactly what to do for each.

Part 1: Export Your Help Center Articles

This is the highest-value asset and the easiest to migrate.

Step 1: Export from Intercom

In Intercom, go to: Help Center → Articles → (top right) Export

Intercom exports articles in a CSV format containing:

• Article title
• Article body (HTML)
• Article state (published / draft)
• Collection name
• Author name
• Published date

Download the export file and keep it safe.

Step 2: Review before importing

Before blindly importing everything, spend 20–30 minutes reviewing the exported articles:

• Remove outdated articles. Anything referencing old features, old pricing, or old UI should be deleted or updated before import. Importing stale content degrades your AI's knowledge.
• Identify your top 20 articles. These are the highest-traffic, highest-value docs. Prioritize getting them right over importing everything.
• Note articles with images. Intercom exports article text but not hosted images. If your articles have screenshots, you'll need to re-upload them after migration.

Step 3: Import to your new platform

Most Intercom alternatives support article import:

• FutureBase: Go to Content → Import and upload the Intercom CSV. FutureBase parses the HTML content and indexes it for the AI automatically.
• Zendesk / Freshdesk / HubSpot: Each has a Help Center import wizard — look for "Import" in your knowledge base settings. They accept the Intercom CSV format or HTML exports.

What you won't get back:

• Image assets (need re-uploading)
• Article view counts and ratings
• Collection hierarchy (you'll need to recreate categories)

Part 2: Preserve Your Conversation History

This is where most teams overthink things. The practical reality: you almost never need old conversation history after migration.

Here's why: your support team uses conversation history for two things — to look up what a specific customer asked before (usually when the customer emails again), and for quality review purposes. Both use cases are served by the old system remaining accessible (read-only) during and after migration.

The recommended approach: keep Intercom accessible, don't try to import history

Most support tools don't have a clean way to import Intercom conversation history. And the ROI of doing so is low. Instead:

1. Keep your Intercom account on the cheapest plan for 90 days after migration (view-only access for history lookup)
2. Export a CSV of recent conversations from Intercom Reports for your own records
3. Brief your team: "For customer history, check Intercom until [date]. After that, all new conversations are in [new tool]."

After 90 days, the vast majority of customer interactions will be handled entirely in your new platform. Cancelling Intercom at that point loses nothing that matters.

If you truly need history in your new platform

Some enterprise teams or compliance-heavy industries need full conversation history in one place. If that's you:

• Use Intercom's Data Export API to export conversation data as JSON
• Intercom exports conversations with: contact ID, assigned agent, channel, status, created/updated timestamps, and message bodies
• Import this into your new platform's data warehouse or your CRM (not into the support tool itself — most don't support conversation history imports)

Part 3: Recreate Your Widget Configuration

This is often the quickest part — and the most frequently forgotten. Take a screenshot of your current Intercom Messenger settings before you migrate.

Capture these settings:

• Brand color (hex code)
• Widget position (bottom-left or bottom-right)
• Welcome message text
• Business hours settings
• Automated response messages
• Any custom chatbot flows or routing rules

Most of this can be re-entered in your new platform in under 30 minutes.

Saved replies / macros

Intercom calls them "Saved Replies." Export or copy these manually — they're your most-used templates. In FutureBase, add them as FAQ entries (explicit Q&A pairs). In Zendesk/Freshdesk, they're called Macros — there's usually an import option.

Part 4: Handle the Widget Swap

This is the step where things go live. Do it carefully.

Step 1: Deploy to staging first

If you have a staging environment, test the new widget there first. Verify:

• Widget appears on the correct pages
• AI answers test questions correctly
• Escalation path works (human handoff or email)
• Brand colors and welcome message are correct

Step 2: Swap on a low-traffic day

Don't swap the widget at 9am on a Monday. Pick a Friday evening or weekend morning when traffic is lowest. This gives you time to catch any issues before they affect most visitors.

Step 3: Replace the snippet

Remove this from your <head> or <body>:

<!-- Intercom snippet -->
<script>
  window.intercomSettings = { app_id: "YOUR_APP_ID" };
  (function(){var w=window;/* ... */})();
</script>

Add your new widget's embed snippet:

<script src="https://embed.futurebase.io/widget.js" data-wid="YOUR_WIDGET_ID"></script>

Step 4: Monitor for 24 hours

Check your new platform's conversation dashboard hourly for the first day. Watch for:

• Spike in escalations (AI is missing content)
• Confused customers ("This doesn't look like the chat I used before")
• Any pages where the widget isn't showing

Part 5: Update Your Internal Links and Campaigns

Intercom has a customer-facing messenger URL (app.intercom.com/...). Any place you've linked directly to the Intercom messenger needs updating.

Check these:

• Email footers ("Chat with us" links)
• Automated email sequences (onboarding, check-in emails)
• Help Center articles that link to chat
• In-app help buttons or tooltips
• Your website's Contact or Support page

This is the most time-consuming part of a migration for teams that use Intercom heavily for outbound. Budget 2–4 hours to audit your email templates and in-app links.

Migration Timeline

What You'll Lose (And Whether It Matters)

The vast majority of teams that switch from Intercom report that the things they thought they'd miss, they didn't.

The Fastest Migration Path

If you want to move fast:

1. Export Help Center articles (15 min)
2. Sign up for FutureBase and enter your website URL for auto-crawl (5 min)
3. Import your top 20 articles (30 min)
4. Add 10 FAQ entries for your most critical policy questions (30 min)
5. Swap the widget on your site (15 min)
6. Update your email templates over the next 2 weeks (2–4 hrs)

Total: core migration done in under 2 hours. The email/link updates can happen over the following weeks without any customer-facing disruption.

— Antoni