Skip to main content
Meticulosity

Agency Migration Guide

Insightly to HubSpot Migration

What actually transfers, what quietly does not, and what has to be rebuilt by hand.

We mapped Insightly against HubSpot feature by feature: 52 features, 5 synced objects, 8 documented traps and 30 items that have to be rebuilt. The whole map is on this page, ungated.

The PDF is the same reference, formatted to send to a client.

Size Your Migration

Get The Guide And The Calculator

The full Insightly to HubSpot reference as a branded PDF you can send straight to a client, plus the Excel calculator we scope these migrations with: every one of the 52 features as a row, enter your counts, get hours.

Three files: the guide as a PDF, the same guide unbranded in Markdown for your AI tool, and the full Excel effort calculator.

PDF documentPDFMarkdown documentMDExcel workbookXLS
Insightly logoHubSpot logo

Insightly to HubSpot is a medium migration, typically 3-6 weeks. Of 52 features we mapped, 40 carry across as they are and 12 land with something lost. The work is not moving records: it is the 30 items nothing moves for you.

Migration Scorecard

Complexity: Medium
Migration complexity
Medium
Typical timeline
3-6 weeks
Recommended method
Sync then migrate
Native sync
Data sync, two way
Smart transfer
Not supported
HubSpot subscription
Free for default mappings. Data Hub Starter or higher required for custom field mappings.

Feature parity across 52 capabilities

4077%
1223%
  • Maps directly: 40 (77%)
  • Maps partially: 12 (23%)
  • No equivalent: 0 (0%)

5

Objects synced natively

8

Limitations and traps

30

Manual rebuild items

3

Source editions covered

Where this comes from: Our own research corpus, verified 2026-08-01, behind every number on this page.

Size Your Own Migration

The Five Objects That Sync Natively

What the connector moves for you, and which way each one flows.

Contacts

Two wayTwo way

Becomes Contacts

Email address is the primary matching key. Records without valid email may not sync.

Organizations

Two wayTwo way

Becomes Companies

Matched by company name and domain.

Opportunities

Two wayTwo way

Becomes Deals

Deal sync requires an accompanying contact and/or company sync to maintain associations. Syncs across all pipelines and stages.

Leads

Two wayTwo way

Becomes Contacts

Insightly Leads map to HubSpot Contacts, a mapping distinct from the Contacts entry. Listed as a shared object on the app's HubSpot marketplace listing (read 2026-07-31). HubSpot publishes 16 default field mappings for it.

Custom Object

Two wayTwo way

Becomes Custom Object

Insightly custom objects sync to HubSpot custom objects, which requires HubSpot Enterprise. Listed as a shared object on the app's HubSpot marketplace listing (read 2026-07-31). No default field mappings are published.

Eight Things the Sync Does Not Tell You

Each one is documented, and each one has ended a migration in a bad week.

Activities and Engagements Do Not Sync Natively

The native HubSpot data sync does not transfer activities such as notes, tasks, emails, calls, or meetings between Insightly and HubSpot. HubSpot's standard import also does not support importing engagements.

Workaround: Use API-based migration or third-party tools (e.g., Trujay/MigrateMyCRM) to transfer activity history.

Attachments Require Separate Migration

File attachments on Insightly records do not transfer through the native data sync and need to be migrated separately.

Workaround: Export attachments from Insightly and re-upload to HubSpot via API or manual import.

Custom Field Mappings Require Data Hub Starter

Default field mappings are available for free, but editing defaults or creating custom field mappings requires Data Hub Starter or higher.

Workaround: Subscribe to Data Hub Starter ($20/mo) for custom mapping capability.

Some Field Types Only Sync One-way as Text

Dropdown select properties may not sync two-way in all cases and may only map one-way as text. Address properties may also sync one-way due to formatting discrepancies.

Workaround: Review field mapping screen carefully; manually update fields that cannot sync bidirectionally.

Custom Objects Require Enterprise Tier and Separate Configuration

Syncing custom objects between Insightly and HubSpot requires HubSpot Enterprise and specific configuration. Not all custom object types may be supported.

Workaround: Use HubSpot Enterprise with custom object sync feature, or migrate custom object data via CSV/API.

Activity Data Split From Main Records Loses Associations

If main records are migrated via native tool and activities are migrated separately (e.g., via third-party), the activities will not be attached to main records and relationships will not be preserved.

Workaround: Use a single migration tool/method that handles both records and activities together to preserve associations.

Email Address Required for Contact Matching

HubSpot's data sync relies on email address as the primary deduplication key. Contacts without valid email addresses may not sync or match correctly.

Workaround: Ensure all contacts have valid email addresses before syncing, or use CSV import for records without emails.

Insightly Projects Do Not Have a Direct HubSpot Equivalent

Insightly's Projects module (used for post-sale delivery tracking) has no direct equivalent in HubSpot CRM. Project data must be mapped to deals, tickets, or custom objects.

Workaround: Map projects to HubSpot tickets, a custom object, or a secondary deal pipeline depending on use case.

One Thing a Migration Does Not Rebuild

This is Insightly's own code or product. A HubSpot migration does not port it, so it carries no hours in any estimate. It still needs a decision, because the client is giving something up.

AppConnect (Integration Platform)

Each AppConnect integration needs evaluation and replacement. Some may have native HubSpot equivalents; others need Zapier/Make.

The 30 Items That Get Rebuilt by Hand

