Migrate from Insightly CRM to HubSpot

Direct 1:1 map. Insightly contacts become HubSpot contacts. Each contact's PRIMARY_ORG_ID resolves to a HubSpot CompanyId lookup. Contacts without an OrganizationId land in HubSpot as contacts without an associated company — flagged for review before the full migration commits. During the migration, any contacts that lack an organization link are logged in a review queue so your team can manually assign a company if needed before finalizing the data.

Direct 1:1 map. Insightly Organisations map to HubSpot Companies. The ORGANISATION_ID becomes the reference for resolving Contact-to-Company associations during the contact migration phase. Parent-child Organisation hierarchies map to HubSpot's parent company field if your HubSpot account has that feature enabled.

Insightly's contact-to-organisation link table is a pure N:N relationship with no limit. HubSpot stores one primary company on a contact and additional company associations via a separate association set. We migrate the most recently modified organisation link as the primary company and surface the rest as secondary HubSpot company associations. All links are preserved as a custom multi-select property for reference.

Direct 1:1 map at the record level. Insightly Opportunity fields (OPP_NAME, AMOUNT, STAGE, PROBABILITY, CLOSE_DATE, PIPELINE_ID, OWNER_USER_ID, CUSTOMFIELDS) map to HubSpot Deal properties (dealname, amount, dealstage, hubspot_owner_id, pipeline, closedate). Stage values require value-by-value mapping against your HubSpot pipeline's stage set.

Insightly stores a contact's role on an Opportunity as a ROLE field on the opportunity contact record (values like Decision Maker, Technical Champion, Influencer). HubSpot uses Deal Contact Associations with role labels. We map the Insightly role value to the equivalent HubSpot association label. Where no HubSpot label matches, we create a custom deal property to preserve the role.

Insightly Pipelines with stage names, probabilities, and stage-order maps translate to HubSpot Pipelines. Each HubSpot pipeline must be created in HubSpot first; we reference pipeline IDs during deal migration. Stage names map value-by-value to HubSpot stage labels in the target pipeline.

Insightly Projects have no native HubSpot equivalent. We assess your project's field structure and either map it to HubSpot Tickets (for simple project-tracking use cases) or a HubSpot custom object (for complex project schemas with multiple custom fields, linked records, or milestones). Your team decides before migration runs.

Direct 1:1 map for standard tasks. Insightly task fields (TITLE, BODY, DUE_DATE, OWNER_USER_ID, TASK_COMPLETED, REMINDER_ENABLED) map to HubSpot Task properties. Completed status, due date, and original owner are preserved. Tasks linked to Opportunities in Insightly are re-linked to the corresponding HubSpot Deal via the association API.

Insightly notes with body text and a linked record (Contact, Organisation, or Opportunity) migrate as HubSpot engagements of type note. The original body text, create date, and linked record association are preserved. If the note contains file attachments, we re-upload those to HubSpot Files and link them to the target contact, company, or deal.

Insightly custom objects (Professional and Enterprise plans) map to HubSpot custom objects. Each custom object in HubSpot must be created before migration. If your Insightly custom object uses N:N associations to Contacts or Opportunities, we replicate those as HubSpot association entries via the custom object API. Simple custom objects with no complex associations may alternatively map to HubSpot Tickets.

Files attached to Insightly contacts, organisations, or opportunities are downloaded from Insightly's file storage and re-uploaded to HubSpot Files. Each file is linked to its target record (Contact, Company, or Deal) in HubSpot. File size limits apply (HubSpot's default file size limit per attachment).

Insightly workflow automations (triggers, conditions, and actions) are not transferable to HubSpot. We export your Insightly workflow definitions as a structured document so your HubSpot admin can rebuild them in HubSpot Workflows. The rebuild reference covers trigger events, condition branches, and action steps from each active workflow.