Migrate from eMarketeer to Microsoft Dynamics 365 Sales

eMarketeer Contact records map directly to Microsoft Dynamics 365 Sales Contact. We map email, firstname, lastname, phone, custom properties, and lifecycle stage to standard Contact fields plus any custom fields created in the destination. Owner resolution is by email match against the Dynamics 365 User table. Any Contact without a matching User goes to a reconciliation queue for admin provisioning before record import. Lifecycle stage from eMarketeer is preserved in a custom field em_lifecycle_stage__c for segmentation and reporting continuity.

eMarketeer Campaigns map to Microsoft Dynamics 365 Sales Campaign. Campaign name, description, send date, and send status migrate. eMarketeer open and click engagement metrics per contact aggregate into CampaignMember activity records (Sent, Opened, Clicked status) rather than individual activity log entries. If the eMarketeer export exposes granular per-contact engagement timestamps, we create Task or EmailMessage records against the Contact for timeline continuity.

eMarketeer Segments are defined by real-time criteria rules that re-evaluate continuously, not by static membership lists. This is a key mapping decision: we snapshot the current segment membership at migration time using the live criteria as of the export date, then create a static Marketing List in Microsoft Dynamics 365 Sales with those contacts pre-populated. Any segment that requires real-time re-evaluation post-migration requires the customer's admin to rebuild the criteria using Dynamics 365 Marketing dynamic list rules or Power Automate logic.

eMarketeer Flows use trigger-action logic with conditions, delays, and multi-step sequences. Microsoft Dynamics 365 Sales Sequences (available from Sales Enterprise tier) provide cadence-based sales engagement but use a different trigger model. We do not migrate Flows as code. We audit each eMarketeer Flow during discovery, document its trigger type (contact lifecycle change, form submission, time delay, CRM event), conditions, actions, and recommended Dynamics 365 Sequence or Power Automate equivalent, and deliver this as a written inventory for the customer's admin to rebuild post-migration.

eMarketeer custom properties extend Contact and Campaign records with business-specific fields. Property types (text, number, date, dropdown, checkbox) map to equivalent Dynamics 365 field types. Enumerated values in dropdown properties require explicit value mapping to Dynamics 365 option set values. Default values are preserved in the field definition. Custom properties are discovered from the export during scoping because eMarketeer does not publish a public field registry; we include schema derivation time in the scoping phase and surface any unmapped fields before transformation begins.

eMarketeer tracks opens, clicks, unsubscribes, SMS sends, and form submissions per Contact per Campaign. We aggregate this history into Contact Activity records in Microsoft Dynamics 365 Sales . Opens and clicks with timestamps migrate as EmailMessage records linked to the Contact. Unsubscribe events migrate as a Contact preference update (HasOptedOutOfEmail = true) with the original timestamp preserved in a custom field em_unsubscribed_at__c. SMS send history migrates as Task records with TaskSubtype = SMS and content in the Description field.

eMarketeer Events manage registrations and attendance tracking. Event name, date, location, and registration count map to Microsoft Dynamics 365 Sales Campaign fields where applicable. Attendee registration lists migrate as CampaignMembers with AttendanceStatus populated. Custom event types and per-attendee check-in statuses require field-level mapping against the Dynamics 365 campaign schema and may need custom fields if the out-of-box fields do not capture the same granularity.

eMarketeer email templates export as HTML blobs. We extract and deliver the HTML content and any dynamic field placeholders as a written reference document for the customer's admin to reconstruct in Microsoft Dynamics 365 Sales using the native Email Template editor or Dynamics 365 Marketing. Visual template editors with locked or proprietary components do not reconstruct identically; we flag any unsupported blocks and provide raw HTML for manual adaptation.