Skip to content
Insightly logo
Switch from another CRM
Live

Connect Insightly to HelloGrowthCRM

Migrate Insightly contacts, leads, opportunities, projects, and custom fields to HelloGrowthCRM with relationship mapping preserved.

Quick answer

Will the links between contacts, organisations and opportunities survive?

Yes, provided records are imported in the right order. Contacts and organisations go in before opportunities so the relationship lookups resolve to records that already exist. Importing out of order is the main cause of orphaned opportunities, which is why the sequence is enforced during setup.

Overview

Insightly blends CRM and lightweight project management, so its data model carries contacts, organisations, leads, opportunities, and projects, all linked by Insightly's relationship records. Teams usually outgrow it when they need stronger mobile access, deeper pipeline reporting, or India-specific workflows. Migrating to HelloGrowthCRM preserves the relationship web — who works at which organisation, which opportunity belongs to which contact — rather than flattening everything into disconnected lists.

The order of import matters more with Insightly than with most tools because of those relationship links. The reliable sequence is contacts first, then organisations, then opportunities, with projects mapped last. Exporting from Insightly's System Settings and mapping custom fields before import keeps linked records intact, so a rep opening a contact still sees the organisation, the open opportunity, and the history attached to them.

What data is involved

  • Contacts imported first as the anchor records, with email as the dedupe key.
  • Organisations mapped to CRM companies and linked back to their contacts.
  • Leads and opportunities mapped to CRM leads and deals with stage and value retained.
  • Insightly projects mapped to deals or post-sale records depending on how your team uses them.
  • Custom fields and tags mapped so segmentation built up in Insightly survives the move.
  • Linked relationships re-established so contact-to-organisation-to-opportunity chains stay intact.

Step-by-step setup

Setup at a glance (3-5 bullets)

  • Export Insightly data (System Settings → Data Export)
  • Map Insightly custom fields to HelloGrowthCRM
  • Import records in order: contacts → organizations → opportunities
  • Validate relationships
  1. Sign in or sign up at HelloGrowthCRM. Open the login page, enter your credentials (or use Google), or choose Sign up if you need a new account. You must be signed in before you can open Settings and connect this integration.

    HelloGrowthCRM login screen: Sign in with Google, email and password fields, Remember me, and Sign up link

    Open login page(opens in a new tab)app.hellogrowthcrm.com/login

  2. Open Settings. In the left sidebar, under Admin, click Settings (you will land on the Settings area; the URL is app.hellogrowthcrm.com/settings).

    HelloGrowthCRM Settings: Admin sidebar with Settings selected, secondary menu with Communication and Integrations, and profile area

    Open Settings(opens in a new tab)app.hellogrowthcrm.com/settings

  3. Go to Integrations. On the Settings screen, use the middle settings menu. Under COMMUNICATION, click Integrations (star icon). Then find and configure this connector—the connector-specific steps below pick up from here.

    HelloGrowthCRM Settings menu highlighting COMMUNICATION and Integrations next to the Admin Settings sidebar

    Open Settings (Integrations)(opens in a new tab)app.hellogrowthcrm.com/settings

  4. Export Insightly data (System Settings → Data Export)
  5. Map Insightly custom fields to HelloGrowthCRM
  6. Import records in order: contacts → organizations → opportunities
  7. Validate relationships

Best practices

  • Import in strict order — contacts, then organisations, then opportunities — so Insightly relationship links resolve instead of breaking.
  • Decide what an Insightly project should become (an active deal, a delivery record, or an archive) before mapping, since teams use projects very differently.
  • Dedupe contacts on email in the export, because Insightly often holds the same person under more than one organisation.
  • Map Insightly tags to CRM tags or a source field so existing segmentation keeps working.
  • Validate a sample of linked records after the sandbox import — open a contact and confirm its organisation and opportunity are attached.

Best for & common use cases

SMBs outgrowing Insightly, Teams needing better mobile CRM, India-market focused businesses

  • Contact and organization hierarchy migration
  • Opportunity and project history transfer
  • Custom field mapping to HelloGrowthCRM

Expected outcomes

  • Faster lead handoff between tools and CRM owners
  • Cleaner activity history for follow-up and reporting
  • Lower manual copy-paste errors in the pipeline

Troubleshooting

  • Opportunities with no contact attached: they were imported before contacts and organisations — re-import in the correct order.
  • Projects landed as deals in an odd stage: the project target was left at default; remap projects to the intended record type.
  • Same person appears twice: the Insightly export was not deduped on email before import.

FAQ

Governance

Treat API keys and webhooks as production secrets. Align field mapping with your privacy policy and regional regulations (GDPR, marketing consent, telemarketing rules). Your admin controls which roles can install or edit integrations.