Migrate your Lime Go data

Customers are the primary account-level records in Lime Go, storing company data and metadata. We map Customers 1:1 into destination Account/Company objects, preserving custom fields, tags, and relationship hierarchies.

Contacts store individual people linked to Customers. We migrate contacts with full field fidelity including phone, email, custom properties, and owner assignments. GDPR consent flags transfer as custom properties on the destination record.

Lime Go's built-in Nordic company database provides read-only enrichment data. We extract and flag these as enrichment-only records; destination systems typically receive them as Account custom enrichment fields rather than native contacts.

Pipelines with configurable stages migrate as-is. We preserve stage order, names, probability settings, and the visual pipeline layout. Custom pipeline configurations map to destination pipeline objects or Deal stage fields.

Deals link to Customers and Pipeline Stages. We preserve deal values, expected close dates, owners, and custom fields. Stage transitions and historical pipeline movements map to destination Deal activity history.

Activities log touchpoints between users and records. We migrate activity type, timestamp, subject, body, and linked Contact or Customer. Activity history sequences into destination timeline views.

Tasks include assignee, due date, status, and priority. We preserve task ownership and status transitions. Batch action limitations in Lime Go do not affect how we structure migrated task records.

Reminders attach to Contacts, Customers, or Deals. We map them to destination Task or Activity records, preserving the reminder timestamp and notification context. Recurring reminders map as repeating tasks.

History notes capture chronological interaction records per Customer or Contact. We preserve the full note text, author, timestamp, and associated attachments as activity entries in the destination system.

Documents attach to Customers, Contacts, or Deals with storage in Lime Go. We extract files and link them to the corresponding destination records, preserving file names and upload timestamps. Large binary exports require chunking.

Custom fields on Customers, Contacts, and Deals vary by tenant. We discover the tenant schema during scoping, map field types (text, number, date, picklist) to destination equivalents, and flag unmapped types for manual review.

Tags apply across Customers, Contacts, and Deals for segmentation. We preserve tags as flat label arrays and map them to destination Tag, Label, or custom multi-select properties depending on destination system capability.

Saved filters are user-specific query configurations that do not have a stable exportable schema and are not transferable across CRM platforms. We do not migrate them; users recreate them in the destination system manually.

Consent history and anonymisation flags migrate as custom Contact/Customer properties. We preserve the full consent timeline (granted, withdrawn, timestamps) to maintain GDPR compliance posture in the destination system.