Migrate from Netmera to HubSpot

Netmera user profiles map directly to HubSpot contacts. Each profile becomes one contact record. Custom attributes stored on the profile (device type, app version, push token) become HubSpot custom contact properties. The contact's email address is the primary identifier — profiles without emails are flagged for manual resolution before the migration runs.

Netmera tracks anonymous users via device fingerprinting. These profiles lack email addresses. We migrate them as HubSpot contacts with a custom Is_Anonymous__c property set to true and store the device ID as Source_Device_ID__c. When the user provides an email, the records can be merged or linked manually post-migration.

Netmera organizations that contain user profiles map to HubSpot companies. If Netmera stores a company name on the user profile, it becomes the Company record name. Multi-company associations (one user linked to multiple organizations in Netmera) map to HubSpot's Company associations or are stored as a custom property on the contact.

Netmera segments are rule-based. We export the segment membership list and map it to a HubSpot static list named after the segment. For active segments that drive ongoing targeting, we create a custom multi-checkbox property on the contact so the segment membership is visible in the contact record and usable in HubSpot workflows and reports.

Netmera events are mapped to HubSpot engagement records by event category. Push notification opens become HubSpot Call activities with a custom event_type property. Campaign clicks and page views become Note records with a custom event_name property, original timestamp, and owner preserved. The original Netmera event data is stored as a JSON blob in a custom property for auditability.

Netmera custom attributes (strings, numbers, dates, booleans) that are not HubSpot native properties require custom field creation in HubSpot. We create the property with the appropriate type (string, number, date, checkbox, picklist) and map values during migration. Attribute names are preserved as labels; the property name uses HubSpot's snake_case convention.

Netmera stores APNs and FCM push tokens per device on the user profile. HubSpot has no native push token storage. We migrate the token as a custom string property (Push_Token__c) and optionally a multi-line text property for multi-device tokens. Push notification delivery requires a separate mobile engagement tool post-migration.

Netmera push and in-app campaigns have performance data (send count, open rate, click rate) that does not map to any native HubSpot object. We preserve campaign metadata as custom properties on the associated contacts or as a custom object (Netmera_Campaign__c) so historical campaign performance is available for reporting after migration.

Netmera journey orchestrations and campaign automations are not transferable. The journey definition, trigger rules, and action steps must be rebuilt in HubSpot's workflow builder using the migrated engagement data as new triggers. We export journey definitions as a reference document for your HubSpot admin.

Netmera aggregates all user interactions in an activity log per profile. We extract the log entries and write them as Note records in HubSpot with the event type as the subject, original timestamp, and a JSON body containing the full event payload. For high-volume event logs, we use a custom activity object to avoid hitting HubSpot's note volume limits.