CRM migration

Migrate from Insightly CRM to Nutshell

Field-level mapping, validation, and rollback between Insightly CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Insightly CRM logo

Insightly CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

91%

10 of 11

objects map 1:1 between Insightly CRM and Nutshell.

Complexity

CModerate

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Insightly CRM to Nutshell is a lateral-tier migration for small to mid-sized sales teams seeking a simpler per-seat pricing model and a cleaner administrative interface. The core record types align closely: Insightly Organizations map to Nutshell Companies, Contacts map to Nutshell People, and Opportunities map to Nutshell Deals. The structural difference that affects migration is Insightly's explicit linking model, which uses dedicated link records to associate Contacts with Organizations rather than embedding the relationship in the parent record. We resolve these after parent records are created using Nutshell's native People-to-Company association API. Insightly's custom fields require a FIELD_NAME lookup before any write operation, so we build a metadata reference table at migration start to prevent silent data loss. Workflow Automations live in Insightly's configuration layer and do not migrate; we deliver a written map of every active automation for your Nutshell admin to rebuild post-migration.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Insightly CRM logo

Insightly CRM

What's pushing teams away

  • Workflow automation and AI Copilot are locked behind the Professional tier, pushing teams with automation needs to higher-cost plans quickly as headcount grows.
  • Custom field handling requires referencing FIELD_NAME in API calls, and the UI documentation is described as incomplete and overwhelming by power users.
  • Setup is time-consuming, particularly for automation configuration, with users reporting frequent timeouts during the process.
  • Limited customization compared to enterprise CRMs — some users find field-level tailoring insufficient for complex sales processes.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Insightly CRM objects map to Nutshell

Each row shows how a Insightly CRM object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Insightly CRM

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Insightly Leads map directly to Nutshell Leads. Lead status, source, owner, and custom fields migrate. Any lead scoring or rating fields map to Nutshell's built-in lead rating scale or to a custom numeric field.

Insightly CRM

Organization

maps to

Nutshell

Company

1:1
Fully supported

Insightly Organizations map 1:1 to Nutshell Companies. Organizations are imported first as parent records before Contacts to satisfy the Company lookup reference. The Organization's name becomes the Company name, and the domain or website maps to the Nutshell Company URL.

Insightly CRM

Contact

maps to

Nutshell

Person

1:1
Fully supported

Insightly Contacts map 1:1 to Nutshell People. Standard fields (name, email, phone, address) migrate directly. All custom fields on Contact require a FIELD_NAME lookup via /CustomFields/Contacts before writes to prevent silent field drops. After Organizations are created and Contacts are imported, we reconstruct the Contact-to-Organization link using Nutshell's People-Company association mechanism.

Insightly CRM

Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

Insightly Opportunities map to Nutshell Deals. Pipeline stage names migrate as Nutshell Deal stage values, with a stage name mapping table applied at migration time. Monetary value, probability, expected close date, owner, and custom fields transfer directly. The Opportunity-to-Organization link becomes the Deal-to-Company association in Nutshell.

Insightly CRM

Pipeline Stage

maps to

Nutshell

Deal Stage

lossy
Fully supported

Insightly pipeline stages are custom-named strings per pipeline. We build a stage name mapping table at discovery and configure corresponding Deal stages in Nutshell before importing any Opportunities. Probability percentages transfer per stage, and any custom stage order is preserved.

Insightly CRM

Project

maps to

Nutshell

Deal or external

1:1
Fully supported

Insightly Projects have no direct Nutshell equivalent. We import Project records as a custom object in Nutshell or convert them to Deals if the project scope maps to a revenue milestone. If the customer's post-migration workflow uses a dedicated project management tool, we flag Project records for routing to that system. Project tasks migrate as Tasks linked to the parent Project record.

Insightly CRM

Task

maps to

Nutshell

Task

1:1
Fully supported

Insightly Tasks map to Nutshell Tasks. Task status values (Not Started, In Progress, Completed, Deferred) map to Nutshell Task status equivalents. Owner, due date, priority, and custom fields transfer. Tasks linked to Opportunities carry the Deal association into Nutshell.

