CRM migration
Field-level mapping, validation, and rollback between Insightly CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Insightly CRM
Source
Nutshell
Destination
Compatibility
10 of 11
objects map 1:1 between Insightly CRM and Nutshell.
Complexity
CModerate
Timeline
2-4 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Nutshell
Lead
1:1Insightly 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
Nutshell
Company
1:1Insightly 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
Nutshell
Person
1:1Insightly 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
Nutshell
Deal
1:1Insightly 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
Nutshell
Deal Stage
lossyInsightly 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
Nutshell
Deal or external
1:1Insightly 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
Nutshell
Task
1:1Insightly 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
Nutshell
Comment
1:1Insightly 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
Nutshell
Custom Object
1:1Insightly 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
Nutshell
Tag
1:1Insightly 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
Nutshell
Attachment (metadata only)
1:1Insightly 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.
| Insightly CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | Lead1:1 | Fully supported | |
| Organization | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Pipeline Stage | Deal Stagelossy | Fully supported | |
| Project | Deal or external1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Note | Comment1:1 | Fully supported | |
| Custom Object | Custom Object1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Attachment | Attachment (metadata only)1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Free plan record cap applies to all Insightly objects
API rate limits vary by plan and reset daily
Custom fields require FIELD_NAME lookup before writes
XML export only captures default fields for migrations out
Link relationships must be rebuilt via dedicated endpoints
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
Insightly CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Insightly CRM and Nutshell.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Insightly CRM: 10 requests per second; daily limit varies by plan (starting at 1,000 requests/day for free plan).
Data volume sensitivity
Insightly CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Insightly CRM to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Insightly CRM
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.