Migrate from Evatic to Microsoft Dynamics 365 Sales

Evatic Customer records map directly to Dynamics 365 Account entities. The Account Name, primary address, phone, and website fields carry over directly. Multi-site customers in Evatic (branch offices under one customer) translate to a parent Account with child Account records using the Parent Account lookup field in Dataverse.

Evatic Contact records (site contacts, billing contacts, technician contacts) map to Dynamics 365 Contact entities. The primary Contact per Customer links via the AccountId lookup. Secondary contacts on the same Customer become additional Contact records with the same AccountId lookup value.

Service contracts in Evatic have no direct equivalent in Dynamics 365 Sales. FlitStack creates a custom Agreement entity in Dataverse with fields for contract number, start/end dates, service level (SLA tier), contract value, and renewal status. The Agreement record links to the Account via a lookup relationship. SLA definitions require manual rebuild in Power Automate or Dynamics 365 Field Service.

Evatic equipment units (serialized assets, model numbers, install dates) map to a custom Equipment table in Dataverse. Each Equipment record links to the Account (customer site) and optionally to a Contact (equipment owner). Unit attributes (manufacturer, model, warranty expiration, last service date) become custom fields on the Equipment record.

Work orders in Evatic map to a custom WorkOrder entity in Dataverse. Fields include work order number, status (open/in-progress/complete), scheduled date, actual completion date, technician assigned (lookup to Contact or User), service type, and billable hours. Open work orders at migration time require a delta pickup to capture any completed during cutover window.

Evatic Resources (technicians, dispatchers) resolve by email match to Dynamics 365 User accounts. If a Resource has no corresponding Dynamics 365 user license, their historical assignments migrate as Contact records tagged with a Resource_Role__c custom field. Active technicians with Dynamics 365 licenses retain their assignments as OwnerId lookups on work orders.

Individual line items on Evatic work orders (parts used, labor hours, travel time, consumables) map to a custom WorkOrderLine entity with a lookup to the parent WorkOrder record. Each line captures the service type, quantity, unit cost, and total. Billable vs non-billable flags translate directly.

Evatic attachments on work orders, units, and contracts (photos, signatures, scanned documents) migrate to Dataverse Annotation entities linked to the corresponding record. Large file attachments exceeding Dataverse size limits route to SharePoint document libraries with the document URL stored in a custom field on the record.

Evatic SLA definitions (response time, resolution time, business hours calendars) have no native equivalent in Dynamics 365 Sales. FlitStack migrates SLA tier names and response-hour definitions as custom fields on the Agreement entity. SLA breach tracking and automated escalation require Power Automate workflows post-migration.

Closed, billed invoices in Evatic map to Dynamics 365 Invoice records linked to the Account and Contact. Invoice status, total amount, and line items carry over. Invoice generation and recurring billing logic from Evatic require rebuild in Dynamics 365 Finance or a custom Power Automate flow.

Service cases or requests in Evatic that are not tied to work orders migrate to a custom Case entity in Dataverse. Fields include case number, subject, status, priority, created date, resolved date, and linked Account/Contact. Case-to-work-order routing logic does not migrate and must be rebuilt in Power Automate.

Parts and products catalogued in Evatic map to Dynamics 365 Product records. Unit of measure, product type (service vs inventory), and default price transfer directly. Product库存 quantity tracking in Evatic does not translate to Dynamics 365 unless Field Service or external inventory management is enabled.