Migrate from Field Force Tracker to Microsoft Dynamics 365 Sales

Field Force Tracker organizations (business customers) map 1:1 to Dynamics 365 Accounts. The Account record becomes the parent of all related Contact, Opportunity, and Activity records via parentcustomerid. We resolve the customer name to Account.Name and preserve the original customer ID as new_fft_customer_id for traceability.

Field Force Tracker individual consumers (no company name, residential addresses) map to Dynamics 365 Contacts. We set the parentcustomerid_type to 'contact' and link residential service addresses to the Contact's address fields. Each Contact requires an AccountId — we create a placeholder Account 'Individual Customers' when individuals have no linked organization.

Field Force Tracker Jobs map to Dynamics 365 Opportunities but require transformation: Job.name becomes Opportunity.name, Job.amount becomes EstimatedValue (not the standard Amount field, which is derived from Opportunity Product rollup unless your process uses line items). We preserve Job.status as a custom field new_fft_job_status since Dynamics Opportunity stage semantics differ from Field Force Tracker's job lifecycle.

Each line item on a Field Force Tracker Job (parts, labor, travel) maps to an Opportunity Product record. We link via opportunityproduct opportunity_id and product_id lookups. If Field Force Tracker uses flat pricing not tied to a product catalog, we create a manual 'Service' product in Dynamics and set quantity and unit price from the line amount.

Field Force Tracker technicians map to Dynamics 365 SystemUser records for owner assignment. We resolve by email match: each technician's email in Field Force Tracker is matched against a Dynamics 365 user. Unmatched technicians are flagged and assigned to a fallback user. Role assignment (technician vs. admin) maps from Field Force Tracker's user type field.

Field Force Tracker location addresses map to Dynamics 365 CustomerAddress records (1:N from Account or Contact). We map the primary service address to addressnumber = 1 and preserve original Field Force Tracker location ID as new_fft_location_id on each address record. Multi-site customers generate multiple CustomerAddress records.

Field Force Tracker records status transitions with timestamps (Scheduled → In Progress → Completed). Dynamics 365 Opportunity has no native status-history audit trail. We create custom datetime fields (new_fft_scheduled_date, new_fft_started_date, new_fft_completed_date) to preserve the lifecycle timeline for reporting continuity. These custom fields capture the actual timing of each status change as recorded in Field Force Tracker, enabling analysis of technician response times and job completion patterns within Dynamics 365.

Field Force Tracker visit logs (GPS check-in, arrival/departure timestamps) have no direct Dynamics 365 Sales equivalent. We create a custom WorkOrder table in Dataverse with fields for technician (User lookup), job (Opportunity lookup), check_in_time, check_out_time, and GPS coordinates. This preserves dispatch history while keeping the CRM clean for sales-specific records.

Field Force Tracker notes attached to Jobs map to Dynamics 365 Annotations (the Note/Post model). We preserve the original note text, created-by user, and created-on timestamp. Rich-text formatting in Field Force Tracker notes converts to plain text in Annotation.notetext — HTML preservation is not guaranteed.

Field Force Tracker file attachments (photos, signed forms) migrate as Dynamics 365 Annotations with file attachments. Files are downloaded from Field Force Tracker and re-uploaded as Annotation attachments. Dynamics 365 has a 32MB file size limit per attachment — we chunk larger files and flag oversized uploads before migration.

Field Force Tracker inventory items used on Jobs map to Dynamics 365 Product records. We create Products with Field Force Tracker's part name, SKU, and unit cost. For ad-hoc parts without a catalog entry, we create 'Miscellaneous' products. Inventory quantities do not sync — Dynamics 365 Sales does not include inventory management; that's Field Service or Business Central territory.

Field Force Tracker invoices map to Dynamics 365 Invoice records when the Job is completed and invoiced. We link Invoice to the originating Opportunity via opportunityid. Invoice status (Paid, Overdue, Voided) maps to invoice status values. Historical paid invoices migrate as closed Invoice records — they do not trigger Dynamics finance modules.

Any custom properties on Field Force Tracker Customers, Jobs, or Locations migrate as custom fields on the corresponding Dynamics 365 table. Classic: new_customfieldname; Unified Interface: display name set at creation. Field data types map: text→String, number→Whole Number or Decimal, date→DateTime, dropdown→Picklist. We create a solution in your Dynamics 365 environment and add all custom fields before data loads.

Field Force Tracker scheduling rules (territory-based routing, technician skills matching, availability windows) have no Dynamics 365 Sales equivalent. We export scheduling configuration as a structured reference document and provide a Power Apps canvas app blueprint that implements the same logic against the custom WorkOrder table. This is a manual rebuild item — it is not included in the data migration scope.