Migrate from Netmera to Salesforce Sales Cloud

Netmera Users map to Salesforce Contact as the primary record. The Netmera user identifier becomes an External_ID__c field for deduplication. Standard profile attributes (email, first name, last name, phone, language, timezone) map to Contact fields directly. Custom profile attributes migrate to Contact custom fields (__c suffix) that we provision in Salesforce before migration. Users flagged as EU data subjects require GDPR data controller confirmation before export from Netmera.

Netmera Segments define audience populations for targeting and export. We map each Segment to a Salesforce Campaign of type Static, with the segment membership expressed as CampaignMember records linking the migrated Contacts. Segment membership criteria are preserved as a text field on the Campaign record for audit. Dynamic segments that update automatically are noted; we export the membership at scoping time and do not maintain live sync post-migration.

Netmera Campaign records (name, status, channel, scheduling, performance metrics) migrate to Salesforce Campaign. Channel type maps to Campaign Type picklist values (Advertisement, Email, Mobile Push, Social, Webinar, Other). Performance metrics (open rate, click rate, delivery rate) migrate to custom fields on Campaign. Campaign content blocks and body text migrate to Campaign Description or a custom rich text field; image assets migrate as ContentDocument attached to the Campaign if under file size limits.

Netmera Journey flows define multi-step user-entry rules and channel steps. We map each Journey to a Salesforce Campaign with entry conditions preserved as a custom field journey_entry_conditions__c. Note that Netmera Journey Analytics counts one conversion per user per journey; Salesforce Campaign conversion counts conversion events per occurrence. We document this KPI discrepancy during scoping so reporting expectations align post-migration.

Custom profile attributes in Netmera (beyond defaults like email and phone) map to Salesforce Contact custom fields. We provision all custom fields in Salesforce before migration, matching attribute types (string to Text, number to Number, boolean to Checkbox, date to Date). Attribute values transfer as data; attribute-level validation rules are noted for Salesforce field validation configuration.

Netmera Device records bind users to physical devices and include push tokens, OS, device model, and app version. We map device OS and app version to Contact custom fields. Push tokens themselves are flagged as non-transferable and documented for re-enrollment planning; they do not migrate to Salesforce because they are bound to Netmera's APNs/FCM credentials.

Netmera SDK-tracked behavioral Events (page views, custom actions, trigger events) are mapped to Salesforce Campaign Activity records or custom Event objects depending on volume. High-volume event migrations use the Salesforce Bulk API with batch chunking. Event property keys migrate as field names; property values with inconsistent formats require normalization before import.

Netmera Widget assets (tooltips, pop-ups, in-app messages) with file constraints of 1MB images and 12MB video are exported as design metadata and content. The widget rendering engine is platform-specific and cannot migrate. We export widget designs and content references; the customer's admin rebuilds widget rendering logic in Salesforce using Content Builder or an equivalent in-app messaging tool. Assets exceeding file size limits are flagged for re-encoding.

Netmera Tags label users and organize data. Tag associations migrate as additional Contact custom fields or as Campaign Member Status values depending on tagging use case. The customer chooses tag strategy during scoping: tag-as-field for behavioral labels, tag-as-campaign for audience grouping.

Netmera Survey and Feedback tool records (questions, response data) migrate to Salesforce Campaign or a custom Survey Response object depending on response volume. Survey display logic and trigger conditions are platform-configured and require rebuild in Salesforce Forms or a third-party survey integration.

Netmera Pages and funnel configurations define content surfaces and conversion funnels. We map page structure and funnel step definitions to Salesforce Campaign or Experience Cloud Site Pages. Site search and browse optimization settings are configuration-only and documented for admin rebuild.

Netmera Owners (user-level campaign managers) map to Salesforce User records by email match. Owners without a matching Salesforce User go to a reconciliation queue for admin to provision before record import resumes. Owner assignment on migrated Campaigns links to the Salesforce User.