Migrate from Lime Go to Twenty CRM

Lime Go Customers (the primary account-level records storing company data, metadata, and custom fields) map directly to Twenty CRM Company records. The Customer name becomes Company name, and all custom fields on the Customer record are discovered during scoping and mapped to Twenty CRM Company custom fields. Tags applied to the Customer transfer as label arrays on the Company record. We preserve the Customer ID as a custom reference field for audit traceability.

Lime Go Contacts (individual people linked to Customers) map to Twenty CRM Contact records. We preserve email, phone, custom properties, owner assignment, and GDPR consent flags. Each Contact's link to its parent Customer becomes the Twenty CRM Contact-to-Company relationship via the companyId field. Consent history (granted, withdrawn, timestamps) transfers as a custom JSON field or series of custom date and boolean fields on the Contact record.

Lime Go pipelines with configurable stages map to Twenty CRM Pipeline configurations. Stage names, order, and probability percentages transfer as-is. Each Lime Go pipeline becomes a distinct Twenty CRM Pipeline with its own stage set. Pipeline probability settings map to stage weights in Twenty.

Lime Go Deals (linked to Customers and Pipeline Stages) map to Twenty CRM Opportunity records. Deal value, expected close date, owner, and custom fields transfer directly. The Lime Go pipeline stage assignment maps to the corresponding Twenty CRM Pipeline stage. Stage transitions and historical movement context migrate as activity entries on the Opportunity timeline.

Lime Go Activities (touchpoints logged between users and records) map to Twenty CRM Timeline Entries. We preserve activity type, timestamp, subject, body, and linked Contact or Customer. Activity history sequences into the Twenty CRM Timeline view with the original timestamp preserved for chronological ordering.

Lime Go Tasks (with assignee, due date, status, and priority) map to Twenty CRM Task records. Task ownership and status transitions transfer directly. Lime Go's batch action limitations do not affect how we structure migrated records; each task becomes an individual Twenty CRM Task with its full context.

Lime Go Reminders attached to Contacts, Customers, or Deals map to Twenty CRM Task records. We preserve the reminder timestamp and notification context. Recurring reminders map as repeating Task records with their recurrence pattern encoded in Twenty's task fields.

Lime Go History Notes (chronological interaction records per Customer or Contact) migrate as Twenty CRM Note records linked to the corresponding Contact or Company. The full note text, author, timestamp, and any associated attachments transfer. Notes appear in the Twenty CRM Timeline under the linked record.

Documents attached to Customers, Contacts, or Deals are extracted from Lime Go storage and linked to the corresponding Twenty CRM records (Contact, Company, or Opportunity) via Twenty's attachment model. We preserve file names and upload timestamps. Large binary attachments may require chunked extraction depending on Lime Go's export file size limits.

Tags applied across Lime Go Customers, Contacts, and Deals transfer as flat label arrays. We map them to Twenty CRM Tag records or custom multi-select label fields depending on the customer's preference. Tags used for segmentation preserve their original values for reporting continuity.

Custom fields on Lime Go Customers, Contacts, and Deals vary by tenant. We discover the tenant schema during scoping, map field types (text, number, date, picklist) to Twenty CRM custom field equivalents, and flag any field types that have no direct Twenty CRM equivalent for the customer to decide on a case-by-case basis during design review.

Consent history (granted, withdrawn, timestamp, source) migrates as custom fields on the Contact and Company records in Twenty CRM. We preserve the full consent timeline to maintain GDPR compliance posture post-migration. If the customer uses Lime Go's anonymisation feature, anonymised records are flagged in the migration inventory rather than imported as active contacts.