This is the list that separates a quote that holds from one that does not.

Data And Objects

Notes and Comments (do Not Sync via Native Integration)

Task History and Assignments

Email Correspondence History

Call Logs and Meeting Records

File Attachments on Records

Insightly Projects (no Direct HubSpot Equivalent)

Custom Object Data (requires Enterprise Tier)

Record Relationships Beyond Primary Associations

Automation

Insightly Workflow Automation Rules

Activity Sets (templated Task Sequences)

Email Notification Rules

Lead Assignment Rules

Pipeline Stage Automation Triggers

Reporting

Custom Reports and Saved Filters

Dashboard Configurations

Opportunity Reports and Pipeline Analytics

Activity/productivity Reports

Sales And Marketing Config

Lead Scoring Criteria

Email Templates

Pipeline Stages and Configuration

Web-to-lead/contact Forms

Sales Sequences and Follow-up Cadences

Users And Permissions

User Roles and Permissions

Team/territory Assignments

Record Visibility Rules

Profile-level Field Permissions

Integrations

Third-party App Connections (e.g., Mailchimp, QuickBooks)

Insightly AppConnect Automations

Calendar Sync Configurations

Custom API Integrations

Estimate The Hours

The Sequence

Sync First, Then Migrate

Order is the content here. These are a dependency chain, and running them out of order is a documented way these migrations fail.

  1. 1

    Audit Insightly Data

    identify active records, custom fields, pipelines, and integrations

  2. 2

    Clean Data

    deduplicate contacts, remove inactive records, verify email addresses

  3. 3

    Set up HubSpot

    create custom properties, configure pipelines, set up deal stages

  4. 4

    Install HubSpot Data Sync App for Insightly to Sync Contacts, Companies, and Deals

    Install HubSpot Data Sync app for Insightly to sync contacts, companies, and deals

  5. 5

    Configure Field Mappings (Data Hub Starter Required for Custom Mappings)

    Configure field mappings (Data Hub Starter required for custom mappings)

  6. 6

    Run Initial Sync and Verify Data Accuracy

    Run initial sync and verify data accuracy

  7. 7

    Migrate Activities, Notes, and Attachments via API or Third-party Migration Tool

    Migrate activities, notes, and attachments via API or third-party migration tool

  8. 8

    Rebuild Workflows, Automation Rules, and Email Templates in HubSpot

    Rebuild workflows, automation rules, and email templates in HubSpot

  9. 9

    Recreate Reports and Dashboards in HubSpot

    Recreate reports and dashboards in HubSpot

  10. 10

    Train Team on HubSpot, Run Parallel Systems Briefly, Then Cut Over

    Train team on HubSpot, run parallel systems briefly, then cut over

Typically 3-6 weeks end to end, depending on how much of the source configuration is actually in use.

Effort Estimator

How Big Is This Migration?

A handful of questions, no email required. The ranges come from the research above: every feature we mapped carries an effort figure, and this adds up the ones that apply to you.

Custom fields and properties across all records

Everything beyond the out-of-the-box fields, added up across contacts, companies, deals and anything custom.

Automations, workflows and rules

Anything that fires on its own: workflows, sequences, assignment and validation rules, approvals.

Custom reports and dashboards

Only the ones the business actually uses. Reports nobody opens do not need rebuilding.

Marketing assets to rebuild

Email templates, forms, landing pages, lists and segments taken together.

Custom objects or extra pipelines

Record types beyond contacts, companies, deals and tickets.

Third-party integrations wired into the current system

Anything connected by API, webhook or installed package that has to keep working afterwards.

Users to move across

Seats, plus whatever permission structure sits behind them.

Roughly how many contact records

This affects the sync approach and the reconciliation effort, not the per-record work. The connector moves records; people do not.

Estimated Effort

Answer a couple of questions and an hours range appears here.

Built from our research on 52 Insightly features. It is a range, not a quote.

A planning range, not a quote. It is delivery effort only, with no project management line and no agency markup, so add your own. What moves it most in practice is data quality.

What Goes Wrong Most Often

The failures that show up again and again, in roughly the order they bite.

Insightly Projects Map Onto the HubSpot Projects Object and Milestones Onto Its Pipeline Stages; the Mapping Strategy Is About What to Do With Budgets and Dated Milestones, Not About Finding a Home

Insightly Projects map onto the HubSpot projects object and milestones onto its pipeline stages; the mapping strategy is about what to do with budgets and dated milestones, not about finding a home

Activity Data Migrated Separately From Records Loses Associations

Activity data migrated separately from records loses associations

HubSpot Does Not Natively Import Notes/activities via CSV - API or Third-party Tool Required

HubSpot does not natively import notes/activities via CSV - API or third-party tool required

Email History From Insightly Cannot Be Easily Forwarded Into HubSpot

Email history from Insightly cannot be easily forwarded into HubSpot

Timestamps May Be Lost During CSV-based Migrations

Timestamps may be lost during CSV-based migrations

Insightly's Tag System Needs to Be Mapped to HubSpot Properties or Lists

Insightly's tag system needs to be mapped to HubSpot properties or lists

Questions

Insightly To HubSpot, Answered

Ready to get started?

Let's do something great together.

Augment your agency's marketing team's bench with our end-to-end inbound and digital solutions and find out why we're "The HubSpot Agency for HubSpot Agencies."

Fill out this form, and someone from our Solutions team will be in touch with you soon!