Insightly CRM to Dynamics 365 migration
We migrate Organizations, Contacts, Leads, Opportunities, and Notes from Insightly CRM into Microsoft Microsoft Dynamics 365 Sales with the Contact-to-Organization link model resolved before import, pipeline stages explicitly mapped across the schema boundary, and Insightly custom fields handled via FIELD_NAME lookup before any Dataverse API writes proceed.
FlitStack AI migrates accounts, contacts, leads, opportunities and sales process + stages from Insightly CRM to Dynamics 365, 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: 2-4 weeks.

What moves from Insightly CRM to Dynamics 365?
Moving from Insightly CRM to Microsoft Microsoft Dynamics 365 Sales is a migration between platforms with fundamentally different relationship models.
Read the full summary
Insightly uses explicit link records to associate Contacts with Organizations; Microsoft Dynamics 365 Sales uses native Account-Contact lookups with a parent-child hierarchy that is automatic once AccountId is set on the Contact. We resolve this by importing Organizations first, then Contacts with AccountId resolved from the Organization mapping, and reconstructing any supplemental link records as Contact Account associations. Opportunities carry custom-named pipeline stages that require an explicit stage-name mapping table before migration. Notes become Dynamics Annotations. Custom fields on every object require a FIELD_NAME metadata lookup against Insightly's /CustomFields/{objectName} endpoint before writes; without this step the fields are silently omitted. Workflow automations, AppConnect integrations, and project management configurations do not migrate as code; we deliver a written inventory for the customer's admin to rebuild in Dynamics or Power Automate.
Organization → Account
Insightly Organizations map directly to Microsoft Microsoft Dynamics 365 Sales Account records.
How it maps
OrganizationId serves as the dedupe key during import. Account is created first, before any Contact import, so that the AccountId lookup is available at Contact insert time. Address fields (street, city, state, postal code, country) map directly to the Account address composite. Industry and annual revenue fields migrate as custom fields if they are non-standard Insightly fields.
Contact → Contact
Insightly Contacts map to Microsoft Dynamics 365 Sales Contact records.
How it maps
Each Contact receives the corresponding AccountId from the Organization mapping. Email, phone, title, and address fields map 1:1. Any duplicate email addresses detected in the Insightly dataset are held in a reconciliation queue for the customer to resolve before final import. Contact links originally managed via Insightly's Add/Update Link endpoints are resolved as AccountId on the Contact record, which is the Dynamics-native equivalent.
Lead → Lead
Insightly Leads map directly to Microsoft Dynamics 365 Sales Lead records.
How it maps
Lead status from Insightly maps to the configured Lead Status picklist in Dynamics, with any custom Insightly status values added to the Dynamics picklist before migration. Lead scores, if stored as Insightly custom fields, migrate to custom numeric fields on the Lead.
Opportunity → Opportunity
Insightly Opportunities map to Microsoft Dynamics 365 Sales Opportunity records.
How it maps
The OpportunityName maps to Dynamics subject or name field, and estimated value, close date, and probability migrate directly. Pipeline stage is a custom string in Insightly and requires an explicit mapping table entry per stage name to the Dynamics Sales Process stage values. We configure the Sales Process and stage entries in Dynamics before migration begins.
Pipeline Stage → Sales Process + Stage
Insightly pipeline stages are custom-named strings attached to each Opportunity.
How it maps
We extract all distinct stage names from the Insightly export, add them as Stage values in a pre-configured Dynamics Sales Process, assign probability percentages matching Insightly where available, and map each Opportunity's stage string to the new Dynamics stage value during the Opportunity import transform.
Note → Annotation
Insightly Notes map to Microsoft Dynamics 365 Sales Annotation records on the Microsoft Dataverse layer.
How it maps
Note body, author, and creation timestamp migrate. Each Note's link to its parent record (Contact, Organization, or Opportunity) is reconstructed as a Regarding (objectid) reference on the Annotation during import, preserving the full note context inside the Dynamics timeline.
- OrganizationAccount1:1
- ContactContact1:1
- LeadLead1:1
- OpportunityOpportunity1:1
- Pipeline StageSales Processtransformed
- NoteAnnotation1:1
+ 4 more in the mapping below
How Insightly CRM and Dynamics 365 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.
| Dimension | Insightly CRM | Dynamics 365 |
|---|---|---|
| Account-Contact relationship | Explicit link records via separate links API | Native AccountId lookup on Contact with automatic hierarchy |
| Pipeline stage model | Custom-named string stages attached to each Opportunity | Stage values in Sales Process with probability and category |
| Custom fields | FIELD_NAME lookup required before writes via /CustomFields/{objectName} | Schema-defined custom fields with API name and type at schema creation time |
| Record linking | Link records separate from primary objects | WhatId/WhoId on Activity; parent lookups on all primary objects |
| Per-user cost entry | Plus $29/user/mo; Professional $49/user/mo | Sales Professional $65/user/mo; Sales Enterprise $105/user/mo |
| Attachment handling | URL/blob reference; no binary migration | SharePoint and Dataverse document storage with ContentDocumentLink |
| Automation scope | Workflow Automations in configuration layer, gated at Professional | Power Automate and Dynamics workflows; no direct workflow migration |
What to watch for in a Insightly CRM to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Insightly link records must be reconstructed as Account lookups
Insightly does not embed Contact-Organization relationships in the Contact record itself.
How we handle it
Instead it uses explicit link records created via the /Links endpoint. Microsoft Dynamics 365 Sales uses a native AccountId field on the Contact record to establish the parent Account relationship. During migration we export link records separately, import Organizations (to Accounts) first, then import Contacts with AccountId populated from the Organization mapping. If the Insightly dataset contains Contacts with multiple Organization links, we flag this during scoping because Dynamics Contact supports only one primary AccountId per Contact, and the customer must decide which Organization takes priority.
Custom fields silently drop without FIELD_NAME metadata lookup
Insightly does not expose custom field IDs in record objects.
How we handle it
Writing to a Contact custom field without first retrieving the FIELD_NAME from /CustomFields/Contacts results in the write silently ignoring the field. We retrieve all custom field metadata per object at migration start, build a FIELD_NAME reference table, and use it consistently across all record writes. Customers who have exported Insightly data via the native XML export and then attempted to load it into another system commonly report missing custom fields because the XML export captures only standard fields.
Insightly pipeline stage names require explicit mapping table
Insightly Opportunity stages are free-form strings stored per Opportunity with no centralized enumerated schema.
How we handle it
Microsoft Dynamics 365 Sales Opportunity stages are defined in a Sales Process with specific Stage values. We extract all distinct stage name strings from the Insightly export, create corresponding Stage entries in the destination Sales Process before migration, and run a stage-name mapping transform during the Opportunity import. If the customer has renamed stages inconsistently across pipelines (e.g., 'Negotiation' in one pipeline and 'In Negotiation' in another), we consolidate to a single stage name per Dynamics pipeline and document the merge for the customer's review.
XML export omits custom fields entirely
Insightly's native export-to-ZIP function produces XML files that include only default (standard) fields.
How we handle it
Custom fields, custom objects, and link records are excluded. Customers who rely on the native export for migration discover after cutover that all custom field data is absent. We bypass the XML export entirely and pull all records directly from the Insightly REST API, including custom fields via the FIELD_NAME approach and link records via the /Links endpoints. We inform customers of this limitation before migration begins.
User provisioning requires Active Directory or Entra ID coordination
Microsoft Dynamics 365 Sales uses Azure Active Directory (now Microsoft Entra ID) for user identity.
How we handle it
Insightly Users do not have a direct mapping to Dynamics Users without an Entra ID match. We extract every distinct Owner referenced on Insightly records, match by email against the destination Dynamics org's User table, and hold any unmatched owners in a reconciliation queue. The customer's Dynamics admin must provision Entra ID-synced users for any Insightly owners who do not have a corresponding Dynamics User before the migration can complete record assignment.
How the migration runs
Discovery and record count audit
We audit the Insightly source instance across plan tier, record counts per object type (Organizations, Contacts, Leads, Opportunities, Tasks, Notes), custom field count per object, pipeline count and stage names, active tag usage, and any custom object definitions.
What this step covers
We also extract all link records from the /Links endpoints to establish the Contact-to-Organization relationship map. The output is a written migration scope including record counts, a preliminary stage-name mapping table, and a custom field inventory requiring FIELD_NAME metadata retrieval.
FIELD_NAME metadata retrieval and schema creation
We query /CustomFields/{objectName} for Contacts, Organizations, Opportunities, Leads, and any custom objects to build the FIELD_NAME reference table.
What this step covers
We use this to create matching custom fields in the Microsoft Dynamics 365 Sales schema via the Dataverse API before any data import. We also configure the Sales Process with stage entries mapped from the Insightly pipeline stage names, add tag-based multi-select picklist fields, and provision any custom entities for Insightly custom objects.
Organization and Account import
We import Organizations first as Dynamics Account records.
What this step covers
The OrganizationId becomes a reference key held in memory for the Contact import phase. Address fields, industry, and standard fields map directly. We run a reconciliation check to confirm the Account count matches the Insightly Organization count before proceeding.
Contact import with AccountId resolution
We import Insightly Contacts as Dynamics Contacts, resolving each Contact's AccountId from the Organization mapping.
What this step covers
Link records from the Insightly /Links export are applied as AccountId on each Contact. Any Contacts with multiple Organization links are flagged and escalated to the customer's admin for resolution before the import batch closes. Email deduplication is applied to the Contact set.
Lead, Opportunity, and Activity migration
Leads migrate directly to Dynamics Leads with status mapping.
What this step covers
Opportunities migrate with stage name transformation applied from the stage mapping table, AccountId resolved from the Organization mapping, and OwnerId resolved by email match against the Dynamics User table. Tasks and Notes migrate via the Dataverse API with Regarding references set to the parent Contact, Account, or Opportunity.
Cutover, delta sync, and automation handoff
We freeze Insightly writes during the cutover window, run a final delta migration for any records modified during migration, then deliver the written Workflow and automation inventory to the customer's admin.
What this step covers
We provide a one-week post-cutover window to address reconciliation issues. Workflows, AppConnect integrations, and Power Automate flows do not migrate as part of the data scope and are documented separately for the customer's admin or implementation partner to rebuild.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and pipeline complexity. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Insightly CRM to Dynamics 365 →Why teams move from Insightly CRM to Dynamics 365
- Teams with existing Microsoft 365 licensing and Active Directory infrastructure migrate to Microsoft Dynamics 365 Sales to consolidate the productivity stack. Native integration with Outlook, Teams, SharePoint, and Excel means email tracking, meeting capture, and document collaboration surface inside the CRM without third-party connectors, according to G2 and Gartner Peer Insights reviewers comparing Dynamics against Insightly for Microsoft-centric organizations.
- Insightly's workflow automation and AI Copilot are gated behind the Professional tier at $49/user/month. Teams with automation needs report rapid cost escalation as headcount grows, with the free plan's 2,500-record cap adding a separate ceiling. Microsoft Dynamics 365 Sales Enterprise at $105/user/month includes AI-assisted features and unlimited customization without an automation upsell, according to Microsoft documentation and CRM evaluator guides.
- Organizations already running Microsoft Dynamics 365 Business Central or Finance and Operations consolidate CRM into the same environment to enable Quote-to-Order flows between the ERP and CRM layers. Reddit r/CRM discussions on Business Central integration specifically recommend Microsoft Dynamics 365 Sales as the native CRM pairing over non-Microsoft alternatives.
- Insightly's custom field handling requires FIELD_NAME API lookups that add complexity to every write operation, and users report the UI documentation as incomplete and time-consuming. Microsoft Dynamics 365 Sales defines custom fields in the schema editor with explicit API names from the start, making them straightforward to reference in Dataverse API calls, Power Automate flows, and Power BI reports without separate metadata lookups.
- Reviewers comparing Insightly against enterprise-grade CRMs cite limited customization for complex sales processes and insufficient field-level tailoring as reasons to move. Microsoft Dynamics 365 Sales supports unlimited record types, custom entities, and Power Apps extensions from the Enterprise tier, enabling the deeper customization that growing sales organizations require as their processes diverge from standard CRM templates.
Questions, answered
Insightly CRM to Dynamics 365 migration questions
How long does an Insightly CRM to Microsoft Microsoft Dynamics 365 Sales migration take?
Most migrations land between two and four weeks for accounts under 10,000 total records with no custom objects and a single pipeline. Migrations with multiple Insightly pipelines, custom objects, large Contact sets with complex link relationships, or more than 50 custom fields per object move to five to ten weeks because of FIELD_NAME metadata retrieval overhead, stage mapping design, and Dataverse API batch sequencing.
Do Insightly Workflows and AppConnect integrations migrate to Microsoft Dynamics 365 Sales ?
No. Insightly Workflow Automations live in the configuration layer and do not have a direct equivalent in Microsoft Dynamics 365 Sales , which uses Power Automate and Dynamics-native workflows instead. AppConnect integrations similarly are Insightly-specific connector configurations. We do not migrate them as code. We deliver a written inventory of every active Workflow and AppConnect configuration with its trigger, conditions, and recommended Power Automate equivalent for the customer's admin to rebuild. This inventory is part of the standard migration deliverable.
How are Insightly Notes handled in Microsoft Dynamics 365 Sales ?
Insightly Notes migrate to Microsoft Dynamics 365 Sales Annotation records via the Dataverse API. The note body, author, and creation timestamp transfer directly. Each Note's link to its parent record (Contact, Account, or Opportunity) is reconstructed as a Regarding reference on the Annotation, so the note appears in the correct record's timeline in Dynamics. File attachments stored as URL references in Insightly are flagged in the migration report; Dynamics-native SharePoint or Dataverse document storage requires separate configuration by the customer's admin.
Do we lose historical tasks and activities during migration?
No. We migrate all Insightly Task records as Dynamics Task records with ActivityParty resolution and OwnerId mapped by email match. Notes migrate as Annotations with the correct Regarding reference to the parent record. Each activity's original creation timestamp is preserved on the Dynamics record so the historical timeline is intact when sales reps open a Contact or Opportunity in Microsoft Dynamics 365 Sales .
How do we handle Insightly pipeline stages that are named differently than Dynamics defaults?
We extract all distinct stage name strings from the Insightly export before migration begins. Each unique stage name is added as a Stage value in a Dynamics Sales Process that we configure in the destination org before any Opportunity records are imported. Probability percentages from Insightly (where available) are mapped to the corresponding Dynamics stage probability field. If the customer has used the same stage name for different pipeline contexts in Insightly, we consolidate and document the decision in the stage mapping table for the customer's approval before the Opportunity import phase starts.
Can we run Insightly and Microsoft Dynamics 365 Sales in parallel during migration?
We recommend against running both systems as active systems of record simultaneously because changes made in Insightly after the migration window closes will not reflect in Dynamics. We do offer a delta sync pass at cutover to capture any final changes made in Insightly during the migration window. If the customer requires a parallel-run period for user acceptance testing, we can run the initial migration into a Dynamics sandbox environment first, leaving the production Insightly instance active for the sales team until sandbox validation is complete.
What happens to Insightly custom objects during migration?
Insightly custom objects migrate to Dataverse custom entities in Microsoft Dynamics 365 Sales . We create the destination entity schema via the Dataverse API before any data import, including all custom fields and any lookup relationships to standard entities such as Contact, Account, or Opportunity. Custom object data is imported last in the migration sequence, after all parent standard entities are confirmed to be in place, to satisfy any required lookup relationships.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Yardi to Dynamics 365Mapping · history · rollbackJobber to Dynamics 365Mapping · history · rollbackClose to Dynamics 365Mapping · history · rollbackCivicrm to Dynamics 365Mapping · history · rollbackActiveCampaign to Dynamics 365Mapping · history · rollbackField Services Workflow and Logistics to Dynamics 365Mapping · history · rollback Insightly CRM to HubSpotMapping · history · rollbackInsightly CRM to Zoho CRMMapping · history · rollbackInsightly CRM to SalesforceMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Service protection limits (Microsoft Dataverse)
- Entity relationship behavior — Microsoft Learn
Get a quote
Moving from Insightly CRM to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote