Skip to content
Get a quote

Insightly CRM to Zoho CRM migration

We migrate Organizations, Contacts, Leads, and Deals from Insightly CRM into Zoho CRM with explicit Contact-to-Organization link reconstruction, custom field metadata resolved via FIELD_NAME lookup before writes, and pipeline stage values mapped through a customer-approved stage table at cutover.

Short answer

FlitStack AI migrates accounts, contacts, leads, deals and pipeline stages from Insightly CRM to Zoho CRM, 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: 3-5 weeks.

By

Source Insightly CRM
DestinationZoho CRM
AccountContactLeadDealPipeline Stage
Mapped field by field · sample run · one-click rollback

What moves from Insightly CRM to Zoho CRM?

Moving from Insightly CRM to Zoho CRM restructures how parent-child relationships and pipeline stages are handled.

Read the full summary

Insightly stores Organizations as the top-level company record and requires explicit link records to associate Contacts; Zoho CRM maps Organizations to Accounts and enforces the relationship through a standard Account-Contact lookup, meaning we must sequence Account creation before Contact import and re-establish every Contact-Organization link using Zoho's association API. Insightly's custom fields require a FIELD_NAME lookup via the /CustomFields/{object} endpoint before any write operation; Zoho CRM creates custom fields during import from a pre-built schema. We resolve both of these dependency chains before data moves. Workflow automations and project-task structures built inside Insightly do not transfer as configuration; we deliver a written Blueprint and workflow inventory for the customer's Zoho admin to rebuild. The native Zoho migration wizard supports standard field mapping but silently drops custom modules and does not preserve the full activity timeline, which is why a direct API migration is the correct approach for data integrity.

1:1

Organization → Account

Insightly Organizations map directly to Zoho CRM Accounts.

How it maps

Organization Name becomes Account Name; all address fields (shipping and billing) map to the corresponding Zoho Account address fields. We import Accounts first in every migration to satisfy the parent lookup required by Contact records. Organization Owner maps to Zoho Account Owner by email match against Zoho Users.

1:1

Contact → Contact

Insightly Contacts map 1:1 to Zoho CRM Contacts.

How it maps

All standard fields (First Name, Last Name, Email, Phone, Mobile, Mailing Address) map directly. Prefix maps to Zoho Salutation. We resolve the Contact's parent Account by looking up the Organization name from the Insightly link record and matching it to the Zoho Account created in the prior phase. If multiple Contacts share one Organization, we re-apply the link to each Contact after Account creation.

1:1

Lead → Lead

Insightly Leads map directly to Zoho Leads.

How it maps

Lead Status maps to Zoho Lead Status with a value mapping table applied at migration time. Any custom fields on Insightly Leads are resolved via FIELD_NAME lookup and created as corresponding Zoho custom fields before import. Lead Owner maps to Zoho User by email match.

1:1

Opportunity → Deal

Insightly Opportunities map to Zoho CRM Deals.

How it maps

Stage name mapping is the most critical step: Insightly uses custom-named stage strings while Zoho uses stage values configured per pipeline. We build a customer-approved stage mapping table during scoping and apply it during migration. Probability percentage maps to Zoho Probability field. Closed-Won and Closed-Lost reasons map to Zoho Loss Reason and Won Reason if those custom fields are present in the destination.

configuration

Pipeline Stage → Pipeline Stage

Each Insightly Opportunity pipeline becomes a Zoho CRM pipeline within the Deals module.

How it maps

We replicate stage names and probabilities from Insightly into Zoho's pipeline configuration before migration begins. If the customer has multiple pipelines in Insightly, we create corresponding Zoho pipelines and map Opportunity records to the correct pipeline during import using the pipeline_id field.

1:1

Tag → Tag

Insightly Tags are flat string labels on Contacts, Organizations, Opportunities, and Projects.

How it maps

Zoho CRM supports Tags as a native multi-value field. We export tag arrays as string lists and import them as Zoho Tags. Tag semantics are preserved as-is; no transformation is applied beyond the string array to tag-list conversion.

What moves11 objects
Insightly CRMZoho CRM
  • OrganizationAccount1:1
  • ContactContact1:1
  • LeadLead1:1
  • OpportunityDeal1:1
  • Pipeline StagePipeline Stagetransformed
  • TagTag1:1

