Migrate from FilePro to Salesforce Sales Cloud

FilePro clients are organizations or individuals who matter records attach to. They map directly to Salesforce Accounts. The Account.Name field holds the client name; FilePro client-type flags (individual vs. organization) determine whether a secondary Contact record is needed in Salesforce.

Individual contacts at a FilePro client firm map to Salesforce Contacts. A Contact's AccountId links to the parent Account. FilePro allows multiple contacts per client; Salesforce supports N contacts per Account via Account Contact Relations for additional associations beyond the primary.

FilePro matters (cases, files, engagements) map to Salesforce Opportunities when the firm uses matter-based billing analogous to deal tracking. The Opportunity.Name maps from Matter.description; Opportunity.Amount maps from the estimated matter value or billing budget field. StageName maps from Matter.status pick-list via value mapping.

For firms where Salesforce Opportunities do not represent the legal matter structure (e.g., matters are non-revenue or contain non-standard fields), we create a Matter__c custom object. Matter__c fields replicate the FilePro matter record; the custom object requires a junction object if each matter can involve multiple contacts beyond the primary attorney.

Billable hours logged in FilePro migrate as Salesforce Tasks with Task.Type='Time Entry'. The Task.Subject carries the matter reference; Task.DurationInMinutes carries the billed time converted from hours. Original billing rate and billable/non-billable flags migrate as custom fields on the Task for reporting continuity. Each Task is linked to its parent matter via WhatId pointing to the resolved Opportunity or Matter__c record.

FilePro documents linked to matters or clients export as binary files and re-upload as Salesforce Files. Each file becomes a ContentVersion record; a ContentDocumentLink associates it with the parent Account, Contact, or Matter__c record. Files over 25MB must be split or stored in an external DMS with a hyperlink stored in Salesforce.

FilePro User Defined Fields on the Client table create Salesforce custom fields on Account with __c suffix. Field types map: text fields to Text(255), numeric fields to Number, date fields to Date. Pick-list UDFs map to Salesforce pick-lists with value mapping. FLS must be configured per profile after field creation.

Matter-level UDFs create custom fields on the target object (Opportunity or Matter__c). Multi-select pick-lists in FilePro map to Salesforce multi-select pick-lists. Very-long-text UDFs map to Long Text Area fields with appropriate length. All custom fields require Field Level Security before data loads.

FilePro attorney and staff records are resolved to Salesforce Users by email address match. Records without a matched user are flagged for fallback assignment. Salesforce OwnerId is set on Account, Contact, Opportunity, and Task records during migration. Unmatched owners require either a Salesforce user invitation or reassignment to a default user.

FilePro billing records (invoices, disbursements, trust entries) have no direct Salesforce CRM equivalent. We preserve billing totals, outstanding amounts, and payment status as custom fields on the Matter__c object. Full invoice history requires a legal billing AppExchange package — we provide a rebuild reference document for your admin.

FilePro client classification codes (e.g., 'Corporate', 'Private Client', 'Government') map to a custom Account.Client_Type__c pick-list. Each value is mapped value-by-value from FilePro's code table, preserving the firm's classification hierarchy. Unmapped codes are flagged for admin review before migration commits, allowing your team to decide whether to add missing values or adjust the classification scheme in Salesforce.

FilePro matter status values (e.g., 'Open', 'Billing', 'Closed', 'On Hold') map to Salesforce Opportunity Stage values. We apply a value-mapping table per matter type. Stage probability and forecast category are re-applied based on Salesforce's stage configuration in the target org.

Salesforce's CreatedDate and LastModifiedDate are set by the platform at migration time and reflect when records are loaded, not the original FilePro entry dates. We preserve the original FilePro record creation and modification timestamps as custom datetime fields (Original_Create_Date__c, Original_Modified_Date__c) on each object for reporting continuity, audit purposes, and historical analysis of matter timelines.

The original FilePro record identifier is stored as Source_System_ID__c on each migrated Salesforce record. This field serves as the External ID for delta-run de-duplication, prevents duplicate inserts on re-migration, and enables full traceability between the source FilePro database and the Salesforce org for reconciliation and audit purposes.