Migrate your MoEngage data

MoEngage Users are the core records carrying attributes, device data, and auxiliary data. We export all standard and custom user attributes (up to 100 columns per schema) via S3 or SFTP JSON flat files. Import respects the 600K user/hour and 14M user/day rate limits; we chunk large datasets accordingly.

Event data captures user actions and behavior in real time. We export all event types and their associated nested object properties via the Events export API or S3. The 100-attribute column limit per event applies during re-import.

Segments define audience filters based on user attributes and event behavior. Segment definitions are workspace-scoped. When migrating between MoEngage workspaces, we preserve segment logic; when migrating to a different platform, we translate filter criteria into equivalent targeting rules or static user lists.

Campaigns (all channels except In-app) can be migrated between MoEngage workspaces within the same data cluster. Cross-cluster migrations require rebuilding. We flag missing prerequisites like campaign tags, Content API references, or disabled channel integrations in the destination workspace.

Email, SMS, push, and WhatsApp templates carry personalization tokens and content blocks. Template HTML and variable mappings must be reviewed for compatibility with the destination platform's template syntax.

MoEngage allows up to 100 custom user attributes and 100 custom event attributes. Custom attribute names and data types must be mapped to destination equivalents. We export the full attribute schema alongside the data to ensure nothing is orphaned.

Product and item catalogs with custom schemas are managed via the Catalog API. We export catalog items and their attribute definitions in bulk JSON. Catalog IDs are preserved; items can be re-ingested via the POST Add Items endpoint in batches.

Device attributes (push tokens, OS version, app version) are exported as part of the User record. We preserve push token validity where possible but flag tokens that may be invalidated by re-platforming (iOS APNs tokens are device-specific).

Auxiliary data is supplementary user attribute data ingested from external sources. We export the data alongside standard user attributes and map it to the destination's equivalent enrichment mechanism.

MoEngage supports querying nested object attributes within events without flattening the schema. We export nested object data in its natural JSON structure. Destination platforms may require schema flattening; we document the tradeoff and apply the customer's preferred approach.

Campaign tags are workspace-scoped string labels. Tags that exist in the source workspace but not the destination appear as warnings during campaign import. We flag all unresolved tag references and provide a mapping table for manual resolution or bulk creation.

Content APIs fetch external data at campaign runtime (e.g., weather data for personalization). Campaigns referencing unavailable Content APIs fail import. We document all Content API dependencies and recommend pre-configuring equivalent connectors in the destination.

MoEngage workspaces are isolated data clusters. Users, events, segments, and campaigns are workspace-scoped. Cross-workspace migrations within the same cluster use MoEngage's native campaign migration feature; cross-cluster migrations require full data export and re-import.