Migrate from Lime Go to HighLevel

Lime Go Customers (the primary account-level record) map directly to GoHighLevel Company. Customer name, address, phone, website, and custom fields transfer as Company fields. The Lime Go Customer record carries the main company-level metadata and becomes the top-level entity in GoHighLevel. Tags on the Customer transfer to GoHighLevel Company tags. We flag any Customer records that originated from Lime Go's read-only Nordic enrichment database separately because those are enrichment context, not user-owned CRM data.

Lime Go Contacts map to GoHighLevel Contact with full field fidelity. Email, phone, title, owner, custom properties, and tags migrate directly. GDPR consent flags (granted, withdrawn, timestamps) migrate as Contact custom fields that GoHighLevel's admin creates before import. We resolve the parent Company reference by matching on Company name or domain so that each Contact is linked to the correct GoHighLevel Company record.

Lime Go's built-in Nordic company database of 3.7 million businesses is a read-only enrichment layer, not user-owned CRM data. These records do not migrate as GoHighLevel Contacts or Companies. We extract the enrichment data during scoping, flag it as non-transferable CRM context, and document whether the customer plans to use a GoHighLevel-compatible enrichment provider post-migration (e.g., Clearbit, FullContact) or retain Lime Go solely for prospecting enrichment purposes.

Lime Go Deals map to GoHighLevel Opportunity. Deal value, expected close date, owner, and custom fields migrate directly. We map Lime Go's deal pipeline stage to a GoHighLevel pipeline stage using a configuration mapping table built during scoping. Stage probability percentages transfer where configured on the Lime Go side.

Each Lime Go deal pipeline becomes a GoHighLevel Pipeline. Stage names, order, and probability values map to GoHighLevel stage equivalents. We configure the GoHighLevel pipeline in the destination account before any Opportunity records import so that stage references are valid at insert time. Multiple Lime Go pipelines map to multiple GoHighLevel pipelines using Record Type scoping if the customer requires pipeline isolation per business line.

Lime Go Activities (call logs, meeting records, general touchpoints) map to GoHighLevel Task records. Activity type, subject, body, timestamp, and linked Contact or Customer transfer. Activity date ordering is preserved using the GoHighLevel Task due date and reminder timestamp fields. We reconstruct the linked Contact or Customer reference by resolving the name or email match against the migrated Contact and Company records.

Lime Go Tasks migrate to GoHighLevel Task with assignee, due date, status, and priority preserved. Task ownership resolves by matching the Lime Go owner email against the GoHighLevel User table. Recurring task patterns in Lime Go map as repeating Task records; the customer rebuilds the recurrence logic in GoHighLevel's calendar system post-migration.

Lime Go Reminders attached to Contacts, Customers, or Deals map to GoHighLevel Tasks flagged with a reminder-type custom field. The original reminder timestamp becomes the Task due date, preserving the notification context. Reminder body migrates as Task notes. Recurring reminders migrate as repeating Tasks and are flagged for the customer to rebuild the recurrence schedule in GoHighLevel.

Lime Go History Notes attached to Customers or Contacts map to GoHighLevel Tasks with a note-style format. Author, timestamp, and full note text migrate. Attachments referenced in History Notes are flagged for document migration separately. Notes are linked to the parent Contact or Company record using the resolved lookup.

Lime Go document attachments on Customers, Contacts, or Deals are extracted and linked to the corresponding GoHighLevel record by file name match and parent record reference. Large file batches (>100MB aggregate) require pre-coordination for GoHighLevel storage planning. We do not migrate the document rendering pipeline; PDF previews and embedded links must be tested post-import.