CleverTap to Braze Migration Guide

CleverTap's differentiating claim is the combination of analytics and engagement in a single platform. That integration is genuinely useful — until it isn't.

The teams migrating from CleverTap to Braze have typically reached a specific inflection point: the unified analytics-engagement model that made CleverTap efficient at one scale becomes a constraint at the next. The engagement infrastructure needs to deepen — in Connected Content capability, in data warehouse integration through Currents, in Canvas Flow's cross-channel orchestration depth — faster than CleverTap's product development can match it. And often, the analytics function is being taken over by a dedicated analytics platform anyway, making the CleverTap analytics bundling less relevant.

At Propel, we've managed CleverTap migrations for consumer app brands across health and fitness, media, and marketplace verticals. The migration has a distinct character because CleverTap's architecture — particularly its approach to segments, RFM, and event-based campaigns — is meaningfully different from Braze's model.

Why Teams Move From CleverTap to Braze

Connected Content. CleverTap's personalization model pulls user profile properties into messages. It is attribute-based and static at send time. Braze's Connected Content makes a live API call at send time to pull dynamic content from any external endpoint — recommendation engines, real-time pricing, live inventory, current account status. For media brands personalizing content feeds, marketplace brands surfacing live pricing, or health apps pulling current plan data, Connected Content changes what personalization means at the send level. This is why building personalized email flows without manual work looks different in Braze than in CleverTap.

Data warehouse integration. Braze Currents streams every engagement event — send, delivery, open, click, conversion — to your data warehouse in real time. CleverTap's data export capabilities are less comprehensive. For teams running a dedicated analytics platform (Amplitude, Mixpanel) or a data warehouse, Currents closes the attribution loop in a way that CleverTap's architecture doesn't match. This matters for DTC revenue and LTV attribution and for behavioral segmentation that depends on warehouse-quality data.

Canvas Flow orchestration depth. Braze's Canvas Flow — with Audience Paths, Action Paths, and Experiment Paths — handles cross-channel lifecycle orchestration at a depth that CleverTap's Journey builder doesn't match. For teams building omnichannel orchestration programs with complex branching logic across email, push, in-app, and SMS, Canvas Flow's architecture is meaningfully more expressive.

Enterprise integration ecosystem. Braze's native integrations — Amplitude, Segment, Snowflake, Salesforce, Google Ads, and many others — represent a broader enterprise integration surface than CleverTap's. For brands building a modern customer engagement stack, the integration depth matters.

One consumer fitness brand we migrated had built CleverTap's RFM-based segmentation into their entire lifecycle program — Champions, Loyal Customers, At Risk, Hibernating. The migration catalyst was a need for real-time workout completion triggers that fired personalized recovery content within minutes of a session ending. CleverTap's event processing latency and attribute-based personalization model couldn't support the real-time requirement. In Braze, the Canvas triggered on workout_completed with properties (duration, intensity, type) and fired Connected Content-powered personalization within 90 seconds. The customer retention for fitness and weight loss apps metric impact was visible within 30 days.

The Architecture Difference: CleverTap vs. Braze

CleverTap's model: Analytics-integrated and funnel-centric. Users are identified by identity attributes. Events are tracked for both analytics and engagement. Segments can be RFM-based (recency, frequency, monetary value computed by CleverTap's engine), funnel-based, or event-filter-based. Campaigns are channel-specific; Journeys handle multi-step sequences. The analytics and engagement data share the same database — which simplifies some workflows and constrains others.

Braze's model: Engagement-first with analytics infrastructure alongside it. Custom Attributes (profile properties) and Custom Events (behavioral events with nested properties). Canvases trigger off Custom Events from any source. Segmentation uses Custom Attributes and event filters — more granular than CleverTap's RFM approximations for behavioral targeting, but requiring more deliberate schema design to get right. Analytics run separately through Currents and connected analytics platforms.

The migration consequence: CleverTap's RFM segments must be translated into Braze Custom Attribute and event-based equivalents. "Champions" (high recency, high frequency, high value) becomes a Braze segment using last_purchase_date, total_purchase_count, and total_spent Custom Attributes with specific filter conditions. The lifecycle stage segmentation playbook is the right framework for this translation — it maps lifecycle stages to Braze's event-driven segment definitions.

What Transfers and What Doesn't

Transfers With Mapping ✅

User identity data. Identity attributes (email, phone, user ID) transfer via import. Map your CleverTap Identity to Braze's external_id.

Profile properties → Custom Attributes. CleverTap's user profile properties map to Braze Custom Attributes. Document every property in active use across campaigns, journeys, and segments.

Suppression data. Email unsubscribes, push opt-outs, and SMS opt-outs transfer — they move first. Email unsubscribes map to email_subscribe: unsubscribed. Push opt-in status re-establishes via SDK initialization.

Event history (with planning). CleverTap event history can be backfilled into Braze via the /users/track API. For teams where event history powers Canvas entry conditions or predictive models from day one, scope this backfill as a dedicated workstream.

Must Be Rebuilt 🔄

Every campaign and Journey becomes a Canvas. CleverTap's campaign and Journey builder has different logic than Braze's Canvas Flow. Every campaign — push, email, in-app, journey — must be rebuilt as a Braze Canvas. Begin with the Braze onboarding Canvas template for your highest-volume lifecycle Canvas.

