Migrate from Field Force Tracker to HubSpot

Field Force Tracker's flat Customer record splits into HubSpot Contact and Company objects. The person's name, phone, email, and address fields map directly to the HubSpot Contact properties firstname, lastname, phone, email, and address. The company name from the Customer record creates a corresponding HubSpot Company (Account) and links via the Contact's associated company.

Field Force Tracker's Customer stores organization data (company name, industry, address) alongside person data. We extract the organization fields and create a HubSpot Company (Account) record. The Company.Name maps from the customer organization name, domain maps where available, and the full address migrates to the Company address properties. The Contact links to this Company via the associated company field.

HubSpot's Service Hub Ticket object is the closest structural match to a Field Force Tracker Work Order. Work order number, description, status, and priority map to Ticket subject, content, hs_ticket_status, and hs_ticket_priority. Original create and close timestamps are preserved in custom datetime fields since HubSpot's CreatedDate is set at migration time.

Field Force Tracker work order statuses (Open, In Progress, On Hold, Completed, Cancelled) map value-by-value to HubSpot's ticket pipeline stage values. We preserve the original status-transition timestamps in a custom field so reporting continuity is maintained in HubSpot's ticket dashboards.

Field Force Tracker's Employee records (technicians, dispatchers) have no direct HubSpot CRM equivalent. We resolve employees by email match to HubSpot Users for owner assignment on Tickets and Deals. For employee records that are not HubSpot users (e.g., field technicians who won't have CRM logins), we create a custom Employee__c object linked to the Contact record.

Field Force Tracker's schedule and dispatch data — job time windows, technician assignments, routing rules — has no native HubSpot equivalent. HubSpot's Meeting object captures calendar events with start/end times but lacks dispatch board or routing logic. We preserve schedule data as a custom Schedule__c object and surface it for rebuild planning with HubSpot Service Hub scheduling tools.

Field Force Tracker's Asset Management module tracks installed equipment, serial numbers, model, maintenance history, and customer association. HubSpot has no native asset object. We create a custom Equipment__c object with fields for serial number, model, install date, maintenance frequency, and a lookup to the Company record. Maintenance history migrates as related Ticket records or custom history fields.

Field Force Tracker's Service Contracts define SLA terms, billing frequency, covered assets, and expiration dates. HubSpot has no native contract object. We create a custom Contract__c object linked to the Company, with fields for contract type, start/end dates, billing frequency, and a lookup to the covered Equipment__c records. Contract status maps to a value-mapped pick-list.

Field Force Tracker's Estimates (job quotes with line items and pricing) map to HubSpot Deals when they represent a sales opportunity. The estimate total maps to Deal amount; the estimate status (Approved, Rejected, Pending) maps to a custom estimate_status__c field on the Deal. Line items from an estimate do not have a native HubSpot equivalent and are stored as a custom line_items__c text field for reference.

Field Force Tracker's invoices and payment records are financial documents tied to Work Orders. HubSpot has no native invoicing. We create a custom Invoice__c object linked to the Work Order (Ticket) and Company, capturing invoice number, date, total, and payment status. Payment history is preserved in a custom payments__c related list.

Field Force Tracker's parts inventory tracks items used on Work Orders — part number, name, quantity on hand, cost, and reorder level. HubSpot has no native inventory object. We create a custom Inventory_Item__c object linked to the Equipment__c record (installed asset) and optionally to the Company for stock-at-customer scenarios.

Field Force Tracker notes and photo attachments on Work Orders migrate to HubSpot Ticket engagements. Notes become HubSpot engagement notes with the original text preserved. Photos are re-uploaded as HubSpot file attachments on the Ticket record. Original timestamps and owner information is preserved.

Field Force Tracker captures customer signatures on completed Work Orders. HubSpot has no native signature capture field. We store signature data (base64 image or URL reference from Field Force Tracker export) as a custom Signature__c field on the Ticket and link the original file as an attachment.

Field Force Tracker's GPS check-in data (technician location, timestamp, job site coordinates) has no HubSpot CRM equivalent. Location data is preserved in a custom Checkin__c object linked to the Ticket and the Employee (User), capturing latitude, longitude, and timestamp. This is informational — HubSpot does not use it for routing or dispatch.