New post: Introducing BYO ClickHouse for UserFlux
Migration Guide

How to migrate from mParticle to UserFlux

Migrating from mParticle to UserFlux means moving from an enterprise CDP focused on data plumbing to a composable, warehouse-native platform with built-in analytics, automation, and activation. Instead of routing data through mParticle to downstream tools, UserFlux handles the entire lifecycle — collection, analytics, segmentation, and action — on your ClickHouse warehouse. Most teams complete the migration in 3-5 weeks.

Your migration path from mParticle.

1
2-3 days

Audit data inputs and outputs

Document your mParticle inputs, outputs, audiences, data plans, and identity configuration. Identify which downstream tools UserFlux replaces and which need alternative integrations.

2
3-5 days

Replace mParticle SDK with UserFlux SDK

Swap the mParticle SDK for the UserFlux SDK across web and mobile. The event model is similar, so most instrumentation changes are straightforward.

3
2-3 days

Migrate audiences and segments

Recreate your mParticle audiences as UserFlux audiences. UserFlux audiences are powered by real-time warehouse queries, giving you more flexibility than mParticle's audience builder.

4
3-5 days

Recreate data connections

Replace mParticle output connections with UserFlux integrations. Many outputs become unnecessary because UserFlux handles analytics, automation, and personalization natively.

5
2-3 days

Set up identity resolution

Configure UserFlux's identity resolution to match your mParticle identity strategy. Map identity types and priority rules to their UserFlux equivalents.

6
5-7 days

Validate and switch

Run both systems in parallel to compare event volumes, user counts, and audience sizes. Once validated, remove mParticle and consolidate on UserFlux.

mParticle→ UserFlux concept mapping.

mParticleUserFluxNotes
InputsSources / SDKSingle SDK for web and mobile data collection
OutputsIntegrationsMany outputs replaced by built-in features
AudiencesAudiencesReal-time segmentation powered by warehouse data
User profilesUser ProfilesEnriched automatically from warehouse data
EventsEventsDirect 1:1 mapping
User attributesPropertiesUser and event properties with warehouse enrichment
Calculated attributesComputed propertiesDynamic properties calculated from event data
Data plansSchema validationDefine and enforce event structure and data quality
KitsSDK modulesModular SDK with configurable capabilities

What you gain by switching.

Warehouse-native data ownership

Your data lives in ClickHouse, not locked inside mParticle's proprietary storage. Query it directly, join it with other sources, and bring your own ClickHouse instance if you prefer.

Built-in analytics and activation

Stop using mParticle as plumbing between tools. UserFlux includes analytics dashboards, automation workflows, personalization, and search — no downstream tools required.

Transparent pricing

Replace mParticle's opaque enterprise contracts with transparent, usage-based pricing. Know exactly what you pay for with no surprises at renewal time.

Composable architecture

UserFlux is composable by design. Use the full platform or bring your own ClickHouse instance. Integrate with any tool through APIs. No vendor lock-in.

Frequently Asked Questions

Get started today with $150 credits

Create an account instantly to get started or contact us to design a custom package for your business.

Always know what you pay

Cost effective usage based pricing with no hidden fees.

Pricing details

Start your integration

Get up and running with our APIs in as little as 10 minutes.

API reference