GuideUpdated 4 min read
How to migrate from Intercom to Campfire: a step-by-step checklist
Campfire checklist for leaving Intercom: what to inventory, what the self-serve importer brings across, what you rebuild by hand, and how to cut over safely.
Moving off Intercom is mostly a planning exercise. Your data can be copied, but your workflows, routing, channel connections and AI behaviour need to be rebuilt and tested. This checklist covers what Campfire's built-in importer brings across, what you do by hand, and how to switch over without a gap in coverage. If you only want the importer, go to /migrate-from-intercom.
Before you start
- Check your Intercom contract and renewal date so you know how long you can run both tools. Campfire has a 14-day trial with no card required, and Intercom data stays in Intercom after an import.
- Decide who will run the migration. The importer needs a Campfire workspace owner or admin and an Intercom access token with read access.
- Know your Intercom region (US, EU or AU). The importer asks for it.
- Pick a quiet period for the cutover, and tell your team what changes for them.
Step 1: inventory what you use in Intercom
List what is actually in use, not what the plan includes. Typical items:
- Inboxes and teams, assignment rules and round-robin.
- Workflows and automations, saved replies, tags and custom attributes.
- Channels: Messenger on your site and app, email, WhatsApp, SMS and any social channels.
- Help center articles and collections.
- The Fin AI agent configuration, and whether anything depends on Copilot.
- Product tours, checklists and other proactive messaging.
- SSO, SLAs, and any reporting people rely on.
Step 2: map Intercom concepts to Campfire
| In Intercom | In Campfire | How it moves |
|---|---|---|
| Contacts | Customers | Imported |
| Conversations | Conversations | Imported, every conversation part Intercom exposes through its API |
| Tags | Tags | Imported |
| Help center articles | Knowledge base articles | Imported; they ground the AI answers |
| Tickets | Tickets | Imported where Intercom exposes them through its API |
| Workflows and team inboxes | Workflows, team inboxes, round-robin, SLA policies | Rebuilt by hand |
| Messenger | Campfire widget | Replace the snippet |
| WhatsApp, SMS and other channels | Channel connections | Reconnected by hand |
| Fin AI agent | Campfire AI agent (managed AI or your own provider keys) | Configured by hand |
| Product tours and checklists | No equivalent | Not available in Campfire |
| SAML SSO | No equivalent yet | Not available in Campfire |
Step 3: start a Campfire workspace
Create a workspace on the 14-day trial. Keep Intercom running; nothing in this process switches it off. Invite the people who will test.
Step 4: preview, then run the importer
- As a workspace owner or admin, open Settings, Import and choose Intercom.
- Paste an Intercom access token and pick the region. When you start the import, the token is stored temporarily in the tenant-scoped credential vault (
integration_credentials) encrypted at rest with AES-256-GCM, given a 6-hour expiry, and deleted when the import job finishes or fails. - Preview the counts Intercom reports for conversations, contacts, tags, articles and tickets. If a count is unavailable, check the token's read scopes and try again.
- Start the import. It runs in the background, so you can keep working.
- Read the final report. It flags API truncation and compares what was staged with Intercom's source counts.
The importer is self-serve. No staffed migration service is offered, and no completion time is promised because it depends on how much history Intercom returns through its API.
Step 5: rebuild what does not import
- Recreate team inboxes, round-robin assignment, workflows and SLA policies. These are available on both Starter and Growth within usage caps.
- Connect channels: web widget, email, WhatsApp, SMS, Telegram, Messenger, Instagram. WhatsApp and SMS carry no Campfire fee, but carrier, Meta or Twilio charges apply.
- Set up AI: choose managed AI or add your own provider keys under Settings, AI Providers (see Bring your own AI), then read through the imported articles and fix any that are out of date.
- Decide what to do about anything with no equivalent: product tours and checklists, SAML SSO, voice. If these are essential, Campfire may not be the right move yet.
Step 6: test in parallel
- Install the Campfire widget on a staging site or a small slice of pages. The installer (
npx campfire-widget@latest init) detects your framework and writes a snippet; follow the generated steps. - Ask your team to answer test conversations on every channel you use, and to try AI drafts on real questions from the imported history.
- Compare the importer's report with what you expect, and spot-check a handful of old conversations and contacts.
Step 7: cut over
- Point channels at Campfire (email forwarding, WhatsApp number, social inboxes) during a quiet period.
- Replace the Intercom Messenger snippet with the Campfire widget.
- Watch the first days closely: new conversations arriving, assignment working, AI handoffs reaching a person.
- Keep the Intercom account until you are satisfied nothing is missing.
Rolling back
Because the importer copies data and leaves Intercom untouched, the rollback is to re-add the Intercom snippet and re-point your channels. Conversations that happened in Campfire after cutover will not appear in Intercom, so keep the window short and note the cutover time.
Cost check
Campfire Growth is $20 per month flat for up to 10 seats (fair use), with caps of 2,500 conversations and 500K managed AI tokens per month; Starter is free within hard limits. For Intercom's side, its pricing page (intercom.com/pricing, as of 2026-10) lists seats at $29, $85 and $132 per month for Essential, Advanced and Expert, and Fin at $0.99 per outcome. The Intercom pricing calculator and the Intercom alternative page lay out the comparison.