Migrate from Insightly Marketing to Microsoft Dynamics 365 Sales

Insightly Contacts map directly to Dynamics 365 Sales Contact records. We preserve first name, last name, email, phone, address fields, and any custom contact fields. The Contact's associated Organization link is held during extraction and resolved to the target AccountId after the Account load completes. Insightly lifecycle stage maps to a custom Contact field for audit purposes when the source instance uses that property.

Insightly Organizations map to Dynamics 365 Sales Account records. Organization name becomes Account Name; domain becomes Website; Industry, Annual Revenue, and Number of Employees migrate as standard Account fields. We load Accounts first in the migration sequence because Contacts, Opportunities, and Projects all reference them via lookup. Organization-to-Organization relationships map to Account-to-Account junction records if the destination uses the Relationship Type feature.

Insightly Leads map to Dynamics 365 Sales Lead records. Lead_Status from Insightly maps to the Lead Status picklist in Dynamics, which requires configuration to match the source value set before migration begins. Any custom lead fields migrate as custom Lead fields in Dataverse. The Lead-to-Contact conversion in Dynamics creates a new Contact and links it to an Account, which must be reconciled against the customer's existing Account records to avoid duplication.

Insightly Opportunities map to Dynamics 365 Sales Opportunity records. Pipeline name maps to a Dynamics Sales Process or Record Type that we configure before migration. Stage names migrate as StageName values with probability percentages normalized to the nearest integer allowed by Dynamics. Expected Close Date, Amount, and Probability migrate directly. The Opportunity's linked Organization maps to AccountId during the Opportunity load phase.

Insightly Projects have no native Dynamics 365 Sales equivalent. If the customer uses Projects primarily to track deal-related work, we map them to Opportunities with project-specific custom fields (milestones, project status, deliverable summary). If Projects represent a distinct business entity (agency work orders, consulting engagements), we recommend a custom Dataverse entity created before migration, with a lookup to the relevant Account and Contact. Project-to-Contact and Project-to-Organization links migrate as related records or custom junction entities.

Insightly Tasks map to Dynamics 365 Sales Task records. Subject, due date, status, priority, and description migrate. Task ownership migrates by resolving the Insightly user ID to a Dynamics User ID via email match. The related-to reference (Contact, Organization, Opportunity, or Project) maps to the corresponding Dynamics entity ID that we resolve during the migration phase. Insightly task categories map to Task Category or a custom picklist.

Insightly custom objects require schema discovery before migration because field names, field types, and relationships are unique to each instance. We create equivalent custom entities in Dataverse via the Microsoft XrmToolBox or Power Apps solution manager, including all custom attributes with appropriate Dataverse types (string, integer, decimal, lookup, picklist). Custom object relationships to standard objects (Contacts, Organizations, Opportunities) become Dataverse lookup relationships on the custom entity.

Insightly custom field groups organize fields into named expandable sections. Dynamics 365 Sales does not have an equivalent grouping construct; instead, we recreate the logical grouping by placing custom fields in the appropriate section of the entity's Page Layout and adding a tab or section header that mirrors the original Insightly group name. The field data migrates as standard custom attributes on the entity.

Insightly tags on Contacts, Organizations, Opportunities, and Projects migrate to a custom multi-select picklist field on each entity when the destination Dynamics version supports multi-select picklists. For older Dynamics versions without multi-select picklist support, we migrate tags as a semicolon-delimited text field. The customer selects the strategy during scoping.

Insightly Users map to Dynamics 365 Sales User records by email address. Owner assignments on Contacts, Organizations, Opportunities, and Tasks migrate by resolving the Insightly user reference to the corresponding Dynamics User ID. Users without a matching Dynamics User are held in a reconciliation queue for the customer's admin to provision before record migration resumes.