Migrate from Netmera to Microsoft Dynamics 365 Sales

Netmera Users map to Microsoft Dynamics 365 Sales Contacts. We extract the user identifier, display name, email address, phone number, and all standard profile fields. Custom profile attributes (string, number, date, boolean types) map to custom Contact fields that we pre-create in Microsoft Dynamics 365 Sales via the metadata API before import. The migration uses Dynamics 365's Bulk API with chunking to handle volume efficiently, and the dedupe key is the email address. Any user record without a valid email address is held in a reconciliation queue because Contacts without email are not actionable in Microsoft Dynamics 365 Sales outbound processes.

Netmera Users that represent prospective buyers who have not been qualified into the sales process map to Microsoft Dynamics 365 Sales Lead records. We define the qualification boundary during scoping — typically users with a Netmera profile attribute indicating prospect status or those without a purchase event — and apply the split at migration time. The Lead record carries the original Netmera user ID in a custom field netmera_user_id__c for audit traceability. The customer decides whether to use Lead records at all if their sales process begins at Contact.

If Netmera stores company-level data alongside user profiles (common in B2B implementations), those company records map to Microsoft Dynamics 365 Sales Account. The company domain name becomes the Account Website field and is used as the dedupe key during import. Account is created before any Contact or Lead import so that the parent AccountId reference is resolved at insert time. Netmera users without a company association become Contacts without an Account link and are flagged in the reconciliation report.

Netmera Segments are rule-based audience definitions (user property filters, event triggers, behavioral conditions) used for campaign targeting. Microsoft Dynamics 365 Sales does not have an equivalent rule-based segmentation engine in its base CRM tier. We document each Netmera segment's rule logic in a segment inventory, then recommend mapping active segments to static Marketing Lists (user-managed, manually updated) or, if the customer licenses Dynamics 365 Marketing, to dynamic marketing lists with equivalent query conditions. Segments that rely on real-time behavioral triggers require Power Automate or a Dynamics 365 Marketing journey to replicate.

Netmera custom profile attributes (beyond the default name, email, phone set) migrate to Microsoft Dynamics 365 Sales Contact custom fields. We map the attribute name to a Salesforce-compatible API name with __c suffix, select the equivalent Dynamics 365 field type (Text, Number, Two Options, Date, etc.), and preserve the original attribute values in the import. Multi-value attributes (arrays, tag collections) map to Dynamics 365 MultiSelect Option Set or a delimited text field depending on the data pattern. We configure these fields in the Microsoft Dynamics 365 Sales schema before any data loads run.

Netmera Device Information records bind users to physical devices for push delivery, storing OS type, device model, push token, and app version. Push tokens are device-bound to Netmera's APNs and FCM credentials and cannot function in Microsoft Dynamics 365 Sales . We export the device data as a custom Microsoft Dynamics 365 Sales entity (PushDevice__c) to preserve the device linkage history for the customer's re-enrollment campaign. This allows the customer's mobile team to identify which users had push-enabled devices and trigger a silent token refresh or re-opt-in campaign in their chosen push provider post-migration.

Netmera campaign records contain the campaign name, content body, channel, schedule, and performance metrics (delivery rate, open rate, conversion). We migrate campaign metadata and content blocks to Microsoft Dynamics 365 Sales Campaign records, with the campaign description carrying the channel and scheduling details. Campaign performance metrics are stored as custom fields on the Campaign record for historical reference. Creative assets (images under 1MB, video under 12MB per Netmera FAQ) are flagged for manual re-upload because the Microsoft Dynamics 365 Sales campaign editor has its own asset library. Push and in-app campaign formats have no native Microsoft Dynamics 365 Sales equivalent and are documented as requiring a third-party push integration rebuild.

Netmera Journeys are multi-step user-entry flows with channel steps and conversion event definitions. Microsoft Dynamics 365 Sales does not include a native journey orchestration engine. We deliver a written journey inventory that documents each Netmera Journey's entry trigger, step sequence, channel assignments, and conversion event. For customers with Power Automate or Dynamics 365 Marketing licenses, we provide a step-by-step configuration guide to rebuild each journey using Power Automate triggers, condition branches, and Outlook/Teams actions. Without Power Automate, the customer's admin rebuilds these manually or accepts the manual campaign re-send model.

Netmera captures behavioral events (page views, custom actions, trigger events) linked to user profiles. Microsoft Dynamics 365 Sales has no native behavioral event store. We map the event name, event properties, and timestamp to a custom Dynamics 365 entity (BehavioralEvent__c) with a lookup to the originating Contact. This preserves the event history for audit and reporting purposes, though it does not activate Dynamics 365's native analytics. Customers requiring real-time behavioral segmentation post-migration should evaluate Dynamics 365 Customer Insights as a complementary data layer.

Netmera Tags label users for segmentation and internal categorization. Tags stored as multi-checkbox profile properties migrate to a Microsoft Dynamics 365 Sales Contact custom field of type MultiSelect Option Set, with each Netmera tag value added as an option. Tags used for campaign targeting are also documented in the segment inventory referenced above. Netmera's tagless data capture feature means some user records may have no tags; we treat untagged users as having no tag value in Dynamics 365 rather than creating a default tag.

Netmera Widgets are in-app visual assets (tooltips, pop-ups, banners) with file constraints of 1MB images and 12MB video. Widget designs, copy, and layout specifications migrate as a written asset inventory with screenshots and content export. The widget rendering engine is platform-specific and cannot be transferred. We flag assets that meet Netmera's file limits for re-encoding and upload to the destination platform's media library. In-app message campaigns built with widgets require reconstruction using the destination platform's native in-app message builder or a third-party tool.