Migrate from Netmera to Twenty CRM

Netmera User profiles map to Twenty CRM Person records. The mapping preserves email, name fields, phone, and any standard profile attributes. Netmera does not expose a raw bulk-user export endpoint—data retrieval requires creating a Segment in the UI with audience rules that capture the target population. We work with the customer to define precise segment rules during scoping, freeze those rules to prevent dynamic updates, run a test export, and validate coverage before committing to the full extraction. Any Users not covered by the frozen segment rules are flagged for a supplemental extraction pass.

Netmera custom profile attributes store user-level data beyond defaults (string, number, boolean, date types). We migrate attribute names and values as custom fields on the Twenty Person object. The field type mapping follows: Netmera string/number/boolean map to Twenty text/number/checkbox equivalents. Multi-value attributes require flattening into comma-separated text or a custom object depending on use case. Netmera's attribute schema is extracted from the platform UI during discovery.

Netmera Segments define audience rules and serve as both targeting units and export sources. Twenty CRM does not have a dynamic segmentation engine; instead, we map segment membership to Tags on the Person record. We extract the segment rules during scoping, apply those rules to the frozen user export to determine membership, and create Tag records on the corresponding Person entries. The customer decides during scoping whether to import all segments as tags or consolidate to a priority subset. Dynamic segments that auto-update produce different membership at export time versus scoping time, which is why we freeze segment rules before extraction.

Netmera Tags used for labeling users and organizing data map directly to Twenty CRM Tags. Tag names migrate verbatim. Tag-to-user associations migrate as Tag records linked to the corresponding Person. Note that Netmera's tagless data capture feature means some user data may arrive without any tag, and we preserve those records without tags in Twenty.

Netmera Device records bind users to physical devices for push delivery, including push token, OS, and app version. We export the OS type and app version as custom fields on the Person record. Push notification delivery tokens stored in Netmera are tied to APNs and FCM credentials configured within Netmera and are non-transferable to Twenty CRM. We flag this upfront and recommend planning for a re-opt-in campaign or silent token refresh for active app users post-migration. Without this step, migrated users will not receive push notifications in any new engagement setup.

Netmera Campaign records include name, content, scheduling, and performance metrics. Twenty CRM has no campaign or multi-channel messaging object. We extract campaign metadata (name, channel type, send date, recipient count, open rate, click rate) as structured records in a temporary migration staging object or as formatted Notes attached to the related Person. The customer uses this metadata as a reference for rebuilding campaigns in a dedicated engagement platform. We do not migrate campaign creative (images, videos, rich text content) unless the customer explicitly requests a separate content migration scope.

Netmera Journey Orchestration flows define multi-step user-entry rules and channel steps with conversion event definitions. Twenty CRM has no journey or orchestration object. We extract journey metadata (name, entry trigger, step sequence, channel per step, conversion event) as structured Notes attached to the Person records that entered the journey, preserving the journey name and step count. Note that Netmera's Journey Analytics counts one conversion per user per journey, which may differ from funnel counting in the destination reporting tool; we document this discrepancy in the migration mapping.

Netmera captures SDK-tracked behavioral events (page views, custom actions, trigger events). Event schemas vary by implementation. We extract event names and timestamps as Comment records attached to the Person record for high-value events (purchase, upgrade, key conversion actions). Routine behavioral events with high volume (page views, app opens) are typically excluded from CRM migration scope and documented in the event schema inventory. The customer decides during scoping which event types to preserve in Twenty versus which to route to an analytics platform.

Netmera Survey and Feedback tools collect structured responses linked to users. We export survey questions and response records as Comment records or a custom object (SurveyResponse) in Twenty CRM, linked to the corresponding Person. Survey display logic and trigger conditions are platform-configured and do not migrate; we document them in the rebuild inventory for the customer to implement in their chosen survey tool post-migration.

Netmera Widgets are visual engagement assets (tooltips, pop-ups, in-app messages) with file constraints of 1MB images and 12MB video. Twenty CRM has no widget or in-app message object. We export widget metadata (name, type, trigger condition, text content) as Notes. Visual assets require re-creation in the destination platform's design system. Netmera's file size limits (1MB images, 12MB video) apply during any asset extraction; we flag oversized assets for re-encoding before the customer imports them into any new engagement tool.

Netmera Pages and funnel configurations define content surfaces and conversion funnels. Twenty CRM has no page or funnel object. We export page names and funnel step definitions as Notes attached to the Person records that converted through those funnels. Site search and browse optimization settings are platform-specific and do not migrate; we document them in the configuration inventory for the customer to rebuild in their chosen web analytics or CMS tool.