Migrate from Netmera to Nutshell

Netmera User profiles map to Nutshell Person records when the profile represents a known sales contact. Netmera Users without identifiable company affiliation or with anonymous SDK-tracked behavior map to Nutshell Lead records. We use Netmera profile attributes (email, phone, company name) as the dedupe key at import time. The original Netmera userId is preserved in a custom field netmera_user_id__c for audit and cross-reference.

Netmera custom profile attributes (string, number, boolean, date types) map to Nutshell custom fields on the Person and Lead objects. We define the field type in Nutshell to match the Netmera attribute type before import. Attribute names are preserved as field labels; the API-safe field name uses a netmera_ prefix to avoid collisions with Nutshell built-in fields. Attribute values with complex nested structures are serialized as JSON in a Long Text custom field.

Netmera Segments define audience rules that cannot be directly transferred because Nutshell does not support dynamic behavioral segmentation. We document each Netmera segment with its name, rule logic, member count, and creation date. The customer admin uses this documentation to create equivalent Nutshell static lists (by exporting the segment member email list and importing as a Nutshell list) or saved filters (using the equivalent attribute filters in Nutshell's reporting layer). Segments with complex multi-condition rules that cannot be replicated are flagged for manual rebuilding.

Netmera Tags used for labeling users migrate to Nutshell custom fields on the Person or Lead object using multi-select picklist type. We extract all unique tag values from the user export, configure a Nutshell multi-select picklist with those values as options, and populate tag associations during the Person import. Tags used for campaign attribution are documented separately for the admin to handle as campaign metadata.

Netmera Device records bind users to physical devices for push delivery (push token, OS, app version). Push tokens are non-transferable — they are tied to Netmera's APNs and FCM credentials and must be regenerated under the destination platform's credentials. We export device metadata (OS type, app version, device model) as informational fields on the Nutshell Person record. The push token field itself is exported to a separate reference file for the customer's mobile team to use in a re-opt-in or silent token refresh campaign post-migration.

Netmera campaign records (name, content, scheduling, performance metrics) map to a Campaign record in Nutshell if the customer licenses Nutshell Marketing, or to Activity notes on the associated Person records if not. Campaign content blocks and message copy are exported as text and attached as notes. We do not migrate campaign creative assets (images, videos) because they reference Netmera-hosted media URLs that will be inaccessible after the platform switch.

Netmera Journeys define multi-step user-entry orchestration flows. Nutshell does not have a native journey orchestration equivalent. We document each Journey with its entry condition, step sequence, channel sequence, and conversion event definition. The customer admin uses this documentation to design equivalent sales automation rules in Nutshell or to note which journeys require rebuild in a dedicated orchestration tool (such as a marketing automation platform paired with Nutshell). Journey conversion counting is user-based in Netmera (one conversion per user per journey); we note this discrepancy in the documentation so KPIs are not misread post-migration.

Netmera SDK-tracked behavioral events (page views, custom actions, trigger events) have no direct Nutshell equivalent because Nutshell does not capture behavioral web or app events natively. We export the event schema (event names, property keys, property types) as a written inventory document that the customer can use to configure equivalent event tracking in their app via a different analytics or CDP tool, or to note which events should be handled by a marketing automation integration post-migration. Raw event property values do not migrate.