Migrate from Lime CRM to Twenty CRM

Lime CRM Company records (sometimes called Account in certain industry variants) map directly to Twenty CRM Company. Standard fields including name, address, industry, website, and phone transfer cleanly. We use company name as the dedupe key during import. Company must be imported before any Person record that references it, because the Company record must exist to satisfy the Person's companyLink relationship.

Lime CRM Contact records map to Twenty CRM Person. Name fields, email address, phone numbers, and any standard contact properties transfer directly. We normalise phone number formats during transformation to prevent the leading-zero stripping that commonly occurs with international numbers during CSV import. Person records are imported after Company records so that the company relationship can be resolved at import time rather than through a post-import reconciliation pass.

Lime CRM Deals map to Twenty CRM Opportunity. The dealstage property maps to the destination StageName, and pipeline assignments map to Twenty pipeline stages that we configure during workspace preparation. Deal value, expected close date, owner, and associated Company and Contact relationships all transfer. Closed-won and closed-lost reasons from Lime CRM custom fields become Opportunity custom fields in Twenty.

Lime CRM's Limetypes have no canonical schema across tenants. During discovery, we export the live Limetype definition from the customer's Lime CRM admin and document every property including field name, data type, relation type (BelongsTo, HasMany), and any custom validation. Each Limetype maps to a Twenty CRM Custom Object created via Settings → Data Model before import. Properties with BelongsTo relations resolve to existing Company or Person records; HasMany relations are created after the parent record exists. This mapping phase is the primary driver of timeline for complex Lime CRM tenants.

Lime CRM Activities representing logged calls, meetings, tasks, and notes attached to a Contact or Deal migrate to Twenty CRM as Task or Note records. Call records map with TaskSubtype preserved. Meeting records with start and end times map to Task with the time preserved. Notes with rich text content map to Note records. Each record carries a link back to the parent Person or Opportunity, and the ActivityDate timestamp is preserved for timeline ordering.

Lime CRM exports email conversations as individual ConversationMessage files rather than threaded records. We detect this at scoping, reassemble threads by conversation ID and timestamp during the transformation phase, and inject them into Twenty CRM as a unified activity record per thread rather than per message. Sender, recipient, subject, body, and timestamp are preserved. This transformation step is unique to Lime CRM migrations and is applied before any CSV is presented to Twenty's import tool.

Lime CRM Ticket records migrate to Twenty CRM as Task records with a support-type classification and associated status values. Ticket pipeline stages map to Task status values, priority transfers to Priority, and assignee resolves by email match against Twenty workspace members. Ticket conversation history is processed through the email thread reassembly logic and imported as related activity records linked to the Task.

Lime CRM attachments are downloaded individually per record without bulk export support in the base tier. We batch download all attachment files, validate file integrity against the export manifest (catching any truncated or missing files before the destination import begins), and rename files to preserve the parent record relationship. Files exceeding 25 MB are flagged for manual handling because they may require chunked upload or a direct storage migration approach. The Twenty import CSV references the attachment path so records display their linked files after migration.

Tags from Lime CRM (applied to Contacts, Deals, and Tickets) export as a flat list per record. We preserve the tag taxonomy as a flat list and recreate tag values in Twenty. The customer chooses whether to apply tags as direct values or to use Twenty's Topics feature during scoping. Tag inheritance across object types is noted and handled per the destination's tagging model.

Lime CRM User records and Deal owners resolve by email match against Twenty CRM workspace members. We validate that a destination member exists for every owner referenced in the migration before importing Opportunities and Activities, because owner resolution is required for Activity assignment. Users without a matching Twenty member enter a reconciliation queue for the customer's admin to provision before the migration resumes.

Lime CRM Documents with auto-fill templates export as document blobs with metadata. The document blob migrates as a file attachment to the related Person or Opportunity. Template auto-fill field mappings require manual reconstruction in Twenty because template logic does not export in transferable format. We document the template structure during discovery for the customer's admin to rebuild using Twenty's document capabilities or a third-party document tool.

Lime CRM workflow automations (ticket assignment rules, follow-up triggers, status change alerts) cannot be exported as machine-readable files. We capture the automation logic from the Lime CRM UI during discovery, document each rule's trigger, conditions, and actions, and deliver a written inventory for reconstruction in Twenty's workflow builder. Complex multi-step flows requiring branching logic, time-based delays, or cross-object triggers require manual reconfiguration by the customer's admin or a consultant engagement.