Migrate from Jarvis Legal to Twenty CRM

JARVIS matter-stage model has no native equivalent in Twenty's Opportunity pipeline

JARVIS tracks matter lifecycle through custom statuses and stages that are defined per-firm. Twenty CRM's Opportunities use a stage pick-list that is flat across all Opportunity records—Twenty does not have a matter-stage concept natively. JARVIS matter status values must be mapped to Twenty Opportunity stage values value-by-value, and any firm-specific matter phases that don't match Twenty's stage names need custom field creation. If your JARVIS setup uses more than three matter types (e.g., Litigation, Corporate, Family Law) each with their own status workflow, each matter type may require its own custom pick-list field rather than relying on the native stage field.

Twenty's strict import ordering requirement breaks if Companies are not migrated first

Twenty's CSV import mechanism requires that the 'one' side of all relationships exist before importing the 'many' side. Specifically, Companies must be imported before People (which reference companyId), and both must exist before Opportunities are imported (which also reference companyId). JARVIS does not enforce this ordering—matters and contacts can be created simultaneously. FlitStack AI sequences the migration to resolve foreign-key dependencies before loading, but if your JARVIS data has People records with company references that have no matching JARVIS organization record, those contacts land as orphaned People in Twenty and must be manually linked post-migration.

JARVIS trust accounting and invoice ledger cannot be represented in Twenty's data model

JARVIS Legal includes trust accounting (IOLTA-style client fund tracking) and a full invoice generation system tied to matter records. Twenty CRM has no native accounting, billing, or trust accounting objects. The invoice total and status can be preserved as custom fields on the Opportunity, but the full invoice line-item history, trust balance, and payment records do not map to any Twenty object. These records must be preserved in a PDF export from JARVIS or migrated to a dedicated accounting tool. FlitStack AI will flag all JARVIS financial records during the data audit and confirm which records can be preserved as Notes versus which must be exported separately.

Twenty's 20,000-record CSV export limit can split JARVIS matter exports

Twenty's export function is capped at 20,000 records per export operation. Most JARVIS Legal instances for small-to-mid firms fall below this threshold, but firms with high matter counts or extensive activity histories may need multiple export passes. The 100 requests/minute API rate limit on Twenty's Pro plan also constrains automated migration throughput—large document re-uploads may require batched processing. FlitStack AI will scope the record count during discovery and confirm whether multiple export passes or extended runtime are needed before the migration begins.

JARVIS document version history collapses to latest version in Twenty file storage

JARVIS Legal tracks document version history for matters—each revision of a contract or filing is stored separately. Twenty's file storage model supports one file attachment per record without native version tracking. FlitStack AI migrates the latest version of each document and stores the complete version history as a custom Note attached to the document record, listing the version number and date for each revision. If your practice relies on accessing prior document versions directly from the CRM record, this representation requires a workflow adjustment in Twenty.