Migrate from FilePro to Freshsales

FilePro client records map directly to Freshsales Accounts. Each client organization or individual becomes one Account record. Business clients with multiple contacts produce an Account with multiple linked Contact records. We resolve FilePro client IDs to Freshsales Account IDs for downstream matter-to-deal linking.

FilePro clients that are individual persons rather than organizations become Freshsales Contact records without a parent Account in Freshsales. For solo-practice configurations, these individual contacts may optionally be linked to a designated default Account record that represents the practice entity. Email addresses, phone numbers, and physical address fields map directly from FilePro contact fields to Freshsales Contact fields without transformation.

Every FilePro matter becomes one Freshsales Deal. The matter number migrates as a custom field (Matter_Number__c) and the matter title becomes the Deal Name. The matter status field maps to Freshsales deal stage via a value-mapping table. Because FilePro has no native stage model, we propose a three-stage Freshsales pipeline: Open (active matters), Pending (matters awaiting action), Closed (resolved or archived).

FilePro stores multiple parties per matter (opposing counsel, witnesses, judges, third parties). Each unique party becomes a Contact in Freshsales. The matter-Deal-to-Contact association uses Freshsales' native deal contact linking. Where parties represent organizations, we also create Account records and link them via Account Contact Relationships.

Every user-defined field on a FilePro matter produces a corresponding custom field on the Freshsales Deal object. Field type is inferred from the exported data — numeric values become Number fields, dates become Date fields, encoded pick-list values become Picklist fields with value mapping. The custom field is created in Freshsales before migration runs.

FilePro time entries (date, duration, description, billing rate) are grouped by matter and stored in a Freshsales custom object linked to the parent Deal. This preserves historical billing context without overloading the standard Deal object. Billing amounts do not flow into Freshsales financial modules — that is a rebuild decision on the destination side.

FilePro document references and file attachments are rehosted into Freshsales Files attached to the corresponding Deal. Large files (over 25MB) are flagged for chunked upload. Inline document links in FilePro notes are converted to Freshsales file attachments with a reference link stored in the note body.

FilePro notes and memos attached to matters migrate as Freshsales Notes on the corresponding Deal. Original creation and modification timestamps are preserved from the source matter record. Any rich-text formatting, embedded images, or proprietary encoding found in FilePro notes is stripped and converted to plain text where necessary to comply with Freshsales note field constraints and character limits.

FilePro staff and user IDs are resolved by email address against Freshsales users. Unmatched FilePro users are flagged before migration and assigned to a fallback Freshsales user. Only active staff with matters in scope are migrated — the rest are noted in the migration plan for manual assignment.

FilePro trust account balances and billing standing linked to clients do not map to any Freshsales native field. We create custom text fields on the Account record (Trust_Balance__c, Billing_Status__c) for reference. Financial settlement logic must be handled outside Freshsales in a dedicated billing system.