+ 5 more in the mapping below

How Insightly CRM and Zoho CRM 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.

DimensionInsightly CRMZoho CRM
Top-level company modelOrganizations with explicit link records to associate ContactsAccounts with native Account-Contact lookup relationship
Lead modelSeparate Lead object with own lifecycle and propertiesSeparate Leads module with standard field set and conversion workflow
Custom field handlingRequires FIELD_NAME lookup via API before writes; silent drop without itCreates custom fields during import or via pre-built schema; no FIELD_NAME required
Activity (engagement) historyNotes, Tasks, and Events as standalone linked objects with explicit link recordsActivities attached to records via standard Zoho activity model; notes as separate module
Project managementBuilt-in Projects linked to closed Opportunities, with task hierarchiesProjects as a separate module or via Zoho Projects integration; not native CRM object
AutomationWorkflow Automation gated at Professional tier ($49/user/mo)Blueprint and Workflow Rules available from Standard tier ($14/user/mo)
Free tier record cap2,500 records across all objects on free plan3 users on free plan; no hard record cap, per-user storage limits apply

What to watch for in a Insightly CRM to Zoho CRM migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Zoho's native migration wizard does not transfer custom modules

Zoho CRM's built-in Insightly migration wizard (Setup > Data Administration > Import > Insightly) maps standard fields only and explicitly notes that custom modules are not supported in API migrations.

How we handle it

Teams that rely on Insightly Custom Objects must use a direct API migration with custom field schema pre-built in Zoho. We create the full custom object schema in Zoho before migration begins, including field types, picklist values, and lookup relationships, and we validate that the Zoho custom field types are compatible with the Insightly source types before any data moves.

high

Insightly link records must be reconstructed after Zoho import

Insightly stores Contact-to-Organization associations as explicit link records separate from the Contact and Organization objects.

How we handle it

Zoho CRM enforces this relationship through the Account Name lookup field on Contact, which is set at insert time. We export Insightly link records, import Accounts first, then Contacts, then update each Contact's AccountId lookup by resolving the linked Organization name to the corresponding Zoho Account ID. If link records are not exported and reconstructed, Contacts arrive in Zoho without an Account association, breaking reporting and Activity timeline grouping.

medium

Custom field values silently drop without FIELD_NAME resolution

Insightly does not expose custom field IDs in record objects.

How we handle it

Writing a Contact with a custom field value requires looking up FIELD_NAME via /CustomFields/Contacts before the write call. Without this step, Insightly's API silently ignores the custom field value. We retrieve all custom field metadata per object at the start of every migration, build a FIELD_NAME reference table, and apply it consistently across all record writes. We verify a sample of records post-import to confirm custom field values are present in Zoho.

medium

Insightly XML export omits custom fields entirely

Insightly's native export-to-ZIP function produces XML files containing only standard (default) fields.

How we handle it

Custom fields are not included in these exports. When migrating out of Insightly via the native export path, custom field data is lost. We bypass the XML export entirely and pull all records including custom fields directly from the Insightly API. We inform customers of this limitation at scoping and use the API path exclusively for outbound migrations.

medium

Duplicate records require pre-migration deduping

Insightly CRM environments frequently contain duplicate Organizations (variations in company name spelling), duplicate Contacts (same email under different Organizations), and duplicate Opportunities.

How we handle it

Zoho CRM enforces unique email addresses per Contact and will reject imports for duplicate emails without a dedupe rule override. We run a dedupe analysis during scoping, present a duplicate record report to the customer, and apply a customer-approved dedupe strategy (merge, keep newest, keep most complete) before migration begins. Skipping this step results in import failures that require re-running phases.

