Migrate from InfoTrack to Freshsales

InfoTrack contacts are stored as parties attached to a matter. They map directly to Freshsales Contacts. Each contact's email, phone, name, and address fields translate 1:1. If the contact has no associated company in InfoTrack, it lands as a Contact with no AccountId link in Freshsales — your team can link it manually or via a post-migration merge.

InfoTrack contacts that are not tied to an open matter (prospective clients, referrals without a filed case) route to Freshsales Leads rather than Contacts. Split happens during migration based on the presence of a matter link in the source record. Lead source defaults to 'InfoTrack Import' for traceability.

InfoTrack company entities map to Freshsales Accounts. Company name, domain, industry, and employee-count fields map directly. If a company is listed as the opposing party or co-counsel, it lands as an Account — your team assigns the Account type in Freshsales to distinguish client companies from opposing counsel.

InfoTrack matters (cases) become Freshsales Deals. The matter name maps to Deal name, and the matter's estimated value or billing amount maps to Deal amount. Matter status (Active, Closed, Pending) maps to Freshsales Deal stage via value mapping. Court name, case number, and matter type are stored as custom text fields on the Deal record.

InfoTrack matter status values (e.g., Active, Pending Court, Closed) map to Freshsales Deal Stage values via a value-by-value table. 'Closed Won' maps to InfoTrack's 'Closed — Served'; 'Closed Lost' maps to 'Closed — Unsuccessful'. Stage probabilities are set per Freshsales pipeline configuration.

InfoTrack documents attached to a matter migrate as Freshsales Notes on the linked Deal record, with the file itself re-uploaded as a Freshsales File attachment. Document type (e.g., 'Motion Filed', 'Stipulation') is stored in the Note title or a custom field. Inline images in PDF documents are extracted and re-hosted as attachments. Original upload timestamps are preserved in the Note body or a custom datetime field.

InfoTrack process-serving orders (ServeIT records) become Freshsales Tasks on the related Deal. Task subject captures the service order description, and the task status mirrors the InfoTrack service status (Attempted, Served, Non-Service). Process server details are stored as custom text fields on the task record since Freshsales has no native process-server entity.

InfoTrack e-filing orders become Freshsales Tasks with a custom sub-type field ('E-Filing'). The filing court and case number reference the parent Deal's custom fields. Order status (Submitted, Accepted, Rejected) maps to task status. E-filing fees from InfoTrack are recorded as a custom currency field on the task.

InfoTrack generates per-order invoices tied to matter billing. These invoice line items do not map to any native Freshsales object. We store the most recent invoice total as a custom currency field on the Deal and preserve the full invoice history as a CSV attachment for reference. Recreating billing as Freshsales Products requires a separate configuration step.

InfoTrack users and staff members are matched to Freshsales users by email address. Unmatched users are flagged before migration — your team either creates the Freshsales user first or assigns their InfoTrack records to a fallback owner. User roles and permissions do not transfer and must be configured in Freshsales' role settings.

InfoTrack allows firms to configure custom properties on matters. Each custom property is evaluated: pick-list types map to Freshsales custom pick-list fields; date types map to custom date fields; text types map to custom text fields. All custom fields are created in Freshsales before the migration run using the Freshsales Settings API.

InfoTrack stores IDs from integrated platforms (Clio, LEAP) as reference metadata on a matter. These external system IDs are preserved as custom text fields on the Deal record (e.g., External_Source_ID__c) for reconciliation and future integration rebuilding. This allows your team to cross-reference records between systems, audit data consistency, and re-establish connections with integrated tools without manual data entry.