Insightly CRM to HubSpot migration
Moving from Insightly CRM to HubSpot is the most common SMB-to-growth-stage migration in our catalog. FlitStack AI maps every Insightly Organization, Contact, Opportunity, and custom field into HubSpot's Companies, Contacts, and Deals — preserving original create dates, stage history, and contact-organization associations so your HubSpot reporting reflects the full deal lifecycle from day one. HubSpot's association model differs from Insightly's N:N link system; we surface the mapping strategy before the migration runs.
FlitStack AI migrates contacts, companies, deals, pipelines and tickets from Insightly CRM to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 total records.

What moves from Insightly CRM to HubSpot?
Insightly CRM and HubSpot both organize data around person-level, company-level, and deal-level records, but the relationship model, field-naming conventions, and pipeline configuration diverge in ways that require deliberate mapping before any data moves.
Read the full summary
Insightly stores Organizations (companies), Contacts, Opportunities (deals), Tasks, Projects, and Notes as standard objects, with a many-to-many link table for contact-to-organization relationships and a separate Role field to indicate a contact's relationship to an Opportunity. HubSpot models the same concepts as Companies, Contacts, Deals, and Tickets, but it uses a primary-company field on contacts (with additional company associations stored as a separate association set), and deal contact roles are managed through a dedicated Deal Contact Association feature rather than a flat Role field. FlitStack AI sequences the migration so foreign keys resolve correctly: Organizations migrate first, then Contacts with OrganizationId resolved to a HubSpot CompanyId, then Opportunities with contact role links rebuilt through HubSpot's association API. Original create dates, stage-change timestamps, and owner assignments are preserved as custom properties since HubSpot's native CreatedDate and LastModifiedDate reflect migration time. Projects and Tasks require case-by-case decisions — Projects may map to HubSpot Tickets or a custom object, and Tasks migrate as HubSpot Tasks with original owner and due-date metadata. Workflows, automations, email templates, and Insightly's AI Copilot settings do not migrate. These are rebuilt in HubSpot using FlitStack's exported workflow definitions as a reference. The migration runs via read-only Insightly API access (v3.1) pulling each object in dependency order, with field-level validation against a pre-run diff before the full dataset commits.
Contact → Contact
Direct 1:1 map. Insightly contacts become HubSpot contacts.
How it maps
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.
Organisation (Organization) → Company
Direct 1:1 map. Insightly Organisations map to HubSpot Companies.
How it maps
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.
Organisation Link (N:N contact-organization) → Company Association (secondary)
Insightly's contact-to-organisation link table is a pure N:N relationship with no limit.
How it maps
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.
Opportunity → Deal
Direct 1:1 map at the record level.
How it maps
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.
Opportunity Contact Role → Deal Contact Association
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).
How it maps
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.
Pipeline → Pipeline
Insightly Pipelines with stage names, probabilities, and stage-order maps translate to HubSpot Pipelines.
How it maps
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.
- ContactContact1:1
- OrganisationCompany1:1
- Organisation LinkCompany Associationtransformed
- OpportunityDeal1:1
- Opportunity Contact RoleDeal Contact Associationtransformed
- PipelinePipeline1:1
+ 6 more in the mapping below
How Insightly CRM and HubSpot differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Insightly CRM | HubSpot |
|---|---|---|
| Object naming convention | Organizations (person records as Contacts), Opportunities (deal records) | Companies (org records), Contacts, Deals (opportunity records) |
| Contact-organization relationship | N:N links via separate link table with ORGANISATION_ID + CONTACT_ID | Primary company field on Contact + secondary company associations via HubSpot association API |
| Contact-opportunity relationship | OPPORTUNITY_ID on Contact + ROLE field indicating influence level | Deal Contact Associations with role labels (Decision Maker, Technical Champion, etc.) |
| Pipeline configuration | Pipelines with stage names, probabilities, and probability-to-stage mapping per pipeline | Pipelines as a separate object from Deals — pipeline_id and dealstageid stored on each Deal record |
| Custom field storage | Custom fields per object via FIELD_NAME + custom field metadata API | Custom properties created in HubSpot property settings, accessible via property name (snake_case or camelCase) |
| Project management | Built-in Projects object linked to Opportunities, Contacts, or Organizations | No native project object — requires HubSpot Tickets or a custom object |
| Workflow automations | Workflow rules with triggers, conditions, and actions — Professional/Enterprise tiers | HubSpot Workflows (Sales Hub Professional/Enterprise) — entirely separate schema, must be rebuilt |
| API rate limits | 10 requests/second, daily limit based on plan (starting at 1,000/day for Gratis) | 100 calls/second in normal tier; 25 calls/second for new portal integrations — affects bulk migration pacing |
Insightly CRM to HubSpot field mapping
The 30 most-used fields of 43 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
FIRST_NAMEContactfirstnameContact -
LAST_NAMEContactlastnameContact -
EMAIL_ADDRESSContactemailContact -
PHONE_NUMBERContactphoneContact -
MOBILE_PHONE_NUMBERContactmobilephoneContact
| Insightly CRM field | HubSpot field | Mapping | Note |
|---|---|---|---|
Contact.FIRST_NAME | Contact.firstname | direct | |
Contact.LAST_NAME | Contact.lastname | direct | |
Contact.EMAIL_ADDRESS | Contact.email | direct | |
Contact.PHONE_NUMBER | Contact.phone | direct | |
Contact.MOBILE_PHONE_NUMBER | Contact.mobilephone | direct | |
Contact.TITLE | Contact.jobtitle | direct | |
Contact.MAILING_STREET | Contact.address | direct | |
Contact.MAILING_CITY | Contact.city | direct | |
Contact.MAILING_STATE | Contact.state | direct | |
Contact.MAILING_POSTCODE | Contact.zip | direct | |
Contact.MAILING_COUNTRY | Contact.country | direct | |
Contact.DATE_CREATED | Contact.Original_Create_Date__c | custom_field_required | HubSpot sets Createdate at migration time; original Insightly date preserved as a custom datetime property for reporting continuity. |
Contact.DATE_UPDATED | Contact.Original_Last_Modified_Date__c | custom_field_required | HubSpot LastModifiedDate reflects migration activity; original Insightly update timestamp preserved as a custom datetime property. |
Contact.USER_ID (owner) | Contact.hubspot_owner_id | transformed | Owner resolved by email match against HubSpot users. Unmatched owners flagged before migration; fallback owner assigned or contact record held for review. |
Contact.ORGANISATION_ID (primary link) | Contact.associatedCompanyId | transformed | The primary Organisation link on an Insightly contact resolves to the HubSpot CompanyId lookup. The Organisation must migrate first so the ID is available. |
Contact.CUSTOMFIELDS | Contact.Custom property (per field) | custom_field_required | Each Insightly custom field on Contact becomes a HubSpot custom contact property. Pick-list custom fields require value-by-value mapping against HubSpot's option set. |
Organisation.ORGANISATION_NAME | Company.name | direct | |
Organisation.WEBSITE | Company.domain | direct | |
Organisation.INDUSTRY | Company.industry | value_mapping | Industry pick-list values mapped per value. Where Insightly uses a value not present in HubSpot's industry list, the nearest match or a custom option is applied. |
Organisation.EMPLOYEE_COUNT | Company.numberofemployees | direct | |
Organisation.ANNUAL_REVENUE | Company.annualrevenue | direct | |
Organisation.PHONE_NUMBER | Company.phone | direct | |
Organisation.CITY | Company.city | direct | |
Organisation.STATE | Company.state | direct | |
Organisation.POSTCODE | Company.zip | direct | |
Organisation.COUNTRY | Company.country | direct | |
Organisation.PARENT_ORGANISATION_ID | Company.parent_id | transformed | HubSpot parent company field. The parent Organisation must migrate before the child so the parent company ID is available for lookup. |
Organisation.CUSTOMFIELDS | Company.Custom property (per field) | custom_field_required | Each Insightly custom field on Organisation becomes a HubSpot custom company property. Date, number, and text types map directly; pick-list types require value mapping. |
Opportunity.OPP_NAME | Deal.dealname | direct | |
Opportunity.OPP_VALUE | Deal.amount | direct |
What to watch for in a Insightly CRM to HubSpot migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
HubSpot's association model requires a primary-company decision for every contact
Insightly stores contact-to-organization relationships as a free N:N link table — a single contact can have five linked organisations with no primary designation.
How we handle it
HubSpot assigns one primary company to a contact and stores additional companies in a secondary association set. If your Insightly data has contacts with multiple active organisation links, we need a rule to pick the primary (most-recently-modified link is the default; you can specify an alternative). Secondary links are preserved as HubSpot company associations, but the one-to-many mapping requires a deliberate choice before migration runs.
Insightly Opportunity Contact Roles must be rebuilt via HubSpot's Deal Contact Association API
Insightly records a contact's role on an opportunity (Decision Maker, Technical Champion, Influencer) as a field on the opportunity contact link record.
How we handle it
HubSpot uses a separate Deal Contact Associations mechanism with role labels. We map the most common Insightly role values to their HubSpot equivalents, but non-standard Insightly role labels that have no HubSpot match require a custom property on the Deal to preserve the data. This is surfaced in the pre-migration field mapping plan — your team confirms the mapping before the migration runs.
Insightly Projects have no native HubSpot object — migration requires a rebuild decision
Insightly's Project object is a standard CRM object linked to Opportunities, Contacts, and Organisations with its own set of custom fields, milestones, and tasks.
How we handle it
HubSpot has no equivalent. Projects can be migrated as HubSpot Tickets (for simple tracking needs), a HubSpot custom object (for complex project schemas with linked records), or archived as a static record with the project data preserved in a custom property. Each approach changes the field mapping and the downstream UX. We present all three options in the migration plan and your team makes the call before data moves.
Insightly workflow definitions must be rebuilt in HubSpot — automation logic does not transfer
Insightly workflow automations (triggers, conditions, and actions defined in the Professional and Enterprise plans) are stored in Insightly's own automation engine with no export path to HubSpot's workflow schema.
How we handle it
We document each active Insightly workflow — its trigger event, condition branches, and action steps — as a structured rebuild reference for your HubSpot admin. The rebuild work falls outside the data migration scope and must be planned separately. Priority tip from teams that have done this migration: rebuild your highest-revenue-impacting automations first, then work down the list.
API rate limits require migration throttling — large datasets need extended windows
Insightly's API enforces 10 requests per second and a daily request limit that varies by plan (Gratis starts at 1,000 requests per day).
How we handle it
HubSpot's normal tier allows 100 requests per second, but new portal integrations start at 25 requests per second. For datasets over 25,000 records, these limits mean the migration runs in batched cycles rather than a single pass. We paginate Insightly API responses and pace HubSpot API writes to stay within both platforms' limits. Large migrations with complex custom object schemas and N:N association rebuilding can extend the migration window to 7–10 days of active processing.
How the migration runs
Audit Insightly data volume and build the field mapping plan
FlitStack AI connects to Insightly via read-only API access (v3.1) to audit record counts across all objects — Contacts, Organisations, Opportunities, Projects, Tasks, Notes, and custom objects.
What this step covers
We generate a data volume report and a field-level mapping spreadsheet that pairs every Insightly field with its HubSpot equivalent. For fields with no direct HubSpot match, we propose a custom property or a value-mapping rule. Your team reviews and approves the mapping plan before any data moves.
Create HubSpot data structure and resolve owners
Before records migrate, we create all required HubSpot custom properties, configure pipeline and stage IDs, and set up custom objects referenced in the mapping plan.
What this step covers
Insightly user accounts are matched to HubSpot users by email address — unmatched owners are flagged so your team can either invite them to HubSpot or assign a fallback owner before migration. No record lands in HubSpot without a resolved owner.
Migrate Organisations first, then Contacts, then Opportunities with association rebuild
We sequence the migration to satisfy HubSpot's foreign-key requirements.
What this step covers
Organisations migrate first and become HubSpot Companies. Contacts migrate next with PRIMARY_ORG_ID resolved to HubSpot CompanyId lookups; N:N organisation links surface as secondary HubSpot company associations. Opportunities migrate last with contact roles rebuilt via HubSpot's Deal Contact Association API. Projects migrate as HubSpot Tickets or a custom object per your team's pre-decided strategy.
Run sample migration with field-level diff before full commit
A representative slice — typically 100–500 records across Contacts, Companies, Deals, and a sample of Notes and Tasks — migrates first.
What this step covers
We generate a field-level diff report comparing source values against HubSpot destination values, covering field-name mapping, pick-list value mapping, owner resolution, and association links. Your team reviews the diff and approves before the full migration commits. This sample validation ensures that all custom property names, pick-list options, and association types transfer correctly before committing the entire dataset.
Execute full migration with delta-pickup window and audit log
Full dataset migrates in dependency order.
What this step covers
A delta-pickup window (typically 24–48 hours) captures any records created or modified in Insightly during the cutover period. Every operation is captured in an audit log — record counts per object, association links created, custom properties populated, and any records that failed to migrate with the reason for each failure. One-click rollback reverts all migrated records if reconciliation against the source data fails.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Insightly CRM to HubSpot migrations land in the lower-to-mid range of our pricing band when the dataset is under 25,000 records with fewer than 30 custom fields — the field-mapping surface is straightforward because both platforms share a similar CRM object model (Contacts, Organizations, Opportunities). Cost climbs when Insightly's Project objects require remapping to HubSpot Tickets or custom objects, when N:N contact-organization links need a custom association preservation strategy, or when multiple custom fields use pick-list values that require value-by-value mapping against HubSpot's property options. Teams with heavy deal-stage history or Insightly role-field data on Opportunities should expect the upper range due to the association rebuild complexity. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Insightly CRM to HubSpot →Why teams move from Insightly CRM to HubSpot
- Insightly's per-user pricing at Professional ($899/user/month) and Enterprise ($2,599/user/month) tiers outpaces HubSpot's Starter tier cost for growing teams, and feature gates on workflow automation push mid-market teams toward the most expensive plan before they get the automation they need — teams cite cost climbing faster than their headcount growth.
- Users report that Insightly's advanced automation and analytics features remain locked behind higher-priced tiers, limiting smaller teams from accessing the tools that would justify the subscription cost. The setup process is time-consuming, with automation workflows creating frequent timeouts that affect day-to-day usability.
- Teams that want HubSpot's inbound marketing and sales tools working from a single integrated platform choose the migration to unify their go-to-market stack — HubSpot's free CRM combined with Marketing Hub and Sales Hub offers a connected platform that Insightly's separate product model doesn't match at the same price point.
- Insightly's learning curve for onboarding new team members is steep, particularly around automating workflows and navigating the interface — teams report that documentation is incomplete and that getting new users productive takes longer than expected. HubSpot's more widely-adopted UX reduces this friction for growing teams.
- HubSpot's App Marketplace and native integrations with tools like Gmail, Google Calendar, and Slack are more established than Insightly's AppConnect ecosystem, and teams cite integration breadth as a reason to consolidate on HubSpot as their growth-stage CRM platform. Additionally, HubSpot's integration ecosystem includes a wide range of third-party apps that can be connected via webhooks and APIs, further extending functionality beyond what Insightly currently supports.
Questions, answered
Insightly CRM to HubSpot migration questions
How long does an Insightly CRM to HubSpot migration take?
Most Insightly-to-HubSpot migrations complete within 48–72 hours of active migration time for datasets under 25,000 total records. Larger datasets — particularly those with Projects that require custom object remapping or extensive N:N contact-organisation links — extend to 7–10 days. The mapping plan review and HubSpot schema setup add 3–5 business days before migration begins. The delta-pickup window (24–48 hours) runs after the full migration to capture final in-flight changes.
Will my Insightly workflows migrate to HubSpot?
No. FlitStack AI migrates data and schema only — Insightly workflow automations do not transfer to HubSpot Workflows because each platform stores automation logic in its own engine with incompatible schemas. We export your Insightly workflow definitions (triggers, conditions, and action steps) as a structured rebuild reference document that your HubSpot admin can use to reconstruct each workflow in HubSpot Workflows. Prioritise revenue-impacting automations first; budget 1–2 hours per complex workflow for rebuild time.
What does an Insightly Opportunity become in HubSpot?
Insightly Opportunities become HubSpot Deals. The opportunity name maps to dealname, the amount field maps directly, and the stage name maps value-by-value to the target HubSpot pipeline's stage label. The close date, probability, and owner all migrate with the record. Any custom fields on the Opportunity become HubSpot custom deal properties. Notes and attachments linked to the Opportunity attach to the corresponding Deal in HubSpot.
Can I migrate Insightly custom objects to HubSpot?
Yes. Insightly custom objects (available on Professional and Enterprise plans) map 1:1 to HubSpot custom objects. Each HubSpot custom object must be created before migration — we include the creation in the pre-migration schema setup phase. Custom-object records that have N:N associations to Contacts or Opportunities in Insightly require those associations to be rebuilt in HubSpot via the association API; we surface this requirement in the mapping plan before migration runs.
How does HubSpot handle Insightly's N:N contact-to-organisation links?
Insightly allows any number of organisation links per contact with no primary designation. HubSpot assigns one primary company to each contact and stores additional company associations separately. We use a rule to pick the primary company (most-recently-modified link by default, or a rule you specify) and surface all other organisation links as secondary HubSpot company associations. All links are preserved, and the mapping strategy is confirmed in the pre-migration review.
Does the migration affect my Insightly account during the cutover?
No. FlitStack AI connects to Insightly via read-only API access, so your team can keep working in Insightly without interruption throughout the migration process. After the primary migration run, a delta-pickup window of 24–48 hours captures any new or changed records created during the cutover period. Once the delta is applied and your data is reconciled against the source, your HubSpot account will reflect the final state of Insightly at go-live.
What happens to my Insightly Projects after migration to HubSpot?
Insightly Projects have no direct HubSpot equivalent — they require a decision before migration. Options are: (1) Migrate as HubSpot Tickets for simple project tracking, (2) Migrate as a HubSpot custom object for complex project schemas with custom fields and milestones, or (3) Archive project data as a static custom property on the related Deal for reference. We present all three options in the migration plan with the field-level mapping for each approach so your team can choose the strategy that fits your HubSpot workflow.
Related migrations
HubSpot implementation
Set up HubSpot and migrate into it as one engagement.
See the service → Freshsales to HubSpotMapping · history · rollbackAttio to HubSpotMapping · history · rollbackDentrix to HubSpotMapping · history · rollbackNimble CRM to HubSpotMapping · history · rollbackSentia to HubSpotMapping · history · rollbackAct! to HubSpotMapping · history · rollback Insightly CRM to Zoho CRMMapping · history · rollbackInsightly CRM to Dynamics 365Mapping · history · rollbackInsightly CRM to SalesforceMapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
- Understand property field types in HubSpot
- Associate records on CRM objects — HubSpot Knowledge Base
- Integration throughput and limits — HubSpot Knowledge Base
- HubSpot Cloud Infrastructure and Data Hosting FAQ
Get a quote
Moving from Insightly CRM to HubSpot?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.
Get a quote