Migrate your Filevine data

Projects are Filevine's core case/matter object. The migration spreadsheet format accepts Projects as the primary import unit. We map standard project fields (status, phase, assigned user) directly. Custom Sections and Vitals require per-firm field mapping against the Customs Editor schema.

Contacts migrate via the Contacts spreadsheet with standard fields (name, phone, email, company). Custom contact properties map 1:1 where the destination system supports them, or we preserve them as custom properties on the linked Project.

Custom fields added via the Customs Editor vary by firm in both name and field type (text, date, dropdown, yes/no, ProjectLink, etc.). We catalog all custom fields during scoping, resolve field-type incompatibilities with the destination, and map field values explicitly.

Phases represent stage-based milestones within a Project. Migration preserves phase names and ordering. Where the destination uses a different pipeline-stage model, we map phases to the closest equivalent and flag any custom phase logic for manual review.

Deadline Chains auto-populate calendar dates from a trigger date. Migration preserves the chain template structure and any linked dates. We flag any chain templates that reference system IDs rather than human-readable names.

Filevine's Docs+ module stores documents with Bates Stamping, PDF Editor, Doc Combiner, and OCR. We export documents from the Docs section preserving metadata. Filevine does not auto-categorize documents on import, so flat document lists require optional manual categorization post-migration.

Billing items have three types: time entries, expenses, and flat fee items. Each has associated ItemType codes and Billable/Chargeable flags. We extract all three types from the billing migration spreadsheet. Flat fee billing logic does not transfer and must be rebuilt in the destination.

Filevine's phase-based task workflows are defined within the Customs Editor per-project template. There is no export mechanism for workflow definitions. All automations must be manually rebuilt on the destination platform.

Collections hold structured datasets such as evidence lists and medical chronologies. The Collection Exports feature generates normalized views from these records. We extract collection data via the API, mapping custom collection field schemas to the destination object model.

Time entries are a billing item type tied to TimeCode fields. We extract time entries with their associated codes and hours. Time entry-to-user assignments are preserved as Owner/User properties in the destination.

Vitals are key-value indicators displayed on the Project card and within sections. Migration preserves vitals as custom project fields. Where vitals reference other records (ProjectLinks), we resolve cross-project references during mapping.

Flex Sections control visibility of sections and phases per project type. Migration of flex section visibility rules requires mapping Filevine's visibility flags (initially visible, always visible, initially hidden, always hidden) to the destination's equivalent conditional display logic.