RFM segments → Custom Attribute segments. CleverTap's computed RFM segments don't directly import into Braze. Translate them to Braze Custom Attribute filter conditions. This is an opportunity to refine your segmentation logic with more behavioral precision than RFM approximations allow. Use the RFM analysis guide as a reference for the mapping logic.

SDK instrumentation. The Braze SDK must be instrumented in your app to replace CleverTap's SDK. Every Custom Event in your Braze schema must be validated as firing correctly. This is core events and attributes architecture work.

Templates. CleverTap's personalization syntax is proprietary. Rebuild all templates in Braze's composer with Liquid personalization. Run the pre-send email QA checklist on every rebuilt template before Canvas activation.

Lost or Replaced ❎

CleverTap's built-in analytics. The analytics function CleverTap bundles moves to your dedicated analytics platform (Amplitude, Mixpanel, or your warehouse) via Braze Currents. Set up your retention metrics dashboard template before the first Canvas goes live.

CleverTap's AI Engine. CleverTap's AI Engine for send time optimization and segment prediction has Braze equivalents in Intelligent Timing and Predictive Churn/Purchases. Braze's predictive models require a calibration period of 30–60 days before producing reliable outputs.

Migration Checklist: CleverTap to Braze

Pre-Migration Audit

• Inventory all active campaigns and Journeys — channel, trigger type, entry volume, 30-day performance.
• Document all RFM segments and event-filter segments in active use — translate logic to Braze Custom Attribute conditions.
• Map CleverTap profile properties to Braze Custom Attribute data types.
• Map CleverTap event schema to Braze Custom Event schema — validate property depth and naming.
• Assess SDK release timeline for Braze SDK integration.

Data Migration

• Export email unsubscribes — import to Braze as email_subscribe: unsubscribed.
• Export push opt-outs — handle at device level via SDK initialization.
• Export SMS opt-outs — import to Braze SMS Subscription Groups.
• Export active users with all profile properties — map to Braze Custom Attributes.
• Segment import into engagement tiers before any Canvas is activated.
• Scope historical event backfill if predictive features or Canvas entry needs event history from day one.

Technical Setup

• Verify sending domain in Braze — DKIM, SPF, DMARC. Reference email deliverability channel health standards.
• Integrate Braze SDK — validate every Custom Event and property against schema.
• Configure APNs and FCM credentials in Braze.
• Configure Braze Subscription Groups for each channel.
• Set up Braze Currents for analytics platform and warehouse integration.
• Build Connected Content endpoints for any real-time personalization use cases.

Canvas Rebuild and Go-Live

• Rebuild RFM-based segments as Braze Custom Attribute segments.
• Rebuild all campaigns and Journeys as Braze Canvases — prioritize by engagement impact.
• Rebuild templates in Braze — rewrite personalization in Liquid.
• Run end-to-end Canvas QA before any Canvas goes live.
• Deactivate CleverTap campaigns as Braze Canvases go live.
• Execute email deliverability warm-up over 4–6 weeks.

Translating CleverTap's RFM Segments to Braze

CleverTap's RFM segmentation — Champions, Loyal Customers, Potential Loyalists, At Risk, Hibernating, Lost — is a valuable framework. In Braze, these don't exist as pre-built segment types; they must be defined explicitly using Custom Attribute conditions.

The translation approach: identify the Custom Attributes that proxy for Recency, Frequency, and Monetary value in your Braze schema, then define filter conditions for each tier. For example, "Champions" becomes: last_purchase_date is within 30 days AND total_purchase_count is greater than 5 AND total_revenue is greater than X. "At Risk" becomes: last_purchase_date is between 60 and 90 days ago AND total_purchase_count is greater than 2.

These conditions need to be maintained dynamically — Braze segments update in real time as Custom Attributes change, so the segments stay current without manual refresh. This is a meaningful operational advantage over CleverTap's scheduled RFM recalculation. The advantages of customer segmentation in lifecycle marketing are amplified when the segments are live and not batch-computed.

Stakeholder Expectations

Lifecycle team: Budget 10–14 weeks for a typical CleverTap migration with multiple channels and a complex Journey library. The RFM segment translation and Canvas rebuild are the primary time investments.

Engineering team: SDK migration requires a planned mobile app release. Budget 2–3 weeks of engineering time for SDK instrumentation and event validation. Connected Content endpoint development adds engineering scope if real-time personalization is in the immediate migration scope.

Analytics team: The CleverTap analytics function transitions to Currents and your dedicated analytics platform. Involve your analytics team in schema design from the start — the event naming established in Braze flows into your analytics tables via Currents. Our campaign analytics and performance insights service bridges the visibility gap during the transition.

Leadership: Set a post-migration baseline using the customer retention impact calculator before the migration starts. Brief leadership on the deliverability warm-up period before the first month shows a send volume reduction.

Why Propel for Your CleverTap to Braze Migration

Propel is a certified Braze partner with consumer app migration experience that includes the specific RFM-to-Braze segment translation, SDK migration coordination, and Connected Content API development that CleverTap migrations require. Our framework covers the full program — schema design, Canvas rebuild, analytics transition, and lifecycle strategy review.

Talk to a Propel operator about your CleverTap to Braze migration.