Migrate from MoEngage to monday CRM

MoEngage Users map to Monday.com Contacts with custom fields carrying MoEngage custom user attributes. We export all standard (first_name, last_name, email, phone) and custom attributes (up to 100 per user) from MoEngage's S3 or SFTP export and create corresponding Monday.com text, number, date, or dropdown columns on the Contacts board. MoEngage's user_id becomes a read-only Monday.com column for cross-system reference. Email address is the primary dedupe key during import.

MoEngage device data (OS version, app version, push token metadata) is exported as part of the User record. Push tokens (iOS APNs, Android FCM) cannot be re-registered on Monday.com CRM because Monday.com has no native push delivery capability. We export the device metadata (OS, app version, token age) as informational custom fields on the Contact record so the customer's app team can determine re-engagement strategy, but active push delivery is not restored by migration.

MoEngage event streams (purchase, page_view, session_start, and custom event types) do not have a native equivalent in Monday.com CRM's data model. Monday.com does not store behavioral event history as a queryable object. We export the event schema (event names, property names, property types) and deliver it as a written inventory for the customer's data team to load into a BI tool (Metabase, Looker, or a data warehouse) if behavioral analysis is needed post-migration. A subset of high-value events (e.g., last_purchase_date, subscription_status) can be written as date or status custom fields on the Contact record.

MoEngage segment definitions (audience filters based on user attributes and event behavior) are workspace-scoped. We extract all segment logic including filter conditions, combination rules, and time-based criteria. Monday.com CRM does not support saved dynamic segment queries equivalent to MoEngage's behavioral segmentation. Segments requiring event-based conditions cannot migrate automatically. We deliver a written segment inventory with each segment's logic, audience size, and recommended Monday.com Board filter or Group configuration for the customer to rebuild manually.

MoEngage campaign definitions (all channels except in-app) carry content templates, personalization tokens, delivery schedules, and channel configurations. Monday.com CRM has no campaign execution capability. We extract all campaign metadata (name, channel, status, content references, tag dependencies) and deliver it as a written inventory for the customer's marketing team to rebuild in their chosen marketing automation tool post-migration. Missing MoEngage campaign tags are flagged as warnings in the gap report.

MoEngage email, SMS, push, and WhatsApp templates carry personalization tokens and content blocks. Template HTML and variable mappings are documented in the gap report. Monday.com CRM has no native templating engine for outbound communications. Templates requiring migration must be rebuilt in the customer's chosen email marketing or sales engagement tool.

MoEngage product catalogs with custom schemas map to Monday.com boards where each catalog item becomes a board Item. Catalog attribute definitions (product name, SKU, price, custom fields) map to Monday.com columns of equivalent types. Catalogued product relationships (categories, tags) map to Monday.com groups or dropdown columns. If the MoEngage catalog contains nested objects (e.g., variants within a product), these are flattened to individual Items or written as linked board Items.

MoEngage auxiliary data (external enrichment sources ingested as supplementary user attributes) is exported alongside standard user attributes. Each auxiliary data field is mapped to a Monday.com custom field on the Contact record. The enrichment source reference is preserved in a text field for audit purposes.

MoEngage allows up to 100 custom user attributes and 100 custom event attributes. Custom attribute names and data types are mapped to Monday.com column types: text attributes to Text columns, numeric to Number columns, dates to Date columns, boolean to Checkbox columns, and enumerated values to Dropdown or Status columns. We export the full attribute schema during discovery so that destination column creation happens before record import begins.

MoEngage campaign tags are workspace-scoped string labels used to categorize campaigns. Tags that exist in the source workspace but not the destination appear as warnings during campaign documentation. We flag all tag references in the campaign inventory and note that tag-based reporting must be rebuilt as Monday.com board labels or tag columns.