Migrate from MoEngage to Microsoft Dynamics 365 Sales

MoEngage Users map to Microsoft Dynamics 365 Sales Contact records for identified customers, and to Lead records for prospects. We use the user attributes to resolve the split: users with a defined account relationship or purchase history map to Contact attached to an Account; users with no account linkage map to Lead. All standard and custom user attributes (up to 100 columns) migrate to Contact custom fields (prefixed moe_) or Lead custom fields. Device push token metadata migrates to Contact fields for re-registration documentation.

MoEngage behavioral events (page views, purchases, cart actions, custom actions) have no direct Microsoft Dynamics 365 Sales equivalent because Dynamics is a relationship CRM, not a behavioral analytics platform. We flatten nested event attributes into a structured Note record attached to the Contact or Lead, and optionally create custom Task records with event type, timestamp, and key properties preserved. High-frequency event streams (thousands per user) are summarized into aggregated engagement scores rather than individual records to avoid record volume inflation in Dynamics.

MoEngage RFM and behavioral segments define audience filters that cannot be translated directly into Microsoft Dynamics 365 Sales because the platform lacks a real-time behavioral segmentation engine. We document the segment logic (filter criteria, attribute conditions, event thresholds) and map each segment to either a static Marketing List in Microsoft Dynamics 365 Sales (for a point-in-time export) or a Dynamic Marketing List based on the equivalent Dataverse query. Advanced segmentation rebuilds inside Customer Insights if the customer licenses that module.

MoEngage campaign definitions (name, channel assignment, targeting audience, schedule, and content references) are workspace-scoped and cannot migrate as live campaigns into Microsoft Dynamics 365 Sales . We extract the campaign metadata via MoEngage API, document the channel, targeting logic, and content references in a campaign inventory, and recreate Campaign records in Microsoft Dynamics 365 Sales with the campaign name and objective. The customer's admin rebuilds the delivery logic inside Dynamics marketing features or Power Automate. MoEngage In-app campaigns cannot be migrated at all and are flagged for complete rebuild.

MoEngage product catalogs with custom schemas map to Microsoft Dynamics 365 Sales Product2 records with extended custom fields capturing the catalog attribute data. If the MoEngage catalog uses nested object structures or multiple price tiers per item, we flatten these into Product2 custom fields and create associated PricebookEntry records for each applicable price list. We preserve the original catalog_id for reference reconciliation.

MoEngage custom user attributes (up to 100 per user schema) map to custom fields on Contact and Lead in Microsoft Dynamics 365 Sales . We create the destination schema in Dataverse before migration, using field types that best match the MoEngage data type (string to Text, number to Decimal or Whole Number, date to Date, boolean to Two Options). Attribute names are normalized to lowercase with underscores for Dataverse compatibility and prefixed with moe_ to avoid naming conflicts with existing fields.

MoEngage email, SMS, push, and WhatsApp templates carry personalization tokens and HTML content blocks. Template content migrates as an exported HTML document stored as a Note attached to the relevant Campaign record. Personalization tokens are documented with their MoEngage variable names for manual remapping into Dynamics Email Templates or Power Automate expressions. Full template rebuild inside Dynamics is recommended because template engine variable syntax differs between platforms.

Device attributes (OS version, app version, push token age, FCM/APNs token strings) export from MoEngage as user auxiliary data. We preserve this data in Contact custom fields (device_os__c, app_version__c, token_age_days__c) for documentation and re-engagement planning. The FCM and APNs token strings themselves do not function in Microsoft Dynamics 365 Sales because they are bound to the originating MoEngage app configuration. A push delivery gap of 7-14 days is expected post-migration as the app re-registers tokens against the new platform on next user open.

MoEngage auxiliary data ingested from external sources (loyalty data, preference center data, third-party enrichment) migrates alongside standard user attributes. We map each auxiliary data field to an equivalent Contact or Account custom field. For highly structured auxiliary data with multiple nested fields, we create a Dataverse custom entity with a 1:N relationship to Contact, preserving the natural structure of the source data.