How the migration runs

  1. Discovery and data audit

    We audit the source Insightly CRM across plan tier, total record counts per object (Organizations, Contacts, Leads, Opportunities, Projects, Tasks, Notes), custom field metadata per object via FIELD_NAME lookup, active link records between Contacts and Organizations, pipeline count and stage names, and any active Workflow Automations.

    What this step covers

    We pair this with a Zoho CRM edition check (Standard $14/user/mo, Professional $23/user/mo, Enterprise $40/user/mo) to confirm the destination tier supports the required modules. The discovery output is a written migration scope document covering record counts, schema gaps, dedupe findings, and a stage name mapping table for customer approval.

  2. Schema pre-build in Zoho CRM

    We create all required custom fields in Zoho CRM before any data import, matching field types to the Insightly FIELD_NAME metadata (text to single-line, date/datetime to date, picklist to picklist, multi-select dropdown to multi-select).

    What this step covers

    We create custom modules for any Insightly Custom Objects, configure lookup relationships, and set up Zoho CRM pipelines and stage values from the approved stage mapping table. If the customer uses Zoho Projects, we configure the project schema in Zoho Projects at this stage. Schema is validated in a Zoho sandbox or parallel org before production migration begins.

  3. Dedupe and data cleanup

    We run a structured dedupe analysis across Organizations (by name similarity), Contacts (by email address), and Opportunities (by name and linked Account).

    What this step covers

    We present a dedupe report to the customer with a recommended resolution per duplicate group (merge, keep one, discard). The customer approves the dedupe strategy before we begin data export. We also standardize date formats, phone number formatting, and null-value handling at this stage so that the import pipeline is clean.

  4. Export and link record extraction

    We export all record types from Insightly via API in dependency order: Organizations first, then Contacts, then Leads, then Opportunities, then Projects, Tasks, and Notes.

    What this step covers

    We export Insightly link records separately (the Contact-Organization association records) and store them as a separate mapping file. Custom field values are retrieved alongside standard fields using the FIELD_NAME reference table built during discovery. We pace exports within Insightly's 10 requests-per-second limit and chunk large datasets across multiple days when the daily request quota is constraining.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Organizations), then Contacts (with AccountId resolved via the link record mapping file), then Leads, then Deals (with pipeline and stage mapping applied), then Tasks and Notes (linked to parent records by Zoho ID), then Projects (as custom module or Zoho Projects), then custom object records (with all lookup fields resolved).

    What this step covers

    Each phase emits a row-count reconciliation report comparing Insightly export counts to Zoho import counts. We validate a random sample of 25-50 records per object type against the source before proceeding to the next phase.

  6. Cutover, delta sync, and Blueprint handoff

    We freeze Insightly writes during cutover, run a final delta migration of any records modified during the migration window, then set Zoho CRM as the system of record.

    What this step covers

    We deliver a written Blueprint and Workflow inventory for every active Insightly Workflow Automation, with a recommended Zoho Blueprint or Workflow Rule equivalent and trigger/condition/action mapping. The customer's Zoho admin rebuilds automations post-migration. We support a one-week hypercare window for reconciliation issues. We do not rebuild Insightly Workflows as Zoho Blueprint or Workflow Rules inside the migration scope; that is a separate Zoho implementation engagement.

Insightly CRM Zoho CRM
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Zoho CRMRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
7-10 weeksLarge or heavily customised accounts

A quote scales with record volume, custom field count, and pipeline stage mapping complexity. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Insightly CRM to Zoho CRM →

Why teams move from Insightly CRM to Zoho CRM

  • Teams cite Zoho CRM's broader feature depth at lower tiers as a reason for switching. Workflow automation (Blueprint + Workflow Rules) is available from Zoho's Standard plan at $14/user/month versus Insightly Professional at $49/user/month. Gartner Peer Insights rates Zoho CRM at 4.4 stars (556 reviews) versus Insightly at 4.2 stars (721 reviews), with reviewers noting Zoho's feature breadth as a differentiator for growing teams that need automation without the Professional-tier price gate.
  • Insightly's 2,500-record cap on the free plan catches teams that have grown beyond small-scale evaluation. Every object type (Contacts, Organizations, Opportunities, Projects, Tasks) counts against the cap, and API exports can time out or fail on plans approaching the limit. Zoho's free plan covers 3 users without a hard record ceiling, making it a direct replacement for teams that outgrew Insightly's free tier.
  • Reviewers on Reddit and comparison threads describe Insightly's documentation as incomplete and overwhelming, particularly for automation configuration and custom field setup. Zoho's documentation, partner ecosystem, and native migration wizard (available in Zoho CRM Setup > Data Administration > Import > Insightly) are cited as more accessible for small teams managing their own implementation without a dedicated admin.
  • Insightly locks marketing automation (email sequences, lead nurturing) behind higher tiers or its separate Marketing product, requiring teams to manage multiple subscriptions. Zoho CRM's email automation, web forms, and Zia AI assistant are included from the Professional tier ($23/user/mo), reducing the tool-stack complexity for teams that need CRM + marketing automation under one billing relationship.
  • Zoho CRM's native integration with 55+ Zoho apps (Books, Desk, Projects, Campaign, Analytics) provides a tighter ecosystem than Insightly's AppConnect marketplace for teams already using or planning to use Zoho's broader suite. Reviewers cite native Zoho-to-Zoho data flow as more reliable than third-party integration routes.

