Migrate from Insightly Marketing to HighLevel

Insightly Contact records map directly to GoHighLevel Contact. The Contact's First Name, Last Name, Email, Phone, Address, Title, and Owner fields transfer 1:1. Insightly custom fields attached to Contact migrate to GoHighLevel custom fields on the Contact object. The Contact's Organization link resolves by matching the Organization Name in Insightly to the Company Name field on the GoHighLevel Contact record.

Insightly Organization records (companies and accounts) merge into GoHighLevel as Company Name entries on Contact records. Each unique Organization becomes a single Company record in GoHighLevel. The Organization's custom fields, Industry, Website, and Phone migrate to corresponding custom fields on the GoHighLevel Contact. Organization-to-Organization relationships and multi-contact organization memberships are preserved as GoHighLevel contact tags or a custom Companies custom object if the customer requires a distinct company-level record type.

Insightly Opportunity records map to GoHighLevel Opportunities with Stage, Amount, Expected Close Date, Probability, and Owner preserved. The pipeline name from Insightly maps to a GoHighLevel pipeline that we configure before migration. Closed-Lost reason custom fields become GoHighLevel Opportunity custom fields. Probability percentages normalize to the nearest integer values allowed in GoHighLevel's stage configuration.

Insightly Projects have no native equivalent in GoHighLevel, which lacks a built-in project management module. We migrate Projects as a GoHighLevel custom object named Project with Status, Milestones, and Task List preserved as custom fields. Project-to-Contact and Project-to-Organization links migrate as association records or as lookup relationships in the custom object schema. This requires a schema discovery phase because Insightly Project structures vary by customer implementation.

Insightly Task records map directly to GoHighLevel Tasks with Subject, Due Date, Status, Priority, and Assignee preserved. The related-to reference (Contact, Organization, Opportunity, or Project) migrates by resolving the target record's identifier in GoHighLevel at migration time. Completed task notes and body text migrate as GoHighLevel task descriptions.

Insightly Notes attached to Contacts, Organizations, Opportunities, or Projects migrate as GoHighLevel Notes linked to the target Contact or Opportunity record via the record's identifier. Note body text and any attachment filenames migrate. Attachments themselves require a separate assessment during discovery to determine if the file storage context is preserved.

Insightly custom field groups (named expandable sections of related custom fields) do not have a direct GoHighLevel equivalent. We extract each custom field from its group, assign it a GoHighLevel custom field of matching type (text, number, date, dropdown, checkbox), and document the original group context in the mapping notes. This preserves the grouping intent without the UI grouping structure.

Insightly custom objects vary per customer implementation and require a schema discovery phase before migration. We map the custom object's API name, fields, field types, and lookup relationships to equivalent GoHighLevel custom objects. Dependencies between custom objects and standard Insightly objects are identified during discovery and mapped to GoHighLevel's custom object relationship model. The GoHighLevel custom object schema is created before any data import begins.

Insightly tags on Contacts, Organizations, Opportunities, and Projects are extracted as plain text label strings. We re-apply them as GoHighLevel native tags on the matching Contact or Opportunity record. Tags that represent categorical data (industry type, client tier, product line) can alternatively map to a GoHighLevel custom multi-select field, depending on the customer's reporting needs. The customer chooses tag strategy during scoping.