Migrate from Dynamics 365 Field Service to monday CRM

Dynamics 365 Field Service stores customer accounts as msdyn_account entities with service addresses and contact relationships. These map to Monday CRM contacts (people) and company items — we resolve the primary contact as a Monday contact record and the account name as a separate company item, preserving service address in custom columns.

Dynamics contact records map 1:1 to Monday CRM contacts. Full name, email, phone, and job title transfer directly. We match by email to avoid duplicate contacts in Monday and flag unmatched Dynamics contacts for manual resolution before the migration commits.

Dynamics Bookable Resources represent field technicians, contractors, and equipment. We map them to Monday CRM team members by email match — the resource name becomes the member name, and the resource type (user vs. contact vs. equipment) maps to a custom column in Monday. Unmatched resources become contacts for assignment after go-live.

Work orders are the core entity in Dynamics 365 Field Service. Each work order maps to a Monday CRM item on the Deals or Service board. The work order subject becomes the item name, and status, priority, and estimated duration map to Monday status and date columns. Primary customer and site links preserve the account relationship.

Dynamics work order line items (products, services, and fees) aggregate under a single work order. We flatten these as sub-items in Monday CRM — each line item becomes a sub-item with product name, quantity, unit price, and tax. This preserves the financial breakdown while fitting Monday's sub-item model.

Dynamics incident types define the service category (repair, maintenance, installation). We map these to Monday status column values on the service board so teams can filter and group work orders by service type. Custom incident types require pre-configuration of status options in Monday before migration.

Dynamics customer assets track equipment at service locations with serial numbers, product associations, and install dates. We map each asset to an item on a dedicated Monday CRM asset board and link it back to the customer account item. Asset hierarchies collapse to parent-asset custom columns since Monday does not support nested asset structures natively.

Dynamics 365 FS agreements define preventive maintenance contracts with billing frequencies and service territories. We map agreements to items on a recurring service board in Monday CRM, preserving start date, end date, billing frequency, and the agreement amount. Recurring work orders generated from agreements require post-migration automation rebuild.

Dynamics booking records encode the scheduled start and end times for a resource on a work order. We translate these into Monday date columns and timeline views — the scheduled start maps to the item start date and the booking duration maps to the timeline span. Multi-resource bookings generate multiple item entries linked by a group or label.

Dynamics service tasks define checklist items within a work order (e.g., safety inspection, parts replacement). We split these into Monday checklist items attached to the work order item. Each checklist item preserves the task description and whether it was marked complete in Dynamics, maintaining the service record fidelity.

Dynamics annotations on work orders and assets — including text notes and file attachments — migrate as item updates in Monday CRM for text and file uploads for attachments. Original timestamps and note authors are preserved in the update metadata. File size limits follow Monday's storage tier constraints.

Dynamics resource territories define geographic service zones for dispatch. We map territories to Monday groups on the service board — each work order in a territory groups under that group's header. Territories with multiple members generate a tag on each item for cross-group filtering.