Migrate from Lime CRM to HighLevel

Lime CRM Contact records (sometimes called Person in industry variants) map directly to GoHighLevel Contact. Standard fields (name, email, phone, address) map cleanly. We normalize phone formats to prevent the leading-zero stripping that occurs when European number formats are imported into GoHighLevel's phone field without explicit formatting rules. Custom Contact properties migrate to GoHighLevel Contact custom fields.

Lime CRM Company records map to GoHighLevel Contact with the Contact Type set to Company. The company name, industry, address, and website migrate to GoHighLevel's organization fields. We configure the Contact Type during import by setting type=company on each record derived from a Lime Company. Relationship to individual Contacts is preserved via the parent_contact_id or custom_company_id field.

Lime CRM Deal records map to GoHighLevel Opportunity. Deal stage values map to GoHighLevel pipeline stages, and deal value migrates to the Opportunity amount. Owner assignment resolves by email match against GoHighLevel Users. Custom deal properties migrate to GoHighLevel Opportunity custom fields. If the Lime CRM deal uses a custom pipeline with non-standard stages, we configure matching GoHighLevel pipeline stages during the schema design phase.

Lime CRM Activities map to GoHighLevel Activity records. Calls become Tasks with type=Call; meetings become Appointments; standalone tasks become Tasks; notes become Notes. Each Activity is linked to its parent Contact or Opportunity via the custom_contact_id or opportunity_id lookup. Activity timestamps are preserved by setting the GoHighLevel ActivityDate to the original Lime CRM created_at timestamp.

Lime CRM Ticket records with helpdesk orientation map to a dedicated GoHighLevel pipeline (configured as a separate pipeline with ticket-type stages) if the customer uses tickets for sales-adjacent tracking. If tickets are pure support cases, we map them to GoHighLevel Tasks with a ticket_tag custom field and conversation history preserved as note attachments. The customer chooses the strategy during scoping based on how they use Ticket records in Lime CRM.

Lime CRM's configurable Limetypes are the core schema complexity in this migration. We extract the live schema definition from Lime CRM admin during discovery, then design the GoHighLevel custom field taxonomy. Each custom field is irrevocably typed as either Contact or Opportunity in GoHighLevel. We map Limetype fields that describe the person (lead source, birthday, preferences) to Contact custom fields, and fields that describe the deal context (budget, timeline, property type) to Opportunity custom fields. Fields that span both contexts get duplicated across both field types. The mapping decision is documented per field before migration begins.

Lime CRM Tags label Contacts, Deals, and Tickets for segmentation. We export tag values as a flat list per record and recreate them in GoHighLevel. Tags migrate as GoHighLevel native tags on Contact and Opportunity. If the tag taxonomy is large (over 200 unique tags), we validate that all tags map cleanly before import and flag any that require manual recreation in GoHighLevel's tag management interface.

Lime CRM attachments are downloaded individually per record and may be multiple files per Contact or Deal. We batch download, rename files to preserve the parent relationship (contact_id_original_filename), and upload to GoHighLevel as Contact or Opportunity attachments. Files exceeding 25 MB are flagged before upload because GoHighLevel attachment limits may require alternative handling. File integrity is validated against the export manifest to catch truncated or missing files.

Lime CRM Users and Deal owners are mapped by email address. We validate that GoHighLevel user accounts exist before assigning ownership to avoid orphaned records with null assignee fields. Any Lime CRM user without a matching GoHighLevel account goes to a reconciliation queue for the customer to provision before record import resumes.

Lime CRM workflow automations do not export in a machine-readable format. We capture the rule logic from the Lime CRM UI during discovery, document each automation with its trigger, conditions, actions, and delays, and deliver a written inventory for reconstruction in GoHighLevel's workflow builder. Complex multi-step flows that involve conditional branching, external API calls, or custom Limetype triggers require manual reconfiguration or a consultant engagement.