Skip to content

Migration guide · CRM Platform

Insightly to HubSpot migration

InsightlyHubSpot

Short answer

Migrating from Insightly to HubSpot moves organizations, contacts, leads, opportunities, projects and notes into HubSpot, so small and mid-sized teams get stronger marketing, automation and reporting on one platform.

Why firms make this move

Insightly users often move when they add marketing automation or need better reporting. The data model maps cleanly to HubSpot, so most of the effort goes into cleaning data, choosing pipelines and rebuilding automation. Projects can become HubSpot projects, tickets or a custom object depending on how they are used.

What moves

  • Organizations and contacts
  • Leads and opportunities
  • Projects
  • Notes, tasks and emails
  • Custom fields

How the data maps

FromTo
OrganizationCompany
ContactContact
LeadContact with lifecycle stage
OpportunityDeal
ProjectTicket, project or custom object

See the field-by-field map ↓

What to watch out for

  • Projects that need a clear home in HubSpot
  • Email history tied to individual inboxes
  • Licence end dates

How Vantage Point runs the migration

  1. Discovery and data inventory: what exists, what is clean, what is worth moving
  2. Target design: objects, record types, households or companies, ownership and security
  3. Field-by-field data mapping document, signed off by business owners
  4. Cleanup and deduplication before the move, not after
  5. Test loads into a sandbox with reconciliation reports
  6. User acceptance testing with real scenarios
  7. Cutover: final delta load, integrations switched, old system set to read-only
  8. Hypercare and adoption support

Typical timeline

Typically 2 to 5 weeks.

Frequently asked questions

Can you do the migration only, without full onboarding?

Yes. A data-migration-only scope is available when your team or HubSpot onboarding covers the rest.

What if Insightly is shutting off soon?

We plan the export first so your data is safe, then complete the load and validation.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

Insightly to HubSpot: field by field

11 mappings we start from on this migration, 7 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
Insightly OrganizationName / website Companyname / domain req derive Clean the domain; HubSpot de-duplicates companies on it.
Insightly ContactName / email / phone Contactfirstname / lastname / email / phone req direct Email is the de-duplication key.
Insightly ContactOrganization link ContactCompany association req association
Insightly OpportunityName / amount / close date Dealdealname / amount / closedate req direct
Insightly OpportunityPipeline / stage Dealpipeline / dealstage req picklist map
Insightly activitiesCalls, meetings, tasks, notes EngagementsCalls / meetings / tasks / notes association
Insightly recordOwner Anyhubspot_owner_id req lookup
Insightly recordCustom fields AnyCustom properties direct
Insightly automationWorkflows / rules Workflow— rebuild
Insightly recordSource ID AnyLegacy ID property req direct
Insightly ProjectProjects Custom object or tasks— manual review

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.