Migrate from MoEngage to Freshsales

MoEngage User records map to Freshsales Contact. Standard attributes (email, first_name, last_name, phone, location) map to Freshsales Contact fields directly. Custom user attributes (MoEngage allows up to 100) migrate as Freshsales custom Contact fields, created before migration. The MoEngage user_id becomes the Freshsales unique_id for deduplication. Users without email addresses are flagged for manual review because Freshsales requires a unique identifier per contact.

MoEngage Company data attached to Users (company_name, company_domain, industry) migrates to Freshsales Account. If MoEngage Company records exist as standalone objects, they map 1:1 to Freshsales Account with company_domain as the dedupe key. Accounts are created before Contact import so that AccountId lookup is satisfied at Contact insert time.

MoEngage behavioral events (purchase, login, page_view, custom events) map to Freshsales Tasks representing activity history. Each event type becomes a Task with a distinct subject (e.g., 'Event: purchase_completed') and the event properties stored in custom Task fields or as JSON in a long-text field. Event timestamps migrate as Task ActivityDate. This is a lossy mapping: MoEngage's nested event object data flattens into task notes, and event-level user attributes do not carry forward unless explicitly mapped.

MoEngage behavioral segments (RFM-based, event-triggered, attribute-based) cannot migrate as live segments because Freshsales has no event-driven segmentation engine. We export segment definitions and membership lists as static Freshsales Lists. The customer's admin rebuilds active segments as Freshsales Filters using Freshsales's filter builder. Segment definitions are delivered in a written inventory for reference during rebuild.

MoEngage campaigns (email, SMS, push, WhatsApp) have no direct Freshsales equivalent. Freshsales Workflows handle CRM actions (create task, update field, send email alert) but not outbound marketing campaigns. We do not migrate campaigns as functional objects. We deliver a written inventory of every MoEngage campaign with channel, audience definition, content summary, and scheduling logic for the customer's admin to rebuild in Freshsales or a dedicated marketing automation tool.

MoEngage custom user attributes (up to 100) migrate to Freshsales Contact custom fields. We create each custom field in Freshsales with the corresponding data type (text, number, date, dropdown) before record import. Attribute names are preserved as field labels with API-safe field names. Attribute values migrate as field values on the Contact record. Attributes exceeding Freshsales field limits (255 characters for text) are truncated with a warning in the migration report.

MoEngage device data (OS, OS version, app version, device model, push token, device_id) migrates to Freshsales Contact custom fields. Push tokens are informational only in Freshsales; they do not enable push delivery because Freshsales has no push channel. We preserve token age and device metadata for audit purposes and document that a new push registration flow is required post-migration if push delivery continues through a separate platform.

MoEngage product catalogs with custom schemas migrate as Freshsales Products if the customer uses Freshsales deal management. Catalog item attributes map to Product custom fields. Catalog-level schema (categories, pricing tiers, relationships) is delivered as a written data dictionary for the admin to configure manually in Freshsales Products. Native MoEngage catalog features (recommendations, dynamic pricing) do not transfer and require rebuild or a separate catalog management tool.