Migrate from Filevine to Microsoft Dynamics 365 Sales

Filevine People map 1:1 to Dynamics 365 Contacts. Name, email, phone, address, and job title carry over directly. Filevine's 'People Type' (Attorney, Client, Opposing Counsel, etc.) is preserved as a custom OptionSet field on the Contact record since Dynamics has no native person-type taxonomy.

Filevine People records that have not yet opened a matter are tagged as prospective clients. We route these to Dynamics Leads by default, and all active-client People records map to Contacts. A pre-migration flag identifies which Filevine People have open Projects so the split is accurate.

Filevine Firms (organization records) map directly to Dynamics 365 Accounts. Firm name, domain/website, address, industry, and employee count transfer to the corresponding Account fields. Filevine parent-child firm hierarchies map to Account.ParentId in Dynamics, preserving referral relationships and multi-office structures.

Filevine Projects (legal matters) translate to Dynamics Opportunities when the matter has an associated fee arrangement or contingency value. The Project name becomes the Opportunity name, and the Project's financial fields (billing type, estimated value, flat fee) map to Opportunity.Amount. When no financial value exists, we create a custom 'Cases' Dataverse table to preserve the matter record without inflating pipeline forecasts.

Filevine phase names and phase-entry timestamps map to Opportunity stage changes with original dates preserved in custom datetime fields (Phase_Entered__c). Each Filevine pipeline becomes a Dynamics Sales Process; phase names map value-by-value to stage names under that process. If your firm uses multiple pipelines in Filevine (e.g., Litigation vs. Personal Injury), we create separate Sales Processes per pipeline.

Filevine's per-matter custom sections (e.g., 'Medical Records', 'Insurance Info', 'Expert Witnesses') hold fields that vary by matter type. We audit every active section template before migration, create matching Dataverse columns for each field (with correct type — text, option set, integer, decimal, datetime, boolean), and map field values during the migration run. Fields with no Dynamics equivalent are preserved as custom fields with a 'FV_SourceField__c' naming convention.

Filevine deadline chains generate calendar tasks in Dynamics. Each deadline record becomes a Task entity with the deadline date in Task.ScheduledEnd, the responsible Filevine user mapped to Task.OwnerId by email match, and the deadline description in Task.Subject. Chain templates (e.g., '30-day response window') are exported as a reference document for rebuilding Power Automate flows post-migration.

Filevine documents and uploads are downloaded from Filevine's storage and re-uploaded to the connected SharePoint or OneDrive for Business location configured in your Dynamics environment. The document is then attached to the corresponding Opportunity or Case record via the SharePoint document location entity. Inline images in Filevine notes are extracted and re-hosted as SharePoint assets.

Dynamics 365 Sales has no native billing item entity. We export all time entries, expenses, and flat fees as a structured JSON file and attach it to the corresponding Matter/Opportunity record. For firms that need live billing sync, we recommend integrating Dynamics 365 Business Central (which has full billing and time-tracking modules) post-migration, using the JSON summary as the initial data load.

Vinesign signature records include signers, timestamps, and document IDs. We export these as Note entities attached to the relevant Project record. Vinesign templates cannot migrate; we provide a template audit document so your team can rebuild templates in DocuSign, HelloSign, or Templafy.

Filevine DocGen templates are document-generation workflows that pull Filevine field values into Word/PDF/Excel. Dynamics has no native DocGen. We export the full list of active DocGen templates with their field mappings as a rebuild reference. Rebuild typically uses Power Automate with the Word Online (Business) connector and a SharePoint template library.

Filevine staff records map to Dynamics 365 SystemUser by email address. We perform an email-match lookup against your existing Dynamics users before migration. Unmatched Filevine staff are flagged so your Dynamics admin can create user accounts before the final migration run. Archived/inactive Filevine users are imported as inactive SystemUsers with a deactivation flag.