Migrate from Filevine to Twenty CRM

Filevine contacts map directly to Twenty People. Each Filevine contact record — including name, email address, phone number, job title, and physical address — creates one corresponding Twenty People record. For contacts linked to multiple Filevine companies, we apply a primary company assignment rule to determine which companyId foreign key value is used when creating the Twenty record. The primary assignment ensures the most relevant company relationship is preserved in the migrated data without creating duplicate contact entries.

Filevine organizations map directly to Twenty Companies with a straightforward field-to-field translation. Company name, domain and website URL, industry classification, primary phone number, and complete address information translate directly without transformation. Parent-child company hierarchies established in Filevine — where a subsidiary company relates to a parent organization — map to Twenty's Company relation model using the parentId foreign key. We validate that all parent references resolve correctly before import to prevent orphaned subsidiary records.

Filevine projects (representing legal cases) map to Twenty Opportunities as the primary entity linking case data. Project name becomes the Opportunity name, project status values map to Twenty Opportunity stage picklist values, and the primary contact becomes the opportunity contact via Twenty's relation model linking to the People record. Law-firm-specific projects with extensive legal metadata may warrant a custom 'Case' object instead of the standard Opportunity object to better capture case-type specifics.

Filevine phase progressions (Intake → Discovery → Pre-Litigation → Settlement → Closed) do not exist as a native Twenty concept. We create a Phase_Current__c select field on the Opportunity object populated with the same stage values from Filevine. Phase-entered timestamps — recording when a case moved into each phase — are preserved as Phase_Entered_Date__c custom datetime fields to maintain historical stage progression records.

Filevine milestones map to Milestone__c select fields on the Opportunity object. Each milestone's descriptive text and scheduled due date are preserved in Milestone_Description__c and Milestone_Date__c fields respectively. Completed status for milestones is recorded as Milestone_Completed__c checkbox fields. Multiple milestones on a single project create a milestone history viewable through custom text area fields on the Opportunity record.

Filevine deadline chains — automatically populated dates that cascade from a trigger date — are converted to Twenty Tasks with due dates and assignees. Each deadline item within a chain becomes a Task linked to the parent Opportunity via the opportunityId foreign key. The chain logic itself (which deadlines cascade from which trigger date) is preserved as task relationship notes for manual rebuild in Twenty's workflow builder, since Twenty lacks native chain-dependency automation.

Filevine documents migrate as Twenty Notes with file attachments. The document name becomes the Note title, and file content is re-hosted as an attachment linked to the Note record. Filevine's Docs section metadata — including document type classification, Bates number, and Bates stamp status — is preserved in Note custom fields since Twenty has no native document management equivalent. The uploaded date translates to the Note createdAt timestamp.

Filevine custom sections created via Customs Editor are audited to determine migration strategy. Fields that map to standard Twenty objects (People, Company, Opportunity) become custom fields on those objects. Fields representing independent entities — such as Medical Record, Insurance Claim, or Witness Statement — may warrant Twenty custom objects with relations to the parent Opportunity rather than simple custom fields.

Filevine tasks and calendar events map to Twenty Tasks with subject line, detailed description, due date, assigned team member, and completion status preserved. Completed status and exact completion timestamps migrate to the completedAt field. Tasks linked to specific contacts or companies in Filevine carry those relationship IDs forward into Twenty through the contactId and companyId foreign keys on the Task record.

Filevine's Lead Docket — a separate lead tracking module distinct from case contacts — can map to a custom Lead_Tracker__c object linked to People records, or directly to People records with a Lead_Source__c custom field to indicate origin. The appropriate structure depends on whether leads and cases share a unified contact record in your data model. We recommend the custom object approach if leads maintain a distinct lifecycle from case contacts.

Filevine billing items including time entries, expenses, and flat fees are financial constructs with no direct Twenty CRM equivalent. Twenty has no billing, timekeeping, or invoicing capability. We preserve billing item data as Line_Items__c custom fields or a JSON blob on the Opportunity for historical audit reference, but active billing and invoicing workflows must be handled in a dedicated accounting system post-migration such as QuickBooks, Clio Billing, or LawPay.

Filevine tags applied to contacts, companies, and projects migrate to Twenty's tag system without transformation. Tags are preserved exactly as they appear in Filevine for searchability and filtering across Twenty's table view and kanban board visualization. Any tag hierarchies or tag groups defined in Filevine are maintained as flat tags in Twenty's tag management system. The tag string values themselves are not modified during migration to preserve data integrity and existing search patterns.

Filevine users are resolved by email address matching against Twenty Workspace Members. Each Filevine user record attempts to match by email to an existing Twenty workspace member. We flag any Filevine users without a corresponding Twenty account before migration begins so your team can send invitations and create accounts proactively. Records assigned to unresolved users default to a fallback Workspace Member designated during migration planning rather than failing the import.