Questions, answered

Insightly CRM to Zoho CRM migration questions

How long does an Insightly CRM to Zoho CRM migration take?

Most migrations land between three and five weeks for accounts under 15,000 records with no custom objects, clean standard field mapping, and an approved dedupe strategy. Migrations with custom objects, complex multi-field schemas (over 30 custom fields per object), project-task hierarchies, or large note and task histories move to seven to ten weeks because of schema pre-build, FIELD_NAME resolution, link reconstruction, and Zoho Projects configuration time.

Do Insightly Workflow Automations and Project-Task structures migrate to Zoho CRM?

No. Insightly Workflow Automations live in the configuration layer and do not transfer to Zoho Blueprint or Workflow Rules. We deliver a written inventory of every active Insightly Workflow with its trigger, conditions, actions, and a recommended Zoho Blueprint or Workflow Rule equivalent for the customer's Zoho admin to rebuild. Project-Task structures require Zoho Projects (a separate Zoho application) to migrate as full hierarchies; without Zoho Projects, we import Projects as a CRM custom module with task data flattened into a sub-list. This limitation is flagged during scoping.

Can we use Zoho's native Insightly migration wizard instead of FlitStack AI?

Zoho's native wizard (Setup > Data Administration > Import > Insightly) is viable for small migrations with no custom objects and no complex link relationships. It does not transfer custom modules, does not preserve custom field values, and does not handle Contact-Organization link reconstruction beyond standard field mapping. For migrations that include custom objects, multiple custom fields per object, project records, or a large activity history, the native wizard is insufficient and a direct API migration with FIELD_NAME resolution and link reconstruction is the correct approach.

What data do we lose if we use Insightly's native XML export for migration?

Insightly's native export-to-ZIP function produces XML files containing only standard (default) fields. Custom fields are not included in these exports. If your Insightly environment uses any custom fields (and most mid-market environments do), using the native XML export means those custom field values are permanently lost during migration. We bypass the XML export entirely and pull all records including custom fields via the Insightly API using the FIELD_NAME lookup approach to preserve custom field data.

How do we handle duplicate records during migration?

Insightly CRM environments frequently contain duplicate Organizations (name variations), duplicate Contacts (same email under different Organizations), and duplicate Opportunities. Zoho CRM enforces unique email addresses per Contact and will reject imports for duplicate emails. We run a structured dedupe analysis during scoping, present a duplicate report to the customer with recommended resolutions, and apply the customer-approved dedupe strategy (merge, keep newest, keep most complete) before migration begins. Skipping dedupe results in import failures that require re-running phases.

Do we migrate Insightly attachments and file links?

Insightly stores attachment metadata (filename, URL, associated record) as URL or blob references. We do not migrate attachment binary data directly. We export attachment metadata (filename, associated record type, associated record ID) and present it to the customer as a reference list for manual re-attachment or for re-upload via Zoho CRM's file attachment feature post-migration. Files stored in third-party integrations (Google Drive, Dropbox links in Insightly Notes) are not migrated and must be re-linked in Zoho manually.

Can FlitStack AI also configure Zoho CRM post-migration (Blueprints, Workflow Rules, layouts)?

Standard migration scope covers data migration only. We deliver a written Blueprint and Workflow inventory for every active Insightly Workflow with trigger/condition/action mapping, but the rebuild of those automations in Zoho Blueprint or Workflow Rules is outside standard migration scope. Layout configuration, field security, role-based page layouts, and Zoho email template setup are also outside scope unless separately scoped as a Zoho implementation engagement. We can provide a separate estimate for post-migration Zoho configuration if needed.

Get a quote

Moving from Insightly CRM to Zoho CRM?

Tell us roughly how many records and objects you have. We scope the mapping and the Zoho CRM setup with you, then send a quote.

Get a quote