Insightly CRM

Note

maps to

Nutshell

Comment

1:1
Fully supported

Insightly Notes (Comments) map to Nutshell Comments. Note body, author, and creation date transfer. The Note's link to the parent record (Contact, Organization, or Opportunity) is reconstructed in Nutshell as a Comment on the corresponding Nutshell record.

Insightly CRM

Custom Object

maps to

Nutshell

Custom Object

1:1
Fully supported

Insightly Custom Objects migrate to Nutshell Custom Objects with equivalent schema. We pre-create the destination schema including all custom fields, field types, and lookup relationships before any data import. Nutshell's custom object configuration interface handles the schema setup during the approach phase. Customers should confirm which custom objects carry critical business data during scoping.

Insightly CRM

Tag

maps to

Nutshell

Tag

1:1
Fully supported

Insightly Tags (flat string labels on Contacts, Organizations, Opportunities, Projects) migrate as Nutshell Tags. Tag arrays export as plain string lists and import as Nutshell Tag values on the corresponding record. Tag semantics are preserved as-is; no transformation is applied.

Insightly CRM

Attachment

maps to

Nutshell

Attachment (metadata only)

1:1
Fully supported

Insightly file attachments are stored as URL or blob references. We do not migrate attachment binary data. We export attachment metadata (filename, URL, associated record type and ID) and deliver it as a reference table so the customer's admin can relink or re-upload files in Nutshell post-migration.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Insightly CRM logo

Insightly CRM gotchas

High

Free plan record cap applies to all Insightly objects

High

API rate limits vary by plan and reset daily

Medium

Custom fields require FIELD_NAME lookup before writes

Medium

XML export only captures default fields for migrations out

Medium

Link relationships must be rebuilt via dedicated endpoints

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Insightly native XML export drops all custom fields

    Insightly's built-in export-to-ZIP function produces XML files containing only default (standard) fields. Custom fields are not included in these XML exports. We bypass the native XML export entirely and pull all records including custom fields directly from the Insightly API. This requires a paid Insightly plan with sufficient API daily request quota. Teams on the free plan (1,000 API requests per day) may need a trial on a paid tier for bulk export if their total record count exceeds what the free daily limit can export in a single window. We flag record count and plan tier at discovery.

  • Custom fields require FIELD_NAME lookup before any write

    Insightly does not expose custom field IDs in record objects. Updating a Contact's custom field requires a prior call to /CustomFields/Contacts to retrieve the FIELD_NAME identifier. Without this step, writes silently ignore the custom field. We retrieve all custom field metadata per object type at the start of every migration, build a FIELD_NAME reference table, and use it consistently across all record writes. This step is the primary reason Insightly API migrations are not equivalent to a simple CSV import.

  • Nutshell has no native project management module

    Insightly includes native project management tied to closed Opportunities, which is a feature many small teams use for post-sale delivery tracking. Nutshell has no equivalent built-in module. We import Insightly Projects as a custom object or convert them to Deals depending on business context, but the customer must plan for post-migration project management routing. This is a workflow decision made during scoping, not a data migration limitation we resolve automatically.

  • Insightly Workflow Automations do not migrate

    Insightly Workflow Automations live in the configuration layer and are not accessible via API. We do not migrate them as code. We deliver a written inventory of every active Insightly Workflow with its trigger, conditions, and actions, and the customer's Nutshell admin rebuilds them as Nutshell Workflows post-migration. Workflows that trigger on Insightly-specific events (e.g., Project creation from Opportunity) require process redesign since Nutshell has no equivalent trigger event.

  • Nutshell has more limited UI customization than Insightly

    Insightly supports custom fields, calculated fields, dynamic page layouts, and custom objects even on lower tiers. Nutshell's front-end customization is more constrained; custom fields and layouts are available but dynamic page layouts and calculated fields are not equivalent features. Teams migrating from Insightly that rely on extensive field-level UI tailoring need to validate that Nutshell's customization surface meets their requirements before migration, not after.

