Migrate from Filevine to Salesforce Sales Cloud

Filevine People map directly to Salesforce Contact when they represent active clients or firm contacts. Email, phone, job title, and address fields translate field-for-field. People with 'Lead' status (prospective clients, referrals) route to Salesforce Lead instead.

Filevine People flagged as prospective or unconverted route to Salesforce Lead. Lead Status pick-list maps from Filevine's person status field. Conversion to Contact happens manually post-migration or via Salesforce lead conversion rules.

Filevine Organizations (firms, opposing parties, courts) map to Salesforce Account. Name, website, type, employee count, and annual revenue carry over. Parent organization hierarchy in Filevine maps to Salesforce ParentId on Account.

Filevine Projects map to Salesforce Opportunity if the firm tracks revenue-per-case. For non-revenue legal matters, we create a custom Matter__c object with fields for case type, court venue, statute of limitations, and project status. The mapping decision is made during the sample migration review.

Filevine Sections are custom containers holding phase data and custom fields. Each Section field maps to a Salesforce custom field on the target object. Multi-value custom fields require concatenation or custom junction objects in Salesforce since there is no direct section-scoped equivalent.

Filevine Phase names map to a custom pick-list field (Phase__c) on Opportunity, or to Opportunity StageName if the firm uses stages to represent case phases. Each Filevine phase value requires explicit value mapping to the Salesforce pick-list value set.

Filevine Deadlines map to Salesforce Task. Subject, due date, assigned user, priority, and completion status translate field-for-field. Deadline type (filing, court date, client meeting) migrates as a custom pick-list field (Deadline_Type__c) on Task.

Filevine Deadline Chains generate cascading tasks from a single anchor date. We export the full chain as individual Tasks linked by a custom Deadline_Chain_ID__c field. The chain configuration (template name, interval rules) is stored in a custom Chain_Config__c field for admin reference during Salesforce Flow rebuild.

Filevine Documents map to Salesforce Files (ContentDocument/ContentVersion). File name, type, size, and uploaded date carry over as custom metadata fields since Salesforce Files do not store these natively. The file binary is downloaded from Filevine storage and re-uploaded to Salesforce.

Filevine billing items have three types (time entry, expense, flat fee) with status and attribution. There is no Salesforce standard equivalent. We create a Billing_Item__c custom object linked to the target Project/Opportunity, with fields for item type, name, amount, status, and date.

Filevine associates People with Projects via Project Links (with role labels like 'Attorney', 'Paralegal', 'Client'). We map these to a custom Project_Role__c junction object linking Contact to Matter__c, preserving the role label as a pick-list field. Multiple roles per person require separate junction records.

Filevine Enterprise allows custom objects (Pipelines, custom entity types). These map 1:1 to Salesforce custom objects with the __c suffix. Filevine's custom object associations (N:N via Project Links) require Salesforce junction objects when the relationship is many-to-many.

Filevine Vitals are project-level fields that surface on the project header (court, judge, venue, statute of limitations). These migrate as custom fields on the Matter__c or Opportunity object. Standard Salesforce fields (Account, CloseDate) are used where the semantic match is exact.

Filevine file attachments re-upload to Salesforce Files (ContentDocument). File size limits apply (Salesforce default 25MB per file; large files require chunked upload or Files Connect to external storage). Inline images in notes are downloaded and rehosted in Salesforce.