Overview

You can move your existing campaigns from tools like Intercom or Customer.io into Journeys in three steps. Let an AI tool rebuild the campaigns for you, import your users and their data, then switch over without messaging anyone twice.

Keep your old tool running until the new journeys are live.

Why migrate to Featurebase

Journeys have no separate price, and their messages use low usage-based pricing. This is the monthly messaging cost by number of users, with one email and 0.2 in-app messages per user each month:

Based on public pricing in November 2026, without seat or plan fees. Intercom needs the Proactive Support Plus add-on for in-app messages and charges for emails separately. Customer.io charges by the number of people in your workspace, not by messages sent. See pricing and usage for the details.

Recreate your campaigns with AI

The Featurebase MCP server lets AI tools like Claude, ChatGPT, Cursor, and Codex build journeys in your workspace. The AI adds the blocks, waits, and rules, and writes the message content. It saves everything as a draft, so nothing reaches people until you publish.

1. Connect your AI tool in Settings → MCP. The MCP server is available on all paid plans

2. Give the AI one campaign at a time. Let it read the campaign in your old tool with its browser, for example with Codex, Claude in Chrome, or ChatGPT agent, or paste the steps and message content into the chat

3. Ask it to rebuild the campaign as a journey, and to stop before it publishes (see the example prompt below)

4. Open the draft in Dashboard → Outbound → Journeys and review the entry audience, each message, and the rule conditions

5. Use 'Preview as…' to walk one person through the journey, then publish it yourself

Example prompt:

Open the campaign "Trial onboarding" in Intercom and list every step: who enters, each message (channel, subject, body, buttons), every wait, and every condition with its branches.

Then use the Featurebase MCP to create a journey with the same flow: set the entry audience, add the matching blocks in the same order, write the message content, and recreate the waits and rules. Validate the draft and fix what it reports.

Do not publish. Tell me the name of the journey and list anything you could not recreate.

For more detailed work, you can also use a browser agent such as Codex or Claude in Chrome. It works directly on the Journeys canvas, so it can copy the exact layout of an email, adjust the settings of each block, and compare every step with your old tool. A browser agent also works when your AI tool does not support MCP.

Check these by hand, because tools name them differently:

• Audience rules - Match each attribute to the same field in Featurebase. Import the data first (see below), so the fields exist

• Rules on email activity - Opens and clicks are tracked only for emails sent from your own sending domain

• Channels - In-app blocks need the Featurebase Messenger on your site, and product tours show only in desktop browsers

See the block library for what each block does.

Import your users and their data

Journeys can only reach people that Featurebase knows. Import them before you publish, together with the data your audience rules and conditions use.

• One-time import - Export users and companies from your old tool as CSV and import them from CSV

• Ongoing sync - Create and update contacts with the Featurebase API, so new signups and changed attributes reach Featurebase automatically

• Events - Send the actions your journeys trigger or branch on as custom events from your product

• Unsubscribes - Carry over each person's email preferences with the API or the MCP server, so people who opted out in your old tool stay opted out

Switch over without double messages

People can be in a campaign in your old tool and enter the same journey in Featurebase. To avoid sending them the same message twice:

1. When you publish each journey, choose 'Only people who qualify from now on'. People who already match the audience do not enter, so your existing users do not get onboarding again

2. Pause or stop the matching campaign in your old tool at the same time

3. Watch the journey report for the first days, and use troubleshooting if someone does not enter

Create and manage journeys from Dashboard → Outbound → Journeys.