Migrate from Field Force Tracker to Salesforce Sales Cloud

Field Force Tracker customers map directly to Salesforce Accounts. Each customer record's name, address, industry, and revenue fields translate to Account.Name, BillingAddress, Industry, and AnnualRevenue. FFT customers without an industry classification receive a default Industry pick-list value. Parent-child customer hierarchies map to Account.ParentId if present in Field Force Tracker.

Field Force Tracker technicians are field employees who perform work orders. They resolve by email match to Salesforce Users if they need login access, or to Contacts if they are non-user stakeholders. Unmatched technicians receive a fallback Contact record flagged with FFT_Technician_Source__c so your admin can reassign ownership after go-live.

Field Force Tracker work orders are the primary service record and map to Salesforce Cases. The work order number becomes Case.CaseNumber, customer maps to Case.AccountId, and technician maps to Case.OwnerId. FFT work order status values map value-by-value to Salesforce CaseStatus pick-list; any custom FFT statuses become a Case.Custom_Status__c custom field preserving the original value.

Individual line items on a Field Force Tracker work order — parts used, labour hours, service description — migrate as a custom Work_Order_Line__c custom object linked to the Case via a lookup. This preserves the per-job financial breakdown without forcing it into Salesforce's Opportunity Product model which is designed for sales quotes, not service billing.

Field Force Tracker equipment records map to Salesforce Asset objects. The Asset is linked to the Account (Case.AccountId in lookup). Serial number, model number, install date, and warranty expiry map to Salesforce Asset standard fields. FFT-specific fields like equipment condition at install or maintenance tier migrate as custom fields on the Asset.

Field Force Tracker maintains a per-asset service history as a list of past work orders. Salesforce Asset has no native history sub-object. We create an Asset_Service_History__c custom field on the Asset record and populate it with a comma-separated or JSON list of historical work order references. For large histories, we recommend a separate Asset_Service_Event__c custom object.

FFT invoices represent completed work order financials. These merge into Salesforce Opportunities at a closed-won stage, with invoice line items stored as OpportunityLineItems if the Salesforce product catalog is configured. If your invoice records carry custom fields not representable in OpportunityLineItems, we create a custom FFT_Invoice__c object and link it to the Account.

Field Force Tracker quotes and estimates map to Salesforce Opportunities in a Proposal or Negotiation stage, or to the Salesforce Quote object if your org has Quotes enabled. The quote amount and description migrate to Opportunity.Amount and Description. Approval status in FFT translates to a custom Quote_Approval_Status__c field.

Field Force Tracker inspection checklists and multi-step forms per industry module (HVAC, elevator, fire alarm, copier) have no Salesforce standard equivalent. We create a custom Inspection_Form__c object and custom fields per form field, linked to the related Case. The form's structure is exported as a JSON schema for your admin to optionally rebuild in Salesforce's Screen Flow or a third-party form tool.

Field Force Tracker's parts inventory tracking has no Salesforce Sales Cloud native equivalent. We migrate parts as a custom Inventory_Item__c object linked to the Account or a central Inventory Account. Part quantities, reorder levels, and bin locations become custom fields. Reordering automation must be rebuilt in Salesforce Flow or handled via Salesforce Field Service inventory management if FSL is deployed.

Field Force Tracker files attached to work orders, assets, or customers re-upload to Salesforce Files (ContentDocument / ContentVersion). Each file is linked to its parent record — Case, Asset, or Account — via ContentDocumentLink. Files exceeding Salesforce's 25MB per-file limit are flagged for chunking or external hosting with a download link stored in a custom field.

Field Force Tracker's real-time dispatch board, technician routing, and GPS tracking have no Salesforce Sales Cloud native equivalent. GPS coordinates migrate as Latitude__c and Longitude__c custom fields on the related Work_Order__c or Case. The scheduling logic must be handled by Salesforce Field Service (FSL) add-on or a third-party field service app post-migration.