Migrate from Lime Go to Freshsales

Lime Go Customers are the primary account-level records storing company data, addresses, custom fields, tags, and owner assignments. We map them 1:1 to Freshsales Account records. The Customer name becomes the Account Name, business number maps to a custom field, and owner assignments resolve via email match to Freshsales Users. Custom fields on Customer map to Freshsales Account custom fields discovered during schema scoping. GDPR anonymisation flags carry over as custom Account properties.

Lime Go Contacts store individual people linked to Customers, including phone, email, custom properties, consent flags, and owner assignments. We map them 1:1 to Freshsales Contact records, with the parent AccountId resolved via the Customer-to-Account lookup established before Contact import. GDPR consent history migrates as custom Contact fields preserving the full consent timeline (granted, withdrawn, timestamps). Freshsales Lead records are created only if the customer has unqualified prospect contacts that should not map directly to Contact; we configure the split rule during scoping.

Lime Go Deals link to Customers and Pipeline Stages with deal values, expected close dates, owners, and custom fields. We map Deals 1:1 to Freshsales Deal records, resolving the AccountId from the linked Customer, assigning the correct Pipeline and Stage via Freshsales pipeline configuration, and preserving custom field values. Stage transition history migrates as Deal Activity records in Freshsales.

Lime Go Pipelines with configurable stages migrate as Freshsales Deal Pipelines. We preserve stage names, order, and probability percentages. Freshsales requires pipeline and stage setup in Admin Settings before Deal import; we configure this during the pre-migration schema phase and deliver the stage probability mapping as part of the configuration document.

Lime Go Activities log touchpoints between users and records including type, timestamp, subject, body, and linked Contact or Customer. We map Activities to Freshsales Activities with type preserved: calls map as Freshsales Task with TaskSubtype=Call, emails as Freshsales email activities, meetings as Freshsales events, and tasks as Freshsales tasks. WhoId and WhatId are resolved at migration time using the imported Contact and Account records.

Lime Go Tasks include assignee, due date, status, priority, and body text. We preserve task ownership by resolving Lime Go owner email to Freshsales User. Status transitions and due dates migrate as-is. Lime Go's lack of batch task operations does not affect migration; each task migrates as an individual record regardless of whether it was created individually or in bulk in the source.

Lime Go Reminders attach to Contacts, Customers, or Deals and carry a notification timestamp and context. We map them to Freshsales Task records, preserving the due date as ActivityDate and adding a custom field indicating the original Reminder type. Recurring reminders in Lime Go convert to Freshsales repeating task patterns if the destination supports them, or map as individual tasks with a recurrence note in a custom field.

Lime Go History Notes capture chronological interaction records per Customer or Contact with author, timestamp, and optional attachments. We migrate them as Freshsales Activity entries linked to the corresponding Account or Contact, preserving the full note body, author, and timestamp. File attachments carry over via the Documents mapping path.

Lime Go Documents attach to Customers, Contacts, or Deals with file storage in the platform. We extract files and link them to the corresponding Freshsales records (Account, Contact, or Deal) as Attachments, preserving file names and upload timestamps. Large binary files may require chunked download and upload with the destination file size limit respected during scoping.

Lime Go Tags apply across Customers, Contacts, and Deals for segmentation. We preserve tags as flat label arrays. Freshsales uses Labels on Contacts and Accounts; we map Lime Go tags to Freshsales Labels, creating any missing label values in Freshsales before import. The customer chooses during scoping whether to apply tags as Labels on both Account and Contact or on the primary record only.

Lime Go 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 Freshsales equivalent field types, and flag unmapped types (e.g., Lime Go-specific field types with no Freshsales equivalent) as manual-entry fields in the handoff document. Freshsales requires custom fields to be pre-created in Admin Settings before data import; we create them via the Freshsales API or deliver a configuration checklist.

Lime Go consent history and anonymisation flags migrate as custom Contact and Account properties in Freshsales. We preserve the full consent timeline (granted date, withdrawn date, consent type, source) to maintain GDPR compliance posture post-migration. The consent data model is recreated as custom fields on Contact and Account rather than as separate consent objects.