Migrate from MoEngage to HubSpot

MoEngage user profiles map directly to HubSpot contacts. The user's email becomes the HubSpot contact email, and standard profile attributes (first name, last name, phone) map to their HubSpot equivalents. Custom user attributes migrate as HubSpot custom contact properties. Original MoEngage user creation timestamps are preserved as a custom datetime field since HubSpot's CreatedDate reflects the migration run date.

MoEngage stores user attributes as key-value pairs with type awareness (string, number, boolean, date). Each attribute becomes a HubSpot custom contact property. Multi-value attributes (arrays) require decision: store as pipe-delimited string or create a custom HubSpot multi-checkbox property. Date attributes preserve original timezone context as HubSpot datetime properties.

MoEngage behavioral events (page_view, purchase, app_open, campaign_click) are aggregated per user. We create a HubSpot contact activity log using the Notes/Activities timeline, and for high-signal events (purchase, subscription_change), we surface key event data as custom contact properties so lists and workflows can reference them. Event count summaries per category land as custom number properties.

MoEngage segments defined by behavioral rules (event frequency, attribute conditions, RFM scores) are documented in a segment mapping plan. Static segments with explicit user lists migrate as HubSpot static lists. Dynamic segments based on MoEngage behavioral rules cannot reproduce automatically — we document the segment logic so your HubSpot admin rebuilds them as HubSpot lists using HubSpot-captured properties and events.

MoEngage campaigns include targeting rules, A/B test configurations, channel settings, and performance metrics that have no direct HubSpot equivalent. We migrate campaign names and targeting audience lists as HubSpot campaigns with membership records. Campaign logic, A/B variants, and performance analytics must be rebuilt in HubSpot's campaign and email tools. MoEngage campaign performance history is preserved as a reference document.

MoEngage product catalog items (name, SKU, price, attributes) map to HubSpot product records. Product images, inventory counts, and custom attributes migrate as HubSpot product custom fields. The HubSpot product library associates with deal line items so your sales team can add products to deals directly.

If MoEngage holds company data linked to users (company name, industry, employee count, domain), those records migrate to HubSpot companies. The company-to-contact association resolves via the user's email domain or explicit company_id field. HubSpot's company hierarchy (parent/child) can be mapped if MoEngage's company structure includes parent references.

MoEngage custom objects (brands track subscriptions, warranties, or properties specific to their business) map to HubSpot custom objects. The mapping is 1:1 for schema. Associations that use MoEngage's N:N model need HubSpot association definitions set up in the HubSpot portal before migration — we include the association plan in the setup guide.

MoEngage captures push notification delivery, open, and click events as well as in-app message interactions and WhatsApp message events. These are MoEngage-specific engagement signals with no HubSpot equivalent in the CRM object model. We log them as HubSpot contact activities with a note describing the channel. Push and in-app opt-in status migrates as a custom contact property for segmentation reference.

MoEngage purchase events and order data link to users and catalog products. These translate to HubSpot deals with line items referencing HubSpot products. Order total, currency, and transaction timestamp migrate as deal custom fields since HubSpot deals have standard amount and close date fields. Multiple items per order create multiple deal line items associated with the same deal.

Subscription plan tiers (Bronze, Silver, Gold) and subscription status (active, churned, paused) tracked in MoEngage map to custom deal or contact properties in HubSpot. Subscription start date and renewal date migrate as custom datetime fields. Churn signals from MoEngage surface as lifecycle stage changes in HubSpot or deal closed-lost reasons.

MoEngage stores user import batch history, data quality flags, and deduplication logs. HubSpot has no equivalent import audit log at the contact level. We preserve the import history as a migration reference document, not as in-system records. Data quality flags from MoEngage (duplicate, invalid_email, merged) become HubSpot contact properties for follow-up cleanup.