Migrate from Field Force Tracker to Freshsales

Field Force Tracker customers (businesses with service agreements) map directly to Freshsales Accounts. Address, phone, and contact name fields migrate as Account-level properties. Industry, website, and any custom properties also transfer as standard or custom Account fields. Multi-site customers require parent-account linkage if Field Force Tracker stores branch relationships, and each service location becomes a separate child Account linked to the parent.

Work orders are the core migration challenge — Field Force Tracker stores labor hours, parts used, technician ID, and GPS coordinates on a single work order; Freshsales Deal has amount, stage, probability, and close date but no native labor or parts fields. We map job status to Deal stage, total job value to Deal amount, and carry all FSM-specific fields as Freshsales custom fields.

Field Force Tracker employees (technicians, dispatchers, admins) map to Freshsales Contacts for the contact record and are matched by email to Freshsales Users for agent log-in access. Employment status, role, and skills are stored as custom fields on the Contact. GPS-enabled field techs keep their FFT employee record but do not gain a separate Freshsales GPS field.

Field Force Tracker inventory items and parts catalog map to Freshsales Products. Part number maps to Product SKU, description maps to product description, and unit price maps to Standard Price. Current stock quantity cannot migrate as Freshsales Products has no native stock-level field — stock-on-hand is preserved as a custom number field.

Field Force Tracker service contracts (SLA terms, contract values, renewal dates) have no Freshsales native equivalent. We migrate them as a custom object linked to the Account, with fields for contract value, start/end dates, and SLA tier. Customer admin configures the custom object in Freshsales before the migration plan finalizes.

Field Force Tracker equipment assets tracked per customer location have no Freshsales standard object. We migrate them as a custom Asset object linked to the Account and Work-Order-as-Deal, preserving manufacturer, model, serial number, install date, and last service date. This requires a custom object setup in Freshsales before migration.

Field Force Tracker work order notes, service summaries, and technician reports migrate as Freshsales Notes attached to the Deal. Timestamps and author are preserved. If the note contains structured data (checklist items, sign-off fields), the raw text migrates and the admin rebuilds the structured format in Freshsales.

Field Force Tracker check-in and check-out timestamps per employee per shift cannot map to any Freshsales field — Freshsales has no attendance or geo-fencing model. We preserve check-in log records as Notes on the Contact record with original timestamps for audit purposes; the operational use of this data must be rebuilt in Freshsales.

GPS coordinates from Field Force Tracker field visits and geo-fence boundary definitions have no Freshsales equivalent — Freshsales stores no geospatial data. We preserve the last-known work order coordinates as custom latitude/longitude text fields on the Deal for reference, but geo-fencing and real-time location tracking cannot be migrated and must be managed through a separate FSM tool.

Every custom property Field Force Tracker stores on customers, work orders, employees, or assets requires a corresponding Freshsales custom field. We deliver a custom field creation checklist before migration so the Freshsales admin pre-creates all required fields and we validate name/type matching during the sample migration.