Migrate from FieldFX to Freshsales

FieldFX stores person-level records as Salesforce Contacts under Account lookup. These map 1:1 to Freshsales Contacts. Owner resolution uses email match against Freshsales users, with case-insensitive comparison and domain normalization. Unmatched owners are flagged before migration commits, and duplicate contacts based on identical email are merged or retained per your deduplication preference.

Salesforce Account in FieldFX maps directly to Freshsales Account. Parent Account hierarchies (if used) are preserved using Freshsales Account's hierarchical relationship, maintaining the same parent-child chain. Multi-company contacts in FieldFX collapse to a primary Account per contact, with secondary contacts linked via custom relationship fields to avoid duplicate Account records. Billing and shipping addresses are copied as-is.

FieldFX Work Orders represent field-service jobs with status, priority, scheduled date, assigned technician, and line items. These map to Freshsales Deals — Work Order Name becomes Deal name, status maps to pipeline stage, and the Work Order's associated Account resolves to Freshsales AccountId before the Deal is created.

Each Work Order Line Item (part number, quantity, labor hours, extended amount) maps to a Freshsales Deal Product. Product records are created in Freshsales from FieldFX line-item part numbers if matching products don't already exist. Line-item discount and tax fields require custom field mapping in Freshsales.

FieldFX Tickets are support-request or issue-tracking records linked to Work Orders. Tickets that represent pre-sale service quotes route to Freshsales Deals with a separate pipeline; operational tickets that represent post-sale service records route to a Freshsales custom Deals pipeline with a 'Service' tag. The split is driven by Ticket record type in FieldFX.

FieldFX Ticket attachments — PDFs of service reports, photos, signature captures — are downloaded and re-uploaded to Freshsales Files linked to the corresponding Deal record. File naming preserves the original Ticket and Work Order identifiers for traceability. File size limits apply (Freshsales default 25MB per file); larger files are split or linked externally. Duplicate attachments are identified by hash and consolidated to avoid redundant uploads.

FieldFX Quotes in the FX CPQ module (if present) map to Freshsales Deals with a 'Proposal' pipeline. Quote line items map to Deal Products using the same transformation as Work Order Line Items. Quote expiration dates map to Freshsales Deal close dates for the proposal.

FieldFX activity records (scheduled technician visits, service completion tasks) map to Freshsales Tasks. Completed events map to Freshsales Events with original start/end times preserved, including duration and time-zone offsets. Parent Work Order ID is preserved in a custom field on the Task for traceability, and any associated notes or comments are migrated as Task Description attachments.

FieldFX users (technicians, dispatchers) are Salesforce users. Resolution is by email match to Freshsales users, with case-insensitive comparison and domain stripping. Inactive Salesforce users in FieldFX are skipped; their Work Orders are reassigned to the matched Freshsales user or a migration fallback owner designated by your admin. User mapping is logged for post-migration review.

FieldFX custom fields (dispatch status, site location, technician certification, service-type codes) are created as Freshsales custom fields on the corresponding object. Field types are mapped: pick-list → pick-list, text → text, number → number, date → date. Custom fields without Freshsales equivalents are created as text fields for reference.

FieldFX Status Workflows define the sequence of allowable status transitions per record type. Freshsales Workflow automator handles assignment and field updates but does not replicate Salesforce Flow-based status workflows. We export the FieldFX status workflow definitions as a reference document for your Freshsales admin to rebuild in the Freshsales Workflow builder.

FieldFX Schedule & Dispatch module manages technician scheduling, route optimization, and travel-time calculations. Freshsales has no native scheduling or dispatch module. These records (technician assignments, route data, travel-time logs) are exported as a CSV reference for teams that choose to implement a dedicated scheduling tool alongside Freshsales.

DataGuide form templates and form response records (inspection data, compliance forms, signature captures) are not migratable to Freshsales. We export DataGuide form definitions and response data as structured JSON and CSV for reference, so your team can evaluate Freshworks' Freshdesk Forms or third-party form tools for replacement.