CRM migration
Field-level mapping, validation, and rollback between Insightly CRM and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Insightly CRM
Source
monday CRM
Destination
Compatibility
8 of 10
objects map 1:1 between Insightly CRM and monday CRM.
Complexity
CModerate
Timeline
3-5 weeks
Overview
Moving from Insightly CRM to Monday.com CRM is a structural migration that translates a relational CRM data model into a board-based work-management CRM. Insightly organizes around four core objects—Leads, Contacts, Organizations, and Opportunities—linked via explicit link records that must be reconstructed in Monday.com as board Groups, Items, and Connections. Monday.com CRM does not have a native Leads object separate from Contacts; Insightly Leads convert to Contact Items with a custom Lead Status column. We preserve pipeline stages as Monday.com Status columns, Organizations as Company Items, and Opportunities as Deal Items with monetary columns. We do not migrate Insightly Workflow Automations or Custom Objects as code; we deliver a written inventory for the customer's admin to rebuild as Monday.com boards and automations. Attachments migrate as metadata only—file binaries are not transferred. The migration timeline typically lands between three and six weeks for SMB-record volumes with straightforward pipeline structures.
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 monday CRM, 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
monday CRM
Person Item with Lead Status column
1:1Insightly Leads map to Monday.com CRM People Items. We add a custom Lead Status column (type: Status) to the People board and map the Insightly Lead Status values to the Monday.com status group labels (e.g., New, Contacted, Qualified). The original Lead score (if present) migrates to a Number column. Insightly Leads that have already converted to Contacts in Insightly are migrated as Contacts with the conversion flag preserved rather than as Leads.
Insightly CRM
Contact
monday CRM
Person Item on CRM board
1:1Insightly Contacts map directly to Monday.com CRM People Items. Standard fields (name, email, phone, address) map to the corresponding Monday.com column types. Custom fields migrate to Monday.com custom columns (Text, Number, Date, Dropdown, etc.) using the FIELD_NAME reference we build from the /CustomFields/Contacts endpoint at the start of migration. Contact records are imported after Organization Items so that the Organization lookup is resolved at insert time.
Insightly CRM
Organization
monday CRM
Company Item on CRM board
1:1Insightly Organizations map to Monday.com CRM Company Items. Organization name, domain, address, phone, and industry fields map to the corresponding Monday.com Company column types. Custom fields on Organization migrate to custom columns on the Company board using the same FIELD_NAME lookup approach as Contacts. Organizations are imported first in the sequence to satisfy the Organization lookup on inbound Contacts.
Insightly CRM
Contact-to-Organization Link
monday CRM
Company Connection on Person Item
1:1Insightly stores Contact-to-Organization relationships as explicit link records that are not embedded in the primary Contact object. We export all link records separately, then set the Monday.com CRM Company Connection on each Person Item during import. This is the critical sequencing step: Organizations import first, Contacts import second with the Company Connection resolved, then link records are applied. Without this step, the Contact-to-Company relationship is lost.
Insightly CRM
Opportunity
monday CRM
Deal Item on pipeline board
1:1Insightly Opportunities map to Deal Items on Monday.com CRM boards. The Opportunity name, monetary value (Amount), probability, expected close date, and owner migrate to the corresponding Monday.com column types (Text, Numbers with currency format, Percentage, Date, Person). Insightly pipeline stages map to Monday.com Status column values, which we configure before migration using a stage name mapping table derived from the customer's Insightly pipeline setup.
Insightly CRM
Pipeline Stage
monday CRM
Status column values
lossyInsightly Opportunity pipeline stages are custom-named strings (e.g., Discovery, Proposal, Negotiation, Closed Won) attached to each Opportunity. Monday.com CRM uses Status column values as the stage representation on a deal board. We create a stage mapping table during scoping and configure the Status column groups in Monday.com to match the Insightly pipeline stages before Opportunity import. Probability percentages migrate to a separate Numbers column (type: Percentage) if the customer wants to track probability alongside stage.
Insightly CRM
Project
monday CRM
Board or Item Group
1:1Insightly Projects migrate to Monday.com Work Management boards or to Item Groups within an existing board, depending on the customer's target structure. Project name, description, status, start date, and end date map to Monday.com board columns. Project tasks migrate as Items within the board, with task status mapped to a Status column. If the customer wants Projects tied to closed Opportunities, we recommend a Monday.com board with an Opportunity Connection column linking the Project board Item to the originating Deal Item.
Insightly CRM
Task
monday CRM
Item on Task board
1:1Insightly Tasks linked to Contacts, Organizations, or Opportunities migrate as Items on a dedicated Tasks board or as Items within the relevant CRM board group. Task status (Not Started, In Progress, Completed, Deferred) maps to Monday.com Status column values. Due date, priority, and assigned owner migrate to Date, Status, and Person column types. The original task assignee resolves against the User mapping established during discovery.
Insightly CRM
Note (Comment)
monday CRM
Text column or Update
1:1Insightly Notes migrate as Updates on the relevant Monday.com Item (Person, Company, or Deal). Note body, author name, and creation timestamp map to the Update text, author attribution, and timestamp. If the note is linked to a specific Contact or Opportunity in Insightly, the Update is posted on the corresponding Item in Monday.com. Standalone notes without a parent link become Updates on the most recently created relevant Item.
Insightly CRM
Custom Object
monday CRM
Separate Board with custom columns
1:manyInsightly Custom Objects have no direct Monday.com CRM equivalent. We treat each Custom Object as a separate Monday.com Board, creating the board schema from the Custom Object field definitions (field name, field type, picklist values). Custom Object records migrate as Items within the new board. Lookup relationships between Custom Objects map to Monday.com Connections columns if the destination plan supports them, or to Text columns holding the related record name for manual lookup. The customer should validate whether the resulting board structure supports their use case.
| Insightly CRM | monday CRM | Compatibility | |
|---|---|---|---|
| Lead | Person Item with Lead Status column1:1 | Fully supported | |
| Contact | Person Item on CRM board1:1 | Fully supported | |
| Organization | Company Item on CRM board1:1 | Fully supported | |
| Contact-to-Organization Link | Company Connection on Person Item1:1 | Fully supported | |
| Opportunity | Deal Item on pipeline board1:1 | Fully supported | |
| Pipeline Stage | Status column valueslossy | Fully supported | |
| Project | Board or Item Group1:1 | Fully supported | |
| Task | Item on Task board1:1 | Fully supported | |
| Note (Comment) | Text column or Update1:1 | Fully supported | |
| Custom Object | Separate Board with custom columns1:many | 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
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and data audit
We audit the source Insightly account across all objects: Leads, Contacts, Organizations, Opportunities, Projects, Tasks, Notes, Custom Objects, and Tags. We export record counts per object, identify custom field definitions via /CustomFields/{objectName} endpoints, retrieve pipeline and stage names from /Pipelines, and extract link records from the links API. We also inventory active Workflow Automations for the rebuild handoff document. This output is a written migration scope with record counts, field mapping draft, and a Monday.com board schema proposal.
Monday.com board schema design
We design the Monday.com board structure before any data moves. The People board holds Contact and Lead Items with a custom Lead Status column; the Companies board holds Organization Items; Deal boards hold Opportunity Items with Status columns mapped to Insightly pipeline stages. Each board gets its column types defined (Text, Email, Phone, Date, Numbers, Person, Status, etc.) based on the Insightly field inventory. Custom Objects become separate boards with columns derived from the Custom Object field definitions. We validate the schema in a Monday.com test workspace before production.
FIELD_NAME reference table and custom field mapping
We retrieve all Insightly custom field metadata from /CustomFields/{objectName} endpoints at the start of every migration. We build a FIELD_NAME-to-column-type reference table and apply it consistently across all record writes. Without this step, custom field writes silently fail in Insightly and Monday.com column creation may mis-match field types. We also map Insightly picklist values to Monday.com Status column group labels during this step.
Sandbox migration and reconciliation
We run a full migration into a Monday.com test workspace using a representative data sample (at minimum 100 records per object type). The customer reconciles record counts, spot-checks field values on 25-50 random Items against the Insightly source, verifies Organization-to-Contact links are present on Person Items, and validates stage mapping on Deal Items. Schema corrections and mapping adjustments happen in the sandbox, not in production.
Production migration in dependency order
We run production migration in sequence: Companies first (to satisfy lookups), then People Items with Company Connection resolved, then Deals with pipeline stage mapping applied, then Projects and Tasks. Link records are reconstructed during the People import phase. Notes migrate as Updates on the relevant Items. Custom Object boards run in parallel with independent import sequences. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation handoff
We freeze Insightly writes during cutover, run a final delta migration of any records modified during the migration window, then hand off Monday.com as the system of record. We deliver the Workflow Automation inventory document listing every active Insightly automation with trigger, conditions, actions, and recommended Monday.com Automation equivalent. We support a one-week hypercare window for reconciliation issues. We do not rebuild Insightly Workflows as Monday.com Automations inside the migration scope; that work is handled by the customer's admin using the inventory document.
Platform deep dives
Insightly CRM
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 2 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 monday CRM.
Object compatibility
2 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 monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Insightly CRM to monday CRM 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 monday CRM
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.