Migrate from Netmera to Freshsales

Netmera Users map to Freshsales Contacts. The primary identifier is email; we use email as the dedupe key during import. Profile attributes (custom properties stored on the user) are mapped to Freshsales custom fields that we pre-create under Contacts before migration. Standard Netmera fields (user_id, first_name, last_name, email, phone, country) map to Freshsales standard fields. Device bindings and push token data do not transfer and are documented separately in the migration inventory.

Netmera segments define audience rules for targeting and export scoping. We map segment membership to Freshsales Contact tags (using the Tags object) or to a multi-select picklist custom field on Contact, depending on the customer's preference for taxonomy versus simple label storage. Segment membership criteria are documented as a written reference for the customer's admin to configure Freshsales Workflow filters if behavioral segmentation is needed post-migration.

Netmera campaign records (name, content, scheduling, performance metrics) map to Freshsales Deals with historical campaign performance stored as custom fields on the Deal. Campaign content blocks are migrated as Deal description fields or attachments. We do not migrate campaign creative assets (images, video) as executable code; we deliver a written inventory of each campaign's creative assets for the admin to rebuild in Freshsales.

Custom profile attributes from Netmera are mapped to Freshsales custom fields. We match attribute types (string, number, boolean, date) to equivalent Freshsales field types. Multi-value attributes (arrays) are stored as text or multi-select picklist depending on the attribute structure. All custom fields are pre-created in Freshsales before user migration begins. Netmera's default profile attributes (email, phone, country) map to Freshsales standard Contact fields.

Netmera device records bind users to physical devices and carry OS type, OS version, device model, and push token. We export device metadata (OS, version, model) as custom fields on the Freshsales Contact record. Push tokens themselves are not migrated because they are bound to Netmera's APNs and FCM credentials and become invalid in any new engagement platform. We document this in the migration inventory and recommend a re-opt-in or silent token refresh campaign post-migration.

Netmera behavioral events (page views, custom actions, SDK-tracked triggers) are mapped to Freshsales activity records on the Contact timeline. High-value events (conversion events, purchase events) are stored as custom fields or tags on the Contact for segmentation in Freshsales. We map event names and property keys; property value normalization may be required for date formats and numeric precision. Event schemas vary by Netmera implementation, so we validate a sample of event records before bulk migration.

Netmera Journey Orchestration flows define multi-step user-entry rules and channel steps. We map the entry conditions, step sequence, and conversion event definitions as a written inventory document for the customer to rebuild in Freshsales Workflows. Note that Netmera's Journey Analytics counts one conversion per user per journey, not per occurrence, which affects funnel metrics post-migration. We document this discrepancy in the inventory so the admin can align KPI definitions in Freshsales reporting.

Netmera tags are label-based metadata on user records. We map tag names and associations to Freshsales Contact tags. Tagless data capture is a Netmera platform feature meaning some user data may arrive without any tag, which we note in the data audit. We do not create Freshsales tag taxonomy; we preserve tag names as-is and deliver a tag usage report as part of the migration inventory.