Migrate from LEAP to Twenty CRM

LEAP contact records map directly to Twenty People objects. Each contact's primary client/matter link becomes a relation field pointing to the mapped Company record. Multi-contact matters where multiple contacts share one client require a Company record to exist first so the contact-company foreign key resolves correctly during import.

LEAP client records become Twenty Companies. The client name maps to Company name, and LEAP client type or industry classification maps to a custom select field on the Company if Twenty's default industry list does not cover your classification. Parent-child client hierarchies translate to a Company relation field pointing to the parent Company record.

LEAP matter records map to Twenty Opportunities since both represent deal or case tracking. Matter name becomes Opportunity name, and the matter description or summary field becomes the Opportunity description. LEAP matter status values map to Opportunity stage values via value-by-value correspondence defined in the migration plan before import.

LEAP matter stage values (e.g., Intake, In Progress, Pending Review, Closed) map one-to-one to Twenty Opportunity stage pick-list values. Each LEAP stage gets a corresponding stage in Twenty's Data Model stage definition. Stage-entered timestamps from LEAP preserve as custom datetime fields on the Opportunity since Twenty does not natively track stage transition timestamps.

LEAP time entries do not have a native equivalent in Twenty's standard model. We create a TimeEntry custom object in Twenty with fields for date, duration, description, linked Person, and linked Opportunity. This preserves billable hour history for reporting continuity, though the rebuild of billing workflows in Twenty falls outside migration scope.

LEAP documents associated with matters are exported as files and re-hosted as Twenty Notes with file attachments. The note body captures the document description from LEAP, and the file attachment re-upload uses Twenty's file storage. Large document volumes may require batched import to stay within per-file size limits.

LEAP activities logged against matters (calls, emails, meetings) map to Twenty Tasks attached to the related People or Opportunity record. Original activity timestamps, type (call, email, meeting), and owner email are preserved as Task fields. Activity type becomes a Task custom select field since Twenty Tasks do not natively distinguish call versus email subtypes.

LEAP custom fields created per contact, client, or matter require pre-creation in Twenty's Settings > Data Model before the migration CSV loads. We deliver a custom field manifest listing each LEAP custom field, its data type, and the Twenty field type that best fits (text, number, select, multi-select, date, etc.). Fields must exist in Twenty first — the CSV import creates records, not schema.

LEAP user and staff records map to Twenty Workspace Members. Owner assignment on migrated records resolves by email match — the LEAP user email must correspond to an accepted Twenty workspace invitation. Unmatched users surface as a pre-flight flag so your team can invite them before the migration commits.

LEAP's trust accounting records do not map to standard Twenty objects. We create a TrustEntry custom object with fields for transaction type, amount, date, client relation, and description. This preserves the trust ledger history for compliance and audit purposes. Trust workflow rules require manual configuration in Twenty.