Migrate from Method:Field Services to Microsoft Dynamics 365 Sales

Method contacts migrate 1:1 to Dynamics 365 Contact records. Dynamics requires an Account lookup on every contact — contacts without a primary company in Method receive a placeholder 'Unassigned Account' or the dispatcher/owner record is used as a stand-in until accounts are linked.

Method companies map to Dynamics Accounts. Parent-child hierarchies in Method map to the Account.ParentId field. Multi-address companies need the Address Number field to distinguish shipping vs. billing locations when writing to the Dynamics Address1/Address2 composite.

Dynamics has no native Work Order entity. A custom table (new_workorder) is created in the migration solution with fields for WorkOrderNumber, Status, Description, ScheduledDate, AssignedTechnician, CustomerId (lookup to Account), ContactId (lookup to Contact), SiteAddress, JobType, and Priority. FlitStack generates the table creation plan before data loads.

Each work order line item (service task, part used, labor) migrates as a child row in the new_workorderdetail custom table linked to the parent work order via a 1:N relationship. Original line item totals are summed and written to the parent work order's EstimatedAmount field.

Method estimates translate to Dynamics Quote records. The QuoteLineItem entity holds individual estimate line items. Status mapping: Draft → Draft, Sent → Active, Accepted → Won, Declined → Lost. Original estimate date preserved in the CreatedOn field or a custom CreatedInSource__c field.

Method invoices migrate to Dynamics Invoice records, but QuickBooks-linked invoice data (payments, QB transaction IDs) does not carry financial settlement history. Post-migration, a QB-to-D365 connector (KingswaySoft or Scribe) must be configured to re-link invoice payments if continued QB reconciliation is required.

Method's Field Crew role translates to Dynamics Bookable Resource entities when the Field Service module is in scope. Without Field Service, technicians migrate as User records with a custom Technician__c flag and security role assignment. Email-matching resolves owner IDs in work order and contact records.

Method dispatchers migrate as Dynamics Users. A custom Dispatcher__c flag field identifies them for scheduling and dispatch admin functions. Their QuickBooks user linkage is severed — a new Dynamics login must be provisioned and licensed before migration if the dispatcher is to access Dynamics directly.

Method custom tables created via Tables/Fields tab map 1:1 to Dataverse custom tables. Table names are lowercased and prefixed with new_ in Dynamics. Relationships between custom tables in Method must be mapped to 1:N or N:N relationships in Dataverse during the schema build phase before migration runs.

Method's Time Tracking app entries (beta feature) store labor hours against work orders. In Dynamics Field Service, FSSTimeEntry entities handle this. Without Field Service, a custom TimeEntry__c table is required with lookup to the custom work order table. Original clock-in/clock-out timestamps are preserved as custom datetime fields.

Method file attachments on work orders, contacts, or companies migrate to Dynamics Note (Annotation) records attached to the target entity. For larger files or document libraries, SharePoint integration is activated post-migration and documents are re-hosted in Dynamics-connected SharePoint libraries.

Method's QB-synced metadata (QB Invoice IDs, QB Customer IDs, sync timestamps, payment status flags) has no Dynamics equivalent. This data is preserved in custom text fields (QB_SyncID__c, QB_InvoiceID__c) for reconciliation reference, but Dynamics does not process QB transactions natively.