Migrate from ServiceTracker to Freshsales

ServiceTracker customers with a business name map to a Freshsales Account, with the primary contact person created as a Freshsales Contact linked via AccountId. Solo customers without an organization name land as Contacts only, with no AccountId. The mapping also preserves the original ServiceTracker customer ID in a custom field on the Account record for cross-referencing. Address information from ServiceTracker migrates to the Account address fields, while phone and email details populate the Contact record.

ServiceTracker service-location addresses migrate into Freshsales Account address fields (Street, City, State, Zip, Country). Multiple service locations for one customer collapse to the primary site on the Account record with additional locations stored as custom fields. The mapping also captures the service location name and any site-specific notes in custom fields on the Account for reference. FlitStack AI stores additional locations as a comma-separated list in a custom field.

ServiceTracker work orders map to a custom Work_Order__c object in Freshsales linked to the Account. Each work order record preserves job type, status, scheduled date, technician assignment, and parts used. Recurring service contracts with revenue implications map to Opportunities if the contract has a dollar amount.

ServiceTracker service contracts with terms, renewal dates, and pricing migrate as a custom Service_Contract__c object linked to the Account. Contract value and billing frequency are stored as custom fields, preserving the original start and end dates for historical accuracy. Native renewal alerts do not transfer — Freshsales workflow rules must be configured post-migration. FlitStack AI exports the ServiceTracker renewal rule definitions as a reference document for your admin.

ServiceTracker technician records resolve by email match against Freshsales users. Unmatched technicians are flagged for admin review — the record can be stored as a Contact with a custom role field until a Freshsales user account is created for them.

Parts used on ServiceTracker work orders migrate as a custom Parts_Used__c object linked to the Work_Order__c custom object. Part name, SKU, quantity, and unit price stored as custom fields. Freshsales Product Catalog is separate and requires product records to be created for inventory parts.

ServiceTracker customer portal access credentials and portal preferences have no Freshsales equivalent. These are access-control constructs that must be rebuilt in Freshsales's self-service portal or managed outside the CRM. The mapping exports portal credentials and permission settings as a reference CSV for your admin to use during Freshsales self-service portal configuration. User roles from ServiceTracker can be mapped to Freshsales permission sets post-migration.

ServiceTracker service history entries — completed jobs, visits, and outcomes — migrate as Notes on the Account or as a custom Service_History__c object. Original timestamps and technician names are preserved. Dense history logs may be summarized to avoid record-volume inflation.

ServiceTracker dispatch board schedules and route-optimization outputs have no Freshsales equivalent. These are operational constructs that live outside the CRM data model. The raw data can be exported and referenced as historical records but cannot be reproduced in Freshsales. FlitStack AI exports dispatch schedules as a CSV file stored in Freshsales Files for audit purposes. Route-optimization data is exported separately for reference in external scheduling tools.

Inquiries captured by ServiceTracker forms that function as leads map directly to Freshsales Leads. The Source field is populated with 'ServiceTracker Website' for attribution tracking. Lifecycle stage is set to 'New' by default and can be updated via Freshsales workflow rules. Email address, phone number, and form-submitted comments transfer as standard lead fields. Lead scoring data from ServiceTracker is preserved in custom fields on the Freshsales Lead record.

ServiceTracker invoices with payment status and line items have no native Freshsales equivalent. Billing data can be stored as a custom object linked to Account, or referenced in Notes, but Freshsales does not include a billing or accounting module — financial records are better managed in QuickBooks or Xero.