Migrate from Netmera to HighLevel

Netmera Users map to GoHighLevel Contacts. We extract via segment-based export (Netmera has no bulk raw-user endpoint), creating a segment that captures the target population with frozen rules at scoping. User profile attributes map to GoHighLevel Contact custom fields, preserving attribute type (string, number, boolean, date). User email becomes Contact email and dedupe key. External ID is stored as a custom field for future sync resolution.

Netmera Segments define audience rules and serve as both targeting units and export sources. We map segment membership criteria to GoHighLevel Tags (applied to Contacts) or Contact Lists (group-based membership). Dynamic segments in Netmera that update automatically produce different counts at export time; we freeze segment rules at scoping and document the freeze timestamp for audit. Segment count and membership criteria are preserved as tag descriptions or list metadata in GoHighLevel.

Netmera custom profile attributes (string, number, boolean, date, array) map to GoHighLevel Contact Custom Fields with corresponding types. We create the destination schema before import, using GoHighLevel's custom field API. Attribute arrays stored as comma-separated values migrate to GoHighLevel multi-select picklist or text fields depending on cardinality. Default Netmera attributes (user_id, email, created_at, last_active) map to standard GoHighLevel Contact fields where equivalents exist.

Netmera device records include push token, OS, and app version. Push tokens are device-bound to Netmera's APNs and FCM credentials and cannot transfer to GoHighLevel. We export device metadata (OS, app version, device model) as Contact custom fields and document the push token regeneration requirement. The customer plans a re-opt-in campaign or silent token refresh for active app users post-migration to restore push notification delivery.

Netmera campaign records (push, in-app, SMS, email) include name, content, scheduling, and performance metrics. We migrate campaign metadata and content blocks to GoHighLevel as Workflows with corresponding Email or SMS Templates. Creative assets (images under 1MB, video under 12MB) are exported as files and documented for re-upload into GoHighLevel's media library. Campaign scheduling logic maps to GoHighLevel Workflow triggers and time-delay actions. Performance metrics (open rates, click rates) are preserved as a CSV inventory for the customer to re-enter into GoHighLevel reporting.

Netmera Journeys define multi-step user-entry rules and channel steps with per-user conversion counting. We map the entry conditions and step sequence to GoHighLevel Workflow triggers and actions. Note that Netmera counts one conversion per user per journey; GoHighLevel Workflows count per-trigger-occurrence. We document this KPI definition discrepancy during scoping so the customer adjusts reporting expectations post-migration. Journey-to-workflow redesign is a manual rebuild scope documented in the handoff inventory.

Netmera captures SDK-tracked events (page views, custom actions, trigger events) per user. We map event names and property keys to GoHighLevel Activities (Tasks with custom property fields or Notes attached to Contact). Event schemas vary by Netmera implementation; we normalize property values during transform and document any property keys that cannot map directly to GoHighLevel's flat field model. Historical event volume may be large; we batch via GoHighLevel's bulk import API with rate-limit handling.

Netmera tags label users and organize data. We map tag names and user associations to GoHighLevel Tags applied to Contacts. Netmera supports tagless data capture meaning some user records may have no tags; these migrate as untagged Contacts. Tag cardinality and naming conventions are preserved as-is.

Netmera survey questions and response records map to GoHighLevel Contact custom fields for structured responses or to GoHighLevel's native Survey tool for display logic rebuild. Survey trigger conditions and display logic are platform-configured and do not migrate; we deliver a written survey configuration inventory for the customer admin to rebuild in GoHighLevel Surveys.