How to replace ManyChat without losing a single flow

Migrating off ManyChat is a 1-2 week project if you plan it. It's a 4-6 week disaster if you don't. Here's the playbook we use at Bamberg Digital when we move client accounts from ManyChat to Conduit.

Why agencies leave ManyChat in 2026

The pattern is consistent across the agency conversations we have:

• The bill doubles every 6 months as client subscribers grow
• Per-workspace pricing means each new client adds a full Pro subscription
• Channel coverage is limited (no native X / LinkedIn DMs)
• The contact graph doesn't talk to the email tool or the CRM

For agencies who've outgrown ManyChat, Conduit is the natural next step. But the migration has to be planned carefully — flows that work today can't go dark for 48 hours during the cutover.

Pre-migration audit (Week 0)

Before exporting anything, do a complete audit of the existing ManyChat setup:

1. List every active flow. Note: trigger type, channel, completion volume per month, conversion goal.
2. List every subscriber list / tag. Note: list size, source, segmentation logic.
3. List every integration. Note: Zapier zaps, native integrations (Shopify, Stripe, Calendly), webhooks.
4. List every team member. Note: role, permissions, what flows they own.

Most clients have 10-30 active flows. About 30% are obsolete or duplicate; the audit is your chance to clean up before migrating.

Export ManyChat data (Week 1, day 1-2)

ManyChat exports subscribers as CSV (one row per subscriber, columns for tags, custom fields, channel handles). Flows export as JSON via the ManyChat API or a Chrome extension we maintain at Bamberg Digital.

Critical: subscriber consent records. ManyChat captures opt-in via the "opt_in" channel-specific field per subscriber. You must preserve this when migrating — re-prompting for opt-in is a 30-50% drop event.

Conduit imports the CSV and JSON directly. The opt-in field is mapped to Conduit's consent record. Custom fields are preserved as Conduit custom fields. Tags become Conduit segments.

Set up Conduit workspace (Week 1, day 2-3)

In Conduit:

1. Create a new workspace per client (or use existing if agency-level).
2. Connect Meta Business: same Facebook Page + Instagram Business account that was on ManyChat.
3. Connect any other channels: X, LinkedIn, SMS (Twilio), email senders.
4. Configure brand voice in Inbox settings (logo, color, default reply tone).

Critical: when you connect Meta Business to Conduit, ManyChat doesn't lose its connection. Both apps can be authorized simultaneously. This is your safety net during the cutover.

Rebuild flows in Conduit (Week 1, day 3-5)

For each ManyChat flow, decide:

• Auto-migrate: simple flows (welcome, comment-to-DM, single-step keyword reply) can be auto-converted via Conduit's migration helper. JSON in, Conduit Flow out. Test then publish.
• Manual rebuild: complex flows with multiple condition branches, custom field reads, or external integrations. Manual rebuild in Conduit Flow Canvas. Plan 30-60 minutes per flow.
• Skip: flows that are inactive, obsolete, or redundant. Delete from ManyChat post-migration.

Conduit's Flow Canvas supports all ManyChat node types: Send Message, Smart Delay, Condition, Tag (Add / Remove), Set Field, Subscribe to Sequence (Conduit calls these Sequences). Plus modern additions Conduit ships natively: Send Email, Schedule Post, Update CRM, Webhook Out.

Parallel run (Week 1, day 5 — Week 2, day 2)

This is the most important week. ManyChat and Conduit both connected to the same Meta Business. Both flows active. New subscribers go through Conduit; existing subscribers continue on ManyChat.

How: in ManyChat, pause all triggers for new conversations. Existing subscribers in mid-flow continue (don't interrupt them). All NEW inbound messages are routed to Conduit via Meta's default routing rules (whichever app responds first wins).

This gives you 5-7 days to test Conduit flows under real load before fully cutting over. Bugs and edge cases surface here.

Cutover (Week 2, day 3-4)

Once parallel run is clean (no Conduit-side bugs for 48 hours), execute the full cutover:

1. In ManyChat: pause ALL active flows.
2. In Conduit: enable all flows.
3. Watch the unified Conduit Inbox for 24 hours. Address any one-off issues.
4. Disconnect ManyChat from Meta Business after 5 days of clean operation.

Post-migration cleanup (Week 2, day 5-7)

Three things to do after cutover:

• Cancel ManyChat subscription. Don't pay for two tools.
• Update internal documentation. Team Wiki, SOPs, integration docs. Everyone needs to know "we're on Conduit now".
• Reconfigure integrations. Zapier zaps that pointed at ManyChat webhooks now point at Conduit webhooks. Shopify integration switches to Conduit's native adapter.

The 7 gotchas to plan for

1. Opt-in records. Verify they migrated correctly. Re-prompting destroys the list.
2. Tag-based segmentation. ManyChat tags become Conduit segments — but Conduit's segment builder is more powerful, so simplify where possible.
3. Subscriber custom fields. If you have 50+ custom fields, prune to 10-15 essential ones. Most are obsolete data.
4. Sequence drip cadence. ManyChat sequences with day-based delays need to be carefully mapped to Conduit Flow delays. Off-by-one timing errors are common.
5. Comment-to-DM rate limits. Meta's rate limits apply per page, not per app. Switching apps doesn't reset the limit.
6. Stripe integration. If ManyChat's Stripe integration was firing on payment events, rebuild the webhook in Conduit Stripe adapter.
7. Reporting baseline. Conduit's analytics start fresh post-migration. Export ManyChat historical analytics before cancelling subscription.

What you gain on the other side

• Flat $397/mo (or $997/mo Atelier) regardless of subscriber count
• Cold outreach module (email + LinkedIn) bundled in same workspace
• Publisher module for content scheduling
• Unified contact graph across DM + email + form submission
• Local AI for unlimited personalization at zero token cost

The migration takes 1-2 weeks if planned. Once you're on the other side, the operating overhead drops significantly — fewer tools, one bill, one auth, one set of credentials to maintain.

If you want help with a ManyChat migration, our Atelier tier ($997/mo) includes done-with-you migration. Contact Bamberg Digital for a scoped engagement.