Migrate from Netmera to monday CRM

Netmera user profiles map to Monday.com CRM Contacts. We export users via segment-based extraction (Netmera's bulk export method), preserving all standard profile fields (email, name, phone, custom attributes). The user's primary email address is the dedupe key during Monday.com CRM Contact import. Netmera user IDs are preserved in a custom field netmera_user_id__c for cross-reference during reconciliation. Note that Netmera push tokens, device bindings, and SDK-specific identifiers do not map to any Monday.com CRM field and are not imported; they are documented for the customer's mobile team to regenerate post-migration.

If the customer uses Netmera's Company/Organization object (Enterprise tier), we map it to Monday.com CRM Company. Organization name, domain, industry, employee count, and custom fields migrate to the equivalent Company fields. Companies must import before Contacts so that the Contact-Company link is satisfied at insert time. Companies without a mapped organization in Netmera are created as standalone Contacts on the primary board.

Netmera segments define dynamic audience rules and serve as both targeting units and the primary export mechanism. Monday.com CRM has no dynamic segment engine; instead, we document each Netmera segment's rule logic (attribute conditions, event conditions, combined logic) and translate it into a Monday.com CRM View with column filters that recreate the same audience subset on the Contact board. Static segment membership (snapshot lists) migrate as Tags on the Contact records. Dynamic segments require the customer to define which View replaces each segment post-migration.

Netmera campaign records (name, content, channel, schedule, performance metrics) migrate to Monday.com CRM as linked board items on an optional Campaigns board with custom columns for channel, send date, open rate, click rate, and conversion count. We migrate campaign metadata and content blocks; creative assets (images under 1MB, video under 12MB per Netmera FAQ) export as files for manual re-upload. Campaign delivery schedules and A/B test configurations do not migrate because Monday.com CRM has no native campaign scheduling or A/B testing for outreach.

Netmera Journey flows define multi-step user-entry rules and channel steps with conversion event counting. Monday.com automations use when/then triggers on board items and do not have a native journey equivalent. We document each Journey's entry condition, step sequence, channel actions, and conversion event definition in a written handoff sheet for the customer's admin to rebuild as Monday.com board automations. Note that Netmera counts one conversion per user per journey; Monday.com counting is event-occurrence-based. This KPI definition difference is documented in the handoff so the admin does not misinterpret funnel performance post-migration.

Netmera custom profile attributes store user-level data beyond defaults (string, number, boolean, date types). We migrate attribute names and values to Monday.com CRM custom fields on the Contact object. Monday.com's custom field types (text, number, date, location, link, dropdown, multi-select) cover the most common attribute types. Complex nested attribute structures or arrays require flattening into multiple fields. Attribute type mapping is validated during the sandbox migration pass.

Netmera device records (OS, app version, push token, device model) migrate as custom fields on the Monday.com CRM Contact. Push token values are imported as a text field (netmera_push_token__c) purely for audit reference; the values are non-functional in Monday.com and will not deliver notifications. The customer's mobile team must regenerate tokens under their own APNs/FCM configuration post-migration. We flag this explicitly in the migration report so push re-opt-in is planned.

Netmera SDK-tracked behavioral events (page views, custom actions, trigger events) are mapped as Activity Log entries on the corresponding Monday.com CRM Contact item. Event names and key properties migrate to text fields or tag fields. High-volume event histories may be selectively migrated (last 90 days or last 12 events per user) depending on the customer's reporting needs, because Monday.com CRM is not designed as an event analytics platform. We agree on an event scope during scoping.

Netmera tags are user-level labels used for segmentation and organization. Tags migrate as Monday.com CRM Contact tags, preserving the tag name and the user association. Monday.com CRM does not support tag hierarchies or tag-based automation triggers; if the customer's Netmera implementation relies on multi-level tag taxonomies, we document the hierarchy for manual reorganization in Monday.com.

Netmera widgets are visual engagement assets with rendering tied to the Netmera SDK. Widget designs and content export as file assets and text assets for reference, but the widget rendering engine is platform-specific and not portable. Monday.com does not have an equivalent in-app message or tooltip system. We deliver a written widget inventory with screenshots and content so the customer's design team can rebuild critical widgets as Monday.com doc embeds, image files, or integrations with dedicated in-app messaging tools (Intercom, Chameleon, Appcues) if needed.