Migrate from Lemon Tech to Twenty CRM

Lemon Tech's core data container. Both standard and custom entities export via the Entity export function as structured relational tables. We map each entity type to a Twenty Custom Object using the /metadata API to pre-create the object schema with matching fields before any data insert. Custom entity field names are normalized from whatever convention the firm used (camelCase, snake_case, or spaces) to a consistent format; the original names are preserved in a metadata field for auditability. SQL Wrapper-defined entities require manual field mapping during discovery because the join logic and computed columns must be flattened into flat record fields before migration.

Standard Lemon Tech Contact records with name, email, phone, and address fields export cleanly and map directly to Twenty Person. Custom contact properties (firm-specific fields added through Lemon Tech's custom entity or contact property system) map to custom fields on the Person object, pre-created via Twenty's /metadata API before import. Email address serves as the dedupe key during insert.

Lemon Tech Entities classified as Companies export with name, domain, address, and industry fields. These map directly to Twenty Company records. If Lemon Tech stores organization type in a custom field rather than as a dedicated entity type, that field maps to a custom field on the Company object. Company records are imported before Person records so that the Person-Company relationship (stored as a workspaceMember field or custom relation field in Twenty) is resolved at insert time.

Matters are Lemon Tech's primary case and project container, storing practice area, responsible attorney, status, dates, and billing reference. We map Matters to Twenty Opportunity records and preserve the practice area as a custom picklist field on the Opportunity. Matter status (active, closed, archived) maps to Twenty Opportunity stage values that we configure in Settings before migration. Custom Matter fields map to custom Opportunity fields pre-created via /metadata.

Some Lemon Tech firms store practice-area-specific data (court details, opposing counsel, filing deadlines, lien information) as sub-entities or custom fields on Matter rather than as a flat set of Matter properties. We split these into a separate custom object in Twenty with a lookup relationship back to the Opportunity, preserving the hierarchy that the practice-area sub-entity represented in Lemon Tech.

Lemon Tech User records with name, email, and role information map to Twenty WorkspaceMember. We resolve users by email match against the Twenty workspace. Any Lemon Tech User without a matching Twenty WorkspaceMember goes to a reconciliation queue for the customer to provision before record import resumes, because OwnerId references on Opportunities and custom object records require a valid workspace member to exist first.

File attachments associated with Lemon Tech entities or Matters export as binary blobs. We handle these separately from record data, preserving filenames, parent record associations (entity ID, matter ID), and upload timestamps. In Twenty, attachments link to the target record (Person, Company, or Opportunity) via the standard attachment relationship. Very large file sets require staged export batches to avoid timeout in Lemon Tech's export function.

Simple SQL Wrappers that export Lemon Tech data as a flat table (no multi-table joins, no computed columns, no external data sources) migrate as standard custom object records in Twenty. We map the wrapper output fields to a custom object schema pre-created via /metadata, flatten the table structure to one record per row, and insert via Twenty's GraphQL /graphql endpoint.

Complex SQL Wrappers with multi-table joins, computed columns, or third-party data require manual field mapping during discovery. We inventory every complex wrapper definition, identify which source tables feed each computed column, and design a set of Twenty custom objects that reproduce the flattened output. The business logic (join conditions, calculation formulas) does not migrate; we document the wrapper definition for the customer's admin to reconstruct as a reporting pipeline in a BI tool post-migration.

Time entries and billing records linked to Matters in Lemon Tech export via the Entity export with billable amount, date, contact reference, and matter reference. We map these to custom fields on the parent Twenty Opportunity: billable_amount__c, time_entry_date__c, and a lookup to the linked Person record. If the firm requires granular time-entry-level records rather than rolled-up billing fields, we create a separate custom TimeEntry object with a lookup to Opportunity and map the entries accordingly.