Migration approach

Six steps for a successful Insightly CRM to Nutshell data migration

  1. Discovery and scoping

    We audit the source Insightly instance across all object types: Leads, Contacts, Organizations, Opportunities, Projects, Tasks, Notes, Tags, and Custom Objects. We count records per object type, retrieve all custom field metadata via /CustomFields/{objectName} endpoints, list active Workflow Automations for the inventory document, and map Insightly pipeline stages to Nutshell Deal stage equivalents. We also confirm the Insightly plan tier to validate API daily request limits and identify whether the customer needs a paid-plan trial for bulk export.

  2. Nutshell schema setup

    We configure the Nutshell destination before any data import. This includes creating any required custom fields matching Insightly's custom field schemas, configuring Deal stages that map from Insightly pipeline stages, setting stage probabilities, and creating Custom Objects that mirror Insightly Custom Objects. Nutshell's custom field and object configuration is performed by the customer's Nutshell admin or under their credentials; we provide the configuration specification as part of our approach deliverable.

  3. Test migration and reconciliation

    We run a sample migration using a subset of records to validate field mapping, custom field resolution via FIELD_NAME lookup, link reconstruction (Contact-to-Organization), and stage name mapping. The customer's admin reviews the test output against the Insightly source and confirms the mapping. Any corrections to field mapping, stage name mapping, or custom object schema are made before the production migration begins.

  4. Production migration in dependency order

    We run production migration in record-dependency order: Companies (from Organizations) first to serve as parent records, then People (from Contacts) with FIELD_NAME custom field writes and post-import link reconstruction to Companies, then Leads, then Deals (from Opportunities) with stage name and probability mapping, then Tasks and Notes with parent record associations, then Custom Objects last. Each phase emits a row-count reconciliation report before the next phase begins.

  5. Cutover and automation handoff

    We freeze Insightly writes during the cutover window, run a delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the Insightly Workflow Automation inventory document to the customer's admin team with a recommended Nutshell Workflow equivalent for each automation. We support a one-week hypercare window for reconciliation issues raised by the customer's team. We do not rebuild Insightly Workflows as Nutshell Workflows inside the migration scope; that is a separate engagement or an internal admin task.

Platform deep dives

Context on both ends of the pair

Insightly CRM logo

Insightly CRM

Source

Strengths

  • CRM, marketing automation, and project management unified in one subscription, reducing tool sprawl for SMBs.
  • Free plan for 2 users and a 2,500-record cap provides a low-risk evaluation environment.
  • AppConnect delivers 500+ no-code integrations with mainstream business tools without requiring developer resources.
  • Modern UI with faster onboarding compared to legacy CRM alternatives, backed by positive ease-of-setup scores on G2.
  • Project creation directly from closed Opportunities keeps post-sale work connected to the originating deal.

Weaknesses

  • Workflow automation and AI Copilot require the Professional tier, making the Plus plan unsuitable for teams with automation needs.
  • Custom field handling requires FIELD_NAME API lookups, which adds complexity to integrations and migrations.
  • Setup time and reported timeouts during automation configuration create friction for new administrators.
  • Documentation is described as incomplete and overwhelming by power users, according to G2 review themes.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Moderate CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Insightly CRM and Nutshell.

  • Object compatibility

    B

    3 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    C

    Insightly CRM: 10 requests per second; daily limit varies by plan (starting at 1,000 requests/day for free plan).

  • Data volume sensitivity

    B

    Insightly CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Insightly CRM to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Insightly CRM to Nutshell data migrations

Answers to the questions buyers ask most during Insightly CRM to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Insightly CRM to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Insightly-to-Nutshell migrations complete in two to four weeks for accounts under 10,000 total records across all object types. Migrations exceeding 10,000 records, involving multiple Insightly pipelines, large note or task histories, or Insightly Projects requiring scoping for external project management routing, extend to four to eight weeks. Timeline is driven by record count, the number of custom fields requiring FIELD_NAME resolution, and the customer's internal review and sign-off cycle on the test migration output.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Insightly CRM.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day