Migrate from Field Harmony to Microsoft Dynamics 365 Sales

Field Harmony customers map to Dynamics 365 Accounts. The customer name populates Account.Name, and the primary site address populates Account.Address fields. Multiple sites per customer collapse to one primary Account record, with additional sites preserved as address variations or custom location records.

CustomerSite stores service location details including address, latitude, longitude, and site-specific notes. In Dynamics 365, these map as address fields on the Account. Site-specific service types and location identifiers are preserved as custom fields on the Account record for reference.

Site-level contacts in Field Harmony map to Dynamics 365 Contacts. Each contact's name, phone, and email map directly. Contacts link to their parent Account via AccountId lookup. Multiple contacts per site are preserved with primary contact designated by Field Harmony's primary contact flag.

Work orders translate to Opportunities in Dynamics 365 Sales. The work order title and description populate Opportunity.Name and Opportunity.Description. Work order status values map to Opportunity.StatusCode via explicit value mapping rules, converting Field Harmony states to Dynamics opportunity statuses. Original work order number is preserved in SourceSystemID__c for traceability, and the customer and site identifiers link to the parent Account record to maintain referential integrity across the migrated dataset.

Parts and materials on a Field Harmony work order map to Opportunity Product Detail records in Dynamics 365. Each line item becomes a separate product detail entry with quantity and rate mapped to UnitPrice. Product catalog integration determines whether to create new Product records or use miscellaneous items.

Field Harmony technicians resolve to Dynamics 365 System Users by email address matching. Unmatched technicians are flagged before migration for your admin to either create as Dynamics users or assign to a fallback owner. Primary technician assignments on work orders populate Opportunity.OwnerId.

Field Harmony work order status values (Scheduled, In Progress, Completed, Cancelled, On Hold) require explicit value-by-value mapping to Dynamics 365 StatusCode options. Completed work orders set the Opportunity to Closed Won or Closed Lost based on Field Harmony outcome. Pending statuses map to open Opportunity stages.

Field Harmony work order types (Installation, Repair, Maintenance, Inspection) have no native equivalent in Dynamics 365 Sales. These map to a custom pick-list field ServiceType__c created on the Opportunity table. Your admin configures the pick-list values before migration data lands.

File attachments on Field Harmony work orders and customer records migrate as Dynamics 365 Notes with file attachments. Files are re-uploaded to the target environment. Size limits from the Dynamics API apply; files exceeding 25MB are flagged for chunked upload handling.

Field Harmony custom fields on work orders map to custom fields on the Opportunity table in Dynamics 365 Sales Enterprise. Fields typed as text, number, date, or pick-list in Field Harmony map to equivalent field types. Pick-list custom fields in Field Harmony require value-mapping or custom pick-list creation in Dynamics.

Customer-level custom properties in Field Harmony (client classification, billing tier, service agreement type) map to custom fields on the Account table. Field type conversion happens during mapping: Field Harmony multi-select pick-lists become string fields in Dynamics unless your implementation creates multi-select option sets.

Field Harmony's scheduling data (scheduled date, dispatch time, technician assignment timestamp) does not map to any native Dynamics 365 Sales field. These are preserved as custom datetime fields on the Opportunity — OriginalScheduledDate__c, DispatchedAt__c — for reporting continuity even though Dynamics does not replicate Field Harmony's dispatch board functionality.