Migrate from Evam to Microsoft Dynamics 365 Sales

Evam Customer records map to Microsoft Dynamics 365 Sales Contact attached to an Account. Standard profile fields (name, email, phone, demographic attributes) migrate 1:1 to Contact fields. We create the parent Account using the Customer's domain or company name as the Account name. Any custom customer properties are flagged for field-level mapping against Dataverse field types before migration. The Contact's createdon and modifiedon timestamps preserve the original Evam record timestamps for audit.

Evam behavioral and transactional Events map to Microsoft Dynamics 365 Sales Activity records (Task with a custom EventType field for behavioral markers, or EmailMessage for transactional events). Event payload schemas are mapped field-by-field to custom Activity fields. We scope the event export to the last 90-180 days due to Evam API volume limits; older events are aggregated into a summary record attached to the Contact. Event timestamps migrate as ActivityDate on the corresponding Task so that the activity timeline preserves chronological ordering.

Evam Journey definitions encode step sequences, branch conditions, wait timers, and entry/exit rules. These are not exposed via a documented export endpoint. We capture journey topology during discovery via API snapshots and manual documentation: each Journey's name, triggering segment, step count, step types, channel actions, and branch logic are recorded in a written migration inventory. The customer's Dynamics 365 administrator uses this inventory to rebuild equivalent flows in Power Automate. We do not attempt to reverse-engineer journey logic from event data alone.

Evam Campaign metadata (name, status, start and end dates, channel assignments, associated segments) migrates to Microsoft Dynamics 365 Sales Campaign. Campaign performance metrics (open rates, click rates, delivery rates) are derived metrics computed by Evam's analytics engine; these do not migrate directly. We provide a campaign baseline summary from Evam's reporting export and recommend rebuilding metrics in Microsoft Dynamics 365 Sales Marketing or Power BI post-migration.

Evam Segments are customer groupings with rule-based membership criteria. We export segment definitions as rule sets and translate them into Dynamics 365 Marketing segment membership rules where the customer holds a Dynamics 365 Marketing license. Without Dynamics 365 Marketing, segments migrate as static Dataverse security groups or custom lookup tables that the customer's admin populates from the segment membership export. The segment name and criteria are preserved in a custom field on the Contact for reference.

Evam Channel configurations (SMS sender IDs, push notification credentials, in-app notification setup) are environment-locked and cannot be transferred. We document the full channel configuration during discovery — provider names, API credentials, sender ID templates, and routing rules — and deliver a re-setup checklist for the customer's operations team to re-register credentials in Power Automate or the relevant Microsoft Dynamics 365 Sales channel connector before cutover.

Extended properties on Evam Customers, Events, or Journeys defined beyond the standard schema migrate to Dataverse custom fields on the corresponding entity. We map each custom field field-by-field, noting Dataverse data type compatibility (string to Text, integer to Whole Number, decimal to Decimal, boolean to Two Options, date to Date and Time). Custom fields on Journey objects are recorded in the journey inventory for manual rebuild in Power Automate since Journey is not a migratable entity.

Evam AI-based propensity scores are computed per-customer within Evam's runtime environment and are not accessible via the documented API. These scores cannot be migrated. Customers relying on AI-driven routing in Evam Journeys should plan to re-run scoring in Microsoft Dynamics 365 Sales using Copilot for Sales insights or a third-party scoring model post-migration. We disclose the score gap in the discovery report and note the customer's acceptance of a scoring-free day-one state before migration begins.