Migrate from Comarch Field Service Management to Microsoft Dynamics 365 Sales

Comarch Customer nodes map directly to Dynamics 365 Accounts using a field-to-field translation of core attributes including name, primary address, phone, and email. Industry classification codes from Comarch translate to Dynamics 365 IndustryCode picklist values with unmapped codes defaulting to 'Other'. Contact-role information attached to Comarch customers becomes related Contact records linked via the AccountId lookup. Multi-site customers with multiple Comarch location records transform into parent Account hierarchies in Dynamics 365, preserving the organizational structure.

Comarch contacts associated with Customer nodes map to Dynamics 365 Contacts linked via the AccountId lookup to establish the parent-customer relationship. Mobile phone, email address, job title, and name fields transfer directly to their corresponding Dynamics 365 Contact fields. Any custom contact attributes stored in Comarch extended attribute tables migrate to custom fields on the Contact entity using the new_* prefix convention required by Dataverse.

Comarch Work Orders are the central FSM object; they map to Dynamics 365 Cases (incidentid) with a custom WorkOrderNumber field to preserve the original Comarch identifier. Work Order status codes translate to Case status and resolution codes per your defined status mapping.

If your team uses Dynamics 365 Field Service, Work Orders map to the msdyn_workorder table with Field Service-specific fields (MSDynMRIFieldService, incident type, service task taxonomy). This requires the Field Service add-in to be provisioned in your Dynamics 365 environment before migration.

Comarch Resources representing field technicians resolve by email matching against Dynamics 365 Users. When an email match is found, a BookableResource record is linked to the matched User account. Resources without email addresses become Bookable Resources of type Contact. Comarch skill certifications, training credentials, and geographic service zones migrate as individual Bookable Resource Characteristics linked to the BookableResource, and resource crew memberships transfer as Resource Crew associations.

Individual line items within a Comarch Work Order map to Dynamics 365 Tasks linked to the parent Case using the RegardingObjectId lookup. Task subject, description, estimated hours, and actual duration transfer as corresponding Task entity fields. Status transitions for service tasks follow the mapped Work Order status code logic, ensuring that task completion states align with the parent case resolution.

Comarch network assets and equipment records map to Dynamics 365 CustomerAsset (msdyn_customerasset) when Field Service is in scope. Parent-child asset hierarchies in Comarch translate to the CustomerAsset.msdyn_ParentAssetId lookup field, preserving the full equipment lineage. Custom Comarch asset attributes from extended attribute tables become new_* prefixed custom fields on the msdyn_customerasset table.

Comarch parts catalog entries map to Dynamics 365 Products (product type = Product). Unit of measure and pricing data transfer to Product entity fields. Parts consumed per Work Order become Order Products or Invoice Products linked to the Case/Work Order record.

Comarch SLA configurations (response time, resolution time, escalation rules) have no direct Dynamics 365 equivalent. We preserve SLA definition data in a custom text field (SLA_Definition__c) for reference. SLA enforcement is rebuilt as Power Automate flows or Dynamics 365 SLA policies post-migration.

Comarch technician dispatch history tracking which resource was assigned, the assignment timestamp, and geographic zone maps to BookableResourceBooking records. Booking status, start time, end time, and resource IDs transfer as corresponding fields on the booking. For Work Orders with multiple assigned technicians, the migration generates one BookableResourceBooking record per technician, all linked to the same Case or msdyn_workorder.

Comarch user-defined fields and extended attribute tables on Work Orders, Resources, or Assets map to custom fields on the corresponding Dynamics 365 entity (new_* prefix). Multi-value extended attributes may require a custom related entity to preserve the full data structure.

Comarch documents attached to Work Orders migrate as Dynamics 365 Annotations, which include the note text, file attachment, and association to the parent Case or Work Order record. For large or structured document libraries exceeding typical note attachment sizes, re-hosting to SharePoint Online with Document Location records linked to the Account or Case is recommended as a post-migration activity to maintain proper document management practices.