Migrate from Insightly CRM to HighLevel

Insightly Organizations map to GoHighLevel Companies. Organization.ORGANIZATION_NAME becomes Company.name, and Organization.WEBSITE becomes Company.website. GoHighLevel stores Companies as a separate object type from Contacts, and the Company record must exist before any Contact import that references it. We import all Organizations first, using ORGANIZATION_ID as the dedupe key, then resolve the GoHighLevel Company ID for use as a Contact custom field (GoHighLevel treats this as a user-defined company link rather than a native Lookup relationship).

Insightly Contacts map to GoHighLevel Contacts. Standard fields (first name, last name, email, phone, address) migrate directly. The Contact-to-Organization link from Insightly resolves to the GoHighLevel Company ID via a Contact custom field we create and populate during the Organization import phase. Any Insightly contact custom fields migrate to GoHighLevel custom fields under Settings > Custom Fields, looked up by FIELD_NAME in Insightly and pre-created by field name in GoHighLevel before writes begin.

Insightly Leads map to GoHighLevel Contacts with a custom field lead_status__c set to the original Insightly Lead status value. Insightly's Lead object is a top-level record type with its own lifecycle; GoHighLevel does not have a separate Lead object, so Leads land as Contacts with status preserved for segmentation. The migration team creates the lead_status__c custom field in GoHighLevel during schema setup before any Lead data moves.

Insightly Opportunities map to GoHighLevel Opportunities. The Opportunity name, value, probability, and stage migrate directly. Pipeline stages in Insightly are custom-named strings (not enumerated) and must map to GoHighLevel pipeline stage names we configure during schema setup. If the Insightly Opportunity references an Organization, we resolve the GoHighLevel Company ID and attach it to the Opportunity's Company field. We do not create GoHighLevel Pipelines as code; we configure the Pipeline and its stages in GoHighLevel during the schema phase and map Opportunity.OPP_STAGE to the configured stage name.

Insightly pipeline stages are arbitrary named strings attached to Opportunities. GoHighLevel requires Pipeline and Stage configuration before Opportunity records can use them. We extract all distinct stage names from Insightly Opportunities during discovery, create the matching Pipeline and Stage entries in GoHighLevel under Settings > Pipelines, and document the mapping table. Stage probability percentages from Insightly migrate as Stage Order or probability values in GoHighLevel if the customer requests it.

Insightly Tasks migrate to GoHighLevel Tasks. Task.TITLE becomes Task.subject, Task.DUE_DATE becomes Task.date, Task.STATUS maps to GoHighLevel task status values, and Task.ASSIGNED_USER_ID resolves to a GoHighLevel User lookup by email. Tasks linked to specific Insightly objects carry the linked record's GoHighLevel equivalent ID once that import phase completes. Task status value mapping is documented during scoping because Insightly and GoHighLevel use different enumerated status sets.

Insightly Notes (comments) migrate to GoHighLevel Notes. Note.BODY migrates as the Note content, Note.CREATED_DATE preserves the creation timestamp, and Note.OWNER_ID resolves to a GoHighLevel User by email. Notes linked to Contact, Organization, or Opportunity carry the GoHighLevel equivalent record ID once each parent object import phase completes. GoHighLevel stores notes as text entries in the activity timeline of the linked record.

Insightly Tags are flat string labels applied to Contacts, Organizations, Opportunities, and Projects. GoHighLevel does not have a native global tag object; tags can migrate as a multi-select custom field (e.g., tag_list__c) on the Contact object, or as a Contact label depending on the customer's preference. We document the tag distribution during discovery and the customer chooses the strategy before migration. If the tag list exceeds GoHighLevel's 255-character custom field limit, we split into multiple tag-related custom fields.