MoEngage to Salesforce migration
We migrate Users, Events, Segments, and device data from MoEngage into Salesforce with behavioral attributes preserved as custom Contact fields, event history mapped to the Task and Event activity timeline, and every push token exported with its device metadata so your destination platform can attempt re-registration at next app open.
FlitStack AI migrates contacts, task and events, campaign and campaignmembers, product2s, emailtemplate and salesforce files from MoEngage to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from MoEngage to Salesforce?
Moving from MoEngage to Salesforce is a cross-category migration: MoEngage is an AI-native customer engagement platform organized around Users, behavioral Events, Segments, and Campaigns across 11 channels; Salesforce is a CRM organized around Leads, Contacts, Accounts, and Opportunities with an activity timeline.
Read the full summary
We resolve the structural mismatch by mapping MoEngage Users to Salesforce Contacts with custom attributes carrying behavioral and RFM data, mapping MoEngage Events to Salesforce Task and Event records, and preserving the segment membership logic as Salesforce Campaign membership or custom multi-select fields. Push tokens, device metadata, and product catalog data are exported as auxiliary fields and documented for the destination push configuration team. We do not migrate Campaigns, automation logic, or content templates as code; we deliver a written inventory of every campaign, Content API reference, and template dependency requiring rebuild in Salesforce.
Users → Contact
MoEngage User records map to Salesforce Contact with the user_id field preserved as an external ID for deduplication.
How it maps
All standard attributes (email, first_name, last_name, phone) map directly. Custom user attributes (up to 100 per MoEngage schema) map to Salesforce custom Contact fields with __c suffix. Behavioral attributes (RFM scores, last purchase date, lifetime value proxies) are preserved as typed custom fields (Date, Number, Currency, Picklist) so they are available for reporting without requiring Data Cloud. The MoEngage customer_id becomes a custom external ID field moengage_id__c for reconciliation.
Users (Auxiliary Data) → Contact (Custom Fields)
MoEngage auxiliary data ingested from external sources (Shopify, Snowflake, AWS S3 integrations) is exported as additional user attributes and mapped to Salesforce custom fields of equivalent type.
How it maps
Auxiliary data that represents enrichment signals (loyalty tier, preference center data, subscription status) becomes Salesforce custom fields. Any auxiliary data that represents external transaction history is documented separately as a data dictionary for the customer to connect via Salesforce Data Cloud or a native integration.
Device Data → Contact (Device Fields)
MoEngage device data (push tokens, OS version, app version, device manufacturer, device model, OS build) is exported as auxiliary fields on the User record.
How it maps
We map these to Salesforce Contact custom fields (mobile_push_token__c, device_os__c, device_os_version__c, device_app_version__c, device_manufacturer__c). We document clearly that iOS APNs tokens and Android FCM tokens are invalidated on platform switch and require re-registration via the destination push SDK. A push token health report is delivered at cutover showing token age, OS distribution, and expected re-registration rates.
Events → Task and Event
MoEngage event streams (user actions, behavioral triggers, channel interactions) map to Salesforce Task records with event type preserved as TaskType or a custom event_type__c field.
How it maps
High-frequency events (page views, screen opens, heartbeat events) are mapped to Task records at reduced fidelity (one Task per event type per user per day) to avoid Salesforce activity record explosion. Significant events (purchase, cart abandonment, subscription change, campaign click) map 1:1 as individual Task records. The MoEngage event timestamp maps to Task ActivityDate for timeline ordering.
Segments → Campaign and CampaignMember
MoEngage segment definitions (audience filters based on user attributes and event behavior) are too complex to migrate as automated criteria.
How it maps
We export the segment membership snapshot at migration time and create a Salesforce Campaign for each MoEngage segment, with the membership as CampaignMember records linked to the corresponding Contacts. The segment logic (filter criteria, RFM thresholds, behavioral rules) is documented in a segment inventory report for the customer to recreate in Salesforce Reports, Data Cloud, or a third-party segmentation tool post-migration.
Catalogs → Product2
MoEngage product catalogs with custom schemas (item attributes, pricing, inventory, images) are exported as catalog JSON and mapped to Salesforce Product2 records with custom fields for catalog-specific attributes.
How it maps
The catalog_id is preserved as a custom external ID on Product2. Product catalog images and URLs are stored as URLs on the Product2 record or in Salesforce Files linked to the product. Pricebooks are created from MoEngage pricing tiers. If the MoEngage catalog serves non-product purposes (e.g., loyalty rewards catalog), we document the catalog schema and recommend a Salesforce custom object or Salesforce Order Management System approach.
- UsersContact1:1
- UsersContact1:1
- Device DataContact1:1
- EventsTask and Event1:1
- SegmentsCampaign and CampaignMember1:1
- CatalogsProduct21:1
+ 6 more in the mapping below
How MoEngage and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | MoEngage | Salesforce |
|---|---|---|
| Platform type | AI-native customer engagement and behavioral analytics platform | CRM with sales, service, and marketing clouds |
| Core record model | Users with behavioral attributes, events, and segment membership | Leads and Contacts attached to Accounts with activity history |
| Campaign and automation model | Multi-channel Campaigns with AI optimization and behavioral triggers | Salesforce Flow (record-triggered, scheduled, screen) and Salesforce Campaign objects for list management |
| Behavioral data handling | RFM segmentation, event streams, and AI predictions as native platform features | No native RFM or behavioral scoring; requires Data Cloud, third-party tools, or custom fields |
| Push notification infrastructure | Native APNs and FCM token management with 11 channel orchestration | Salesforce MobilePush or custom MCP via REST API with separate token registration |
| Product catalog | Native product catalog API with custom schemas and item attributes | Product2 with Pricebook2; no native catalog API for non-product items |
| Pricing model | Custom-negotiated enterprise pricing based on MAU or message volume | Per-user licensing with edition tiers ($25-$330/user/mo) |
| Data export method | S3 or SFTP via Streams add-on with hourly rate limits (600K users, 5M events) | Salesforce REST API, Bulk API 2.0, or Data Loader with chunking and backoff |
What to watch for in a MoEngage to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Push tokens are invalidated on platform switch regardless of destination
iOS APNs tokens and Android FCM tokens are device-specific credentials issued by Apple and Google respectively.
How we handle it
When migrating to any new engagement platform, including Salesforce MobilePush, these tokens must be re-registered by the app on the user's next open. We export all device metadata (token age, OS version, app version, device manufacturer, device model) and deliver a push token health report at cutover showing the token age distribution, OS breakdown, and expected re-registration rate based on typical app re-engagement cycles. We clearly document that a silent drop in push delivery is expected for the first 7-14 days post-migration. The customer's mobile developer integrates the Salesforce MobilePush SDK before cutover to begin token re-registration.
MoEngage Campaigns and automation logic do not migrate to Salesforce Flow
MoEngage campaigns (email, SMS, push, WhatsApp, in-app) are multi-channel automation constructs with AI-powered optimization, behavioral triggers, and channel orchestration.
How we handle it
Salesforce Flow is a record-triggered, scheduled, and screen flow automation model with different trigger semantics, action types, and limits. There is no automated migration path for campaigns. We deliver a written inventory of every MoEngage campaign with its trigger conditions, channel actions, audience criteria, AI optimization settings, and Content API dependencies. The customer's admin or a Salesforce partner rebuilds campaigns in Salesforce Flow (for CRM-triggered automations) or Salesforce Marketing Cloud Journey Builder (for cross-channel engagement) post-migration. Content templates are delivered as HTML/text files in the template inventory for manual re-creation.
MoEngage RFM and AI predictions have no Salesforce native equivalent
MoEngage Sherpa AI generates behavioral predictions (churn probability, purchase likelihood, best-time-to-send, next-best-action recommendations) and RFM segmentation (Recency, Frequency, Monetary) as platform-native features.
How we handle it
Salesforce Sales Cloud has no native AI prediction or RFM scoring engine without Data Cloud add-ons or third-party tools. We preserve RFM scores and AI prediction values as custom Number fields on the Contact record at migration time, maintaining the last-known scores from MoEngage. The customer should plan to connect Salesforce Data Cloud or a third-party CDSP (e.g., Dynamic Yield, Braze, Optimove) to generate updated scores post-migration. We document the MoEngage RFM methodology and score distribution for any vendor evaluation.
MoEngage workspace isolation prevents cross-cluster campaign migration
MoEngage campaigns (except In-app) migrate natively only between workspaces within the same data cluster.
How we handle it
Cross-cluster migrations are not supported by any native MoEngage tool. All campaign definitions, templates, and segment logic must be manually rebuilt or reconstructed via the REST API. We extract all campaign metadata, trigger conditions, audience filters, and content references via the API and deliver them in a campaign inventory document. The rebuild effort depends on campaign count and complexity; a team with 50 campaigns across 5 channels should plan 3-6 weeks of admin rebuild time post-migration.
MoEngage S3 exports require the Streams add-on to be enabled
S3 Exports via the MoEngage Streams add-on are the preferred method for high-volume user and event data extraction (up to 600K users/hr and 5M events/hr).
How we handle it
Manual API exports via the Events export API are rate-limited and slower. Customers without the Streams add-on must contact their CSM to enable it before migration export begins. We verify Streams add-on status during discovery and escalate to CSM enablement as a prerequisite before any export timeline begins. Without Streams, we rely on the REST API export with lower throughput and larger file splitting requirements.
How the migration runs
Discovery and add-on verification
We audit the source MoEngage workspace across user volume, event history depth, custom attribute schemas, segment count, campaign count, catalog structures, push token volume, and workspace count.
What this step covers
We verify Streams add-on status (required for S3 export) and confirm the MoEngage API credentials have sufficient scope for data extraction. We review the destination Salesforce org for existing Contact schema, custom field limits, and Data Cloud availability. The discovery output is a written migration scope with object-level row counts, a custom attribute data dictionary, and a segment inventory preview.
Schema design and Salesforce custom field provisioning
We design the destination schema in Salesforce.
What this step covers
This includes creating custom fields on Contact for all MoEngage user attributes (behavioral, RFM, auxiliary, device metadata), custom fields on Task for event type and event payload, custom fields on Product2 for catalog attributes, and custom fields on Campaign for tag taxonomy. Each MoEngage attribute is typed to a Salesforce field type. If MoEngage custom attributes exceed Salesforce's per-object limit (800 custom fields per object), we prioritize business-critical attributes and document overflow attributes for a second-phase or Data Cloud migration. Schema is deployed to a Salesforce Sandbox via metadata API for validation before production migration.
Data export via S3 or SFTP
We initiate MoEngage user export via S3 (if Streams add-on is enabled) with file splitting to respect MoEngage's 1M row per file and 200MB per file guardrails.
What this step covers
Event exports are split by event type and time window to stay within the 5M events/hr rate limit. For catalogs, we use the Catalog API to export all items and attribute definitions in bulk JSON. We export segment membership snapshots as CSV with Contact ID, segment name, and membership date. All exports run off-peak to minimize rate limit pressure. Each export produces a row-count manifest for reconciliation.
Data transformation and attribute mapping
We transform the MoEngage export data into Salesforce-compatible CSV format.
What this step covers
This includes: splitting the single Contact record from MoEngage into Salesforce Lead or Contact based on any lifecycle data (or defaulting all to Contact with a moengage_lifecycle__c field if no lifecycle data is present), flattening nested event JSON into the event_payload__c field on Task, mapping MoEngage customer_id to the moengage_id__c external ID field, mapping push tokens to mobile_push_token__c, and mapping RFM scores to custom Number fields. Segment membership maps to CampaignMember records with status populated from the MoEngage membership snapshot.
Salesforce bulk ingestion via Bulk API 2.0
We ingest data into Salesforce in dependency order: Product2 (if catalog migration is in scope), Contact with external ID deduplication, Task records with WhoId (Contact) and ActivityDate resolved, Campaign with tag taxonomy applied, and CampaignMember linking Contacts to Campaigns.
What this step covers
Large event history (over 500,000 Task records) uses the Salesforce Bulk API 2.0 with batch chunking, exponential backoff on rate limit responses, and parent-record lookup resolution. We coordinate with the customer's Salesforce admin to temporarily bypass validation rules and field-level security for the migration user. Push token re-registration begins after the Contact import is complete and the Salesforce MobilePush SDK is integrated by the customer's mobile developer.
Cutover, validation, and campaign rebuild handoff
We freeze MoEngage writes during the cutover window, run a final delta migration of any records modified during the migration, then enable Salesforce as the system of record for the migrated scope.
What this step covers
We deliver: the campaign inventory document (every campaign with trigger, audience, channel, AI settings, and Content API dependencies), the template inventory (HTML/text files with personalization variable mapping), the segment inventory (criteria definitions for manual rebuild), the Content API dependency report, and the push token health report with re-registration status. We support a one-week hypercare window for reconciliation issues. We do not rebuild MoEngage campaigns as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with user record volume, event history depth, custom attribute count, and segment complexity. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for MoEngage to Salesforce →Why teams move from MoEngage to Salesforce
- Teams consolidate engagement and CRM data into a single platform to eliminate sync overhead and the risk of divergent customer views. MoEngage's native Salesforce CRM integration (available via the Streams add-on) sends campaign interaction data to Salesforce as Activities, but that bidirectional sync is a point-to-point bridge rather than a unified record model. Reviewers on Gartner Peer Insights and G2 cite the desire for a single source of truth as a driver to consolidate onto Salesforce when the organization has already standardized on Salesforce for sales and service.
- Salesforce's AppExchange ecosystem offers over 9,000 certified integrations versus the point-solution integrations available for MoEngage. Enterprise teams requiring native ERP connectors (SAP, Oracle, NetSuite), contract lifecycle management (DocuSign CLM, Conga), or revenue intelligence (Clari, Gong) move to Salesforce because those integrations exist as AppExchange listings rather than custom webhook routes. The integration depth and vendor stability of AppExchange-certified apps is cited in enterprise evaluation guides as a key differentiator.
- MoEngage's steep learning curve and complexity in managing segments and AI features extends onboarding timelines beyond 60 days according to reviews. Teams with non-technical marketers or limited platform admin capacity find Salesforce's more familiar CRM paradigm (Leads, Contacts, Opportunities, Tasks) faster to onboard to. The AI and RFM capabilities that MoEngage offers as native features become available in Salesforce via Data Cloud add-ons or third-party tools, trading platform complexity for integration complexity.
- MoEngage operates on custom-negotiated enterprise pricing with no public tiers, which creates TCO uncertainty during annual budget cycles. Salesforce's tiered per-user model (Essential at $25/user, Professional at $80/user, Enterprise at $165/user) is more predictable for finance and procurement teams that need to forecast seat costs 12-18 months ahead. Mid-market teams with predictable headcount cite this pricing transparency as a driver to consolidate onto Salesforce.
- Compatibility issues between MoEngage and other platforms in the stack result in low efficiency, poor connectivity, and lack of visibility into data flows between channels according to MoEngage's own comparison content. Teams running MoEngage alongside Salesforce as a two-system architecture report data lag, duplicate records, and conflicting customer views. Consolidating onto Salesforce removes the bridge-sync dependency and aligns the customer record with the system of record for sales, service, and analytics.
Questions, answered
MoEngage to Salesforce migration questions
How long does a MoEngage to Salesforce migration take?
Most migrations land between three and five weeks for accounts under 50,000 Users with clean attribute schemas and no catalog migration. Migrations with large event histories (over 1 million event records), complex RFM attribute schemas, product catalog data, or multiple MoEngage workspaces consolidating into one Salesforce org move to eight to twelve weeks because of Bulk API time, nested object flattening, catalog reconstruction planning, and cross-cluster deduplication.
Do MoEngage Campaigns, automation logic, and AI features migrate to Salesforce?
No. MoEngage campaigns (email, SMS, push, WhatsApp, in-app, RCS) and Sherpa AI features (path optimizer, best-time-to-send, next-best-action, predictions) do not migrate to Salesforce as code. We do not migrate them. We deliver a written campaign inventory with every trigger, audience criteria, channel action, AI setting, and Content API dependency, plus an HTML/text template inventory for manual re-creation. The customer's admin or a Salesforce partner rebuilds campaigns in Salesforce Flow (for CRM-triggered automations) or Salesforce Marketing Cloud Journey Builder (for cross-channel engagement). RFM scores and AI predictions are preserved as static custom fields at migration time but require a replacement scoring engine post-migration.
What happens to push notifications during the migration?
Push token invalidation is unavoidable when switching engagement platforms. iOS APNs tokens and Android FCM tokens are device credentials issued by Apple and Google; they are bound to the issuing platform's project and are not portable to any new platform including Salesforce MobilePush. We export all device metadata (token age, OS version, app version) and deliver a push token health report at cutover. After the Salesforce MobilePush SDK is integrated and deployed by your mobile developer, users who open the app will re-register tokens. Expect a 7-14 day silent drop in push delivery as tokens re-register. We provide a notification copy template for an in-app message announcing the platform migration to drive re-engagement and token re-registration.
Can we migrate MoEngage product catalogs to Salesforce?
Yes, with caveats. MoEngage product catalogs with custom schemas export as JSON via the Catalog API. We map catalog items to Salesforce Product2 records with custom fields for catalog-specific attributes (color, size, brand, image URLs). If the MoEngage catalog serves a non-product purpose (loyalty rewards catalog, service catalog), we recommend a Salesforce custom object or Salesforce Order Management System rather than Product2. We do not migrate catalog display logic, recommendation algorithms, or MoEngage-specific catalog optimization features. The catalog reconstruction plan is delivered as part of the migration scope for the customer's admin to implement.
How do we preserve MoEngage RFM scores and behavioral segmentation in Salesforce?
MoEngage RFM scores and behavioral segmentation criteria are preserved as static values in Salesforce custom fields at migration time. The RFM score distribution (Recency, Frequency, Monetary bins) is documented in the data dictionary. Sherpa AI predictions (churn probability, purchase likelihood) are preserved as custom Number fields on Contact. These static values represent the last-known scores from MoEngage. For ongoing scoring, the customer needs to implement a replacement engine: Salesforce Data Cloud (with Predictive Studio or a custom model), a third-party CDSP (Braze, Dynamic Yield, Optimove), or a custom Salesforce Flow scoring model. We provide the MoEngage scoring methodology documentation to support vendor evaluation.
What about MoEngage Workspaces and cross-cluster migrations?
If the migration involves consolidating multiple MoEngage workspaces into a single Salesforce org, we deduplicate user records by customer_id across sources, reconcile segment membership from all workspaces, and combine workspace-level tag taxonomies into a unified structure. Cross-cluster campaign migration is not supported natively; we deliver the campaign inventory from each workspace separately and document the consolidation context. This multi-workspace scenario adds two to three weeks to the migration timeline and requires explicit deduplication rules and tag taxonomy decisions from the customer before any data loads begin.
Do we lose segment membership history during migration?
We preserve the segment membership snapshot at migration time as Salesforce CampaignMember records. Each MoEngage segment becomes a Salesforce Campaign, and each Contact's membership in that segment becomes a CampaignMember record with the membership date and status. However, the dynamic segment criteria (the behavioral rules that determined membership) do not migrate because they cannot be expressed as Salesforce filter logic. We deliver a segment inventory document listing each MoEngage segment's criteria, membership size, and the recommended Salesforce equivalent (a static Campaign, a Salesforce Report with filters, a Data Cloud segment, or a third-party tool). The customer's admin rebuilds the dynamic criteria post-migration.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Jobnimbus to SalesforceMapping · history · rollbackSysteme IO to SalesforceMapping · history · rollbackBigin by Zoho CRM to SalesforceMapping · history · rollbackIterable to SalesforceMapping · history · rollbackKeap to SalesforceMapping · history · rollbackWise Agent to SalesforceMapping · history · rollback MoEngage to HubSpotMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from MoEngage to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote