Migrate from Segment to Monfri CDP

Is this migration right for you?

Monfri replaces Segment well if your usage is:

• Tracking user events from web + mobile
• Building audience segments
• Identity resolution (deterministic)
• Activating via email/push/SMS/webhooks

Monfri is NOT the right replacement if you rely on:

• Routing data to 20+ warehouse/analytics destinations
• Segment Protocols schema enforcement (strict, regulated industries)
• Segment's Reverse ETL at scale

For those cases, keep Segment or evaluate RudderStack / Hightouch.

Step 1 — Export your tracking plan (15 min)

In Segment: Workspace → Tracking Plans → [your plan] → Export JSON.

Monfri imports Segment tracking plans directly. Event names, property schemas, and required flags map 1:1.

Step 2 — Set up Monfri CDP (30 min)

Activate CDP in your Monfri workspace. Create a Source (representing your website or app). Copy the write key.

Step 3 — Swap SDK calls (1-3 hours)

Segment API: analytics.track('Event Name', { prop: value })

Monfri API: monfri.track('Event Name', { prop: value })

Property signatures are identical. For most codebases:

1. Replace <script src="segment..."> with Monfri SDK script tag
2. Find-and-replace analytics. with monfri. in your code
3. Swap analytics.identify(userId, traits) → monfri.identify(userId, traits)
4. Swap analytics.page() → monfri.page()

For larger codebases with 100+ events, use grep + sed or IDE refactor tools. Typical automation: 80-95% of replacements done mechanically.

Step 4 — Migrate audiences (2-4 hours)

Segment Engage audiences don't export as a standard format. Rebuild in Monfri's visual segment builder:

1. List all active audiences in Segment (Workspace → Audiences)
2. For each, note the inclusion rules (AND/OR conditions on events + traits)
3. Rebuild in Monfri: CDP → Segments → New
4. Same AND/OR structure; same event reference syntax

Step 5 — Parallel-track both (3-7 days)

Run both SDKs simultaneously for a period. Send events to both Segment and Monfri. Validate:

• Event counts match day-over-day
• Identity merging behaves as expected
• Segment membership counts match between platforms

If Monfri shows different numbers than Segment, investigate — usually a SDK call was missed.

Step 6 — Wire activation (1-2 days)

In Segment, you routed data out to activation tools (email, ads, warehouse). In Monfri, email/push/SMS/CRM are native services — wire segment triggers directly to campaigns.

For external destinations still needed (e.g., BigQuery warehouse), use Monfri Automation HTTP connector or native warehouse connector.

Step 7 — Remove Segment SDK (5 min)

Once Monfri is running all critical use cases, remove the Segment script tag. Cancel Segment subscription.

Tips for large codebases

• Gradual rollout. Swap SDKs one page/feature at a time rather than big bang.
• Keep both libraries briefly. For 3-7 days, both SDKs run side-by-side. Switch one feature per day.
• Track parity with a dashboard. Build a view comparing Segment event counts to Monfri event counts per event name. Deviations > 5% investigate.
• Server-side first. If you're comfortable, migrate server-side tracking (Node/Python/Ruby SDK) before client-side. Less risk.