Skip to content
Get a quote

Insightly CRM to Salesforce migration

We migrate Organizations, Contacts, Opportunities, Notes, and Custom Objects from Insightly CRM into Salesforce with the explicit link-relationship model resolved before Contacts import, every custom field discovered via FIELD_NAME lookup before any write, and pipeline stage mapping configured as Salesforce Sales Processes before cutover.

Short answer

FlitStack AI migrates leads, contacts, accounts, opportunities and sales process + opportunity stages from Insightly CRM to Salesforce, 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: 3-6 weeks.

By

Source Insightly CRM
DestinationSalesforce
LeadContactAccountOpportunitySales Process + Opportunity Stage
Mapped field by field · sample run · one-click rollback

What moves from Insightly CRM to Salesforce?

Moving from Insightly CRM to Salesforce is a schema translation project as much as a data move.

Read the full summary

Insightly ties Contacts to Organizations through explicit link records, not embedded relationships; we reconstruct those as Account-Contact lookups by sequencing Organizations first and resolving AccountId during Contact insert. Insightly's Opportunities map to Salesforce Opportunities with pipeline stages migrated as Record Types and Sales Processes. Custom fields require FIELD_NAME discovery via the /CustomFields/{objectName} endpoint before any write, or they are silently dropped. We do not migrate Workflow Automations, Projects (except as Tasks against Opportunities), or attachment binaries; we deliver written inventories of these for the customer's admin to rebuild in Salesforce Flow, a custom Project object, or a file management system respectively.

1:1

Lead → Lead

Insightly Leads map directly to Salesforce Lead with all standard fields preserved (FIRST_NAME, LAST_NAME, EMAIL_ADDRESS, PHONE_NUMBER, ADDRESS_STREET, CITY, STATE, POSTAL_CODE, COUNTRY).

How it maps

We use the FIELD_NAME lookup via /CustomFields/Leads to discover any custom fields on the Lead object before writing. Lead status values from Insightly's STATUS field map to the customer's chosen Salesforce Lead Status picklist values, which we configure during Sales Process setup.

1:1

Contact → Contact

Insightly Contacts map to Salesforce Contact.

How it maps

Standard fields (FIRST_NAME, LAST_NAME, EMAIL_ADDRESS, PHONE_NUMBER, ADDRESS_* fields) migrate directly. We handle the Account-Contact relationship by importing Organizations first as Accounts, then resolving AccountId during Contact insert using the pre-exported link records. Any custom fields use the FIELD_NAME reference table built during discovery. Insightly's CONTACT_FIELD_RULE_LINK records are not a Salesforce object; the relationship is embedded as Contact.AccountId at write time.

1:1

Organization → Account

Insightly Organizations map to Salesforce Account.

How it maps

ORGANIZATION_NAME becomes Account Name. ADDRESS_* fields map to BillingAddress fields (Street, City, State, PostalCode, Country). We preserve the Insightly ORGANIZATION_ID in a custom field insightly_org_id__c for cross-system reference. WEBTEAM becomes Account Website. Organizations are imported before Contacts to satisfy the AccountId foreign key.

1:1

Opportunity → Opportunity

Insightly Opportunities map to Salesforce Opportunity.

How it maps

OPPORTUNITY_NAME becomes Opportunity Name. PIPELINE_STAGE_NAME maps to StageName using the stage mapping table built during discovery. PROBABILITY migrates to Opportunity.Probability. CUSTOM_AMOUNT becomes Amount. We configure the Salesforce Record Type and Sales Process before migration so that StageName values are valid against the whitelisted stages for the matching process.

configuration

Pipeline Stage → Sales Process + Opportunity Stage

Each Insightly pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values.

How it maps

Stage probability percentages migrate from Insightly's probability values to Salesforce StageProbability, rounded to the nearest integer allowed by the platform. The customer approves the stage name mapping table during discovery before migration begins.

lookup

Link Record (Contact-to-Organization) → Contact.AccountId

Insightly uses explicit link records to associate Contacts with Organizations.

How it maps

These are not embedded in the primary record objects. We export all link records separately, import Accounts first, then Contacts with AccountId resolved from the Organization mapping. This eliminates orphaned Contact records with no Account. We validate link completeness by querying Salesforce for Contacts where AccountId is null and cross-referencing against the original link set.

What moves12 objects
Insightly CRMSalesforce
  • LeadLead1:1
  • ContactContact1:1
  • OrganizationAccount1:1
  • OpportunityOpportunity1:1
  • Pipeline StageSales Processtransformed
  • Link RecordContact.AccountIdtransformed

+ 6 more in the mapping below

How Insightly CRM and Salesforce 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.

DimensionInsightly CRMSalesforce
Relationship modelExplicit link records connect Contacts to Organizations via Add/Update Link endpointsEmbedded Account-Contact lookup relationship; Contact.AccountId is set during insert
Lead and Contact separationContacts serve as the primary person record; Leads are a separate top-level objectSeparate Lead and Contact objects with explicit Convert action separating qualification lifecycle
Pipeline and stagesUp to 15 pipelines with custom-named stage strings attached to OpportunitiesUnlimited Record Types and Sales Processes from Professional tier; stages are a controlled vocabulary per process
Custom field writesFIELD_NAME identifier must be looked up per object before API writesStandard API field names; custom fields use __c suffix with direct API access
Custom objectsAvailable from Professional tier ($49/user/mo)Available from Professional tier ($80/user/mo) with no additional setup fee
Workflow automationGated behind Professional tier ($49/user/mo)Salesforce Flow (record-triggered, scheduled, screen) from Professional tier at no additional cost
App ecosystemAppConnect with 500+ no-code integrationsAppExchange with over 9,000 listings including ERP, CPQ, and revenue intelligence depth
Pricing modelFree plan for 2 users, 2,500 records total; Plus $29/user/mo, Professional $49/user/moSales Cloud from $25/user/mo; Professional $80/user/mo, Enterprise $165/user/mo; per-user licensing

What to watch for in a Insightly CRM to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

FIELD_NAME discovery required before custom field writes

Insightly does not expose custom field IDs in record objects.

How we handle it

Updating a Contact's custom field requires looking up the FIELD_NAME via /CustomFields/Contacts first. If FIELD_NAME is not known, writes silently ignore the custom field and the data is dropped. We retrieve all custom field metadata per object type at the start of every migration, build a FIELD_NAME reference table, and use it across all writes. We flag this as a high-severity risk for customers who have many custom fields per object, particularly on Plus and Professional plans where custom field limits are 50-100 per object.

high

Salesforce validation rules and required fields block import

Salesforce orgs commonly enforce validation rules on Opportunity (StageName required, Amount required on certain stages), Lead (Email format, required fields), and Contact (AccountId required if the page layout mandates it).

How we handle it

These rules can reject 10-30 percent of records on first import if the migration user does not have the right bypass permissions. We coordinate with the customer's Salesforce admin to grant the migration user Modify All Data, relax validation rules during load with a migration-context check, and re-enable them post-migration. We also pre-validate that Opportunity.Amount is populated before writes since null Amount can block Opportunity insert in orgs with required-field enforcement.

medium

Insightly's explicit link records require dedicated reconciliation

Insightly uses separate link records to associate Contacts with Organizations, or to attach Notes to Opportunities.

How we handle it

These links are not embedded in the primary record. We export link records separately, import parent and child records first, then reconstruct relationships in Salesforce as embedded lookups (Contact.AccountId) or ContentDocumentLink entries. Without this sequencing, Contacts end up orphaned with no Account, and Notes end up unlinked. We validate link completeness post-import by querying Salesforce for Contacts where AccountId is null and cross-referencing against the original link set.

medium

XML export omits custom fields; API export required

Insightly's native export-to-ZIP function produces XML files that include only default (standard) fields.

How we handle it

Custom fields are not included in these exports. Customers who attempt to migrate using the XML export path will lose all custom field data in Salesforce. We bypass the XML export entirely and pull all records including custom fields directly from the Insightly REST API. We inform customers of this limitation during scoping and use the API path exclusively for outbound migrations from Insightly.

medium

Workflow Automations, Projects, and attachments do not migrate

Insightly Workflow Automations live in the configuration layer and are not accessible via API.

How we handle it

They do not migrate to Salesforce Flow because the two automation models are structurally incompatible. We deliver a written inventory of every active Insightly Workflow with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent. Insightly Projects without an Opportunity parent require a custom Project__c object that is scoped and priced separately. File attachments are stored as blob URLs in Insightly; we export attachment metadata (filename, URL, associated record) but do not migrate binary data. The customer rebuilds workflows in Salesforce Flow and manages attachment files in Salesforce Files or a linked DMS.

How the migration runs

  1. Discovery and scoping

    We audit the Insightly account across plan tier, total record counts per object, active custom fields per object (using the FIELD_NAME discovery endpoint), custom object schemas and their inter-object lookups, pipeline and stage configuration, active workflow count and complexity, project count and Opportunity attachment rate, and owner email list.

    What this step covers

    We pair this with a Salesforce edition decision: Professional ($80/user) covers most migrations without custom objects; Enterprise ($165/user) is required if the customer needs Salesforce Flow at scale, advanced reporting types, or full profile-based sharing rules. The discovery output is a written migration scope with a record-count estimate and Salesforce edition recommendation.

  2. Schema design and FIELD_NAME reference build

    We design the Salesforce destination schema: we provision any required custom objects with __c API names, create custom fields typed to match Insightly field types (text, date, picklist, currency, checkbox, number), and configure Record Types and Sales Processes to match the Insightly pipeline-stage structure.

    What this step covers

    We simultaneously build the FIELD_NAME-to-Salesforce-API-name reference table by querying /CustomFields/{objectName} for every object that has custom fields. This reference table is the critical artifact that prevents silent custom field data loss during writes.

  3. Sandbox migration and reconciliation

    We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-equivalent data volume.

    What this step covers

    The customer's Salesforce admin or RevOps lead reconciles record counts (Organizations in, Leads in, Contacts in, Opportunities in, Tasks in, Notes in, Custom Object records in), spot-checks 25-50 random records against the Insightly source for field-level accuracy, and verifies that Contact.AccountId is populated for all Contacts (no orphaned records). Link completeness is validated by comparing the pre-exported Insightly link count against the resolved Salesforce relationship count. Sign-off on the sandbox run authorizes production migration.

  4. Owner reconciliation and User provisioning

    We extract every distinct Insightly owner email referenced on Contacts, Organizations, Opportunities, Tasks, and Notes and match by email against the Salesforce destination org's User table.

    What this step covers

    Any Insightly owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision. OwnerId references are required on Opportunity and Task inserts, so this step gates the production migration. We recommend provisioning inactive Users with the correct email for departed team members so that historical assignment is preserved.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Organizations), Leads, Contacts (with AccountId resolved from the link reconciliation step), Opportunities (with RecordTypeId, StageName, and probability set from the pipeline configuration), Tasks (with WhatId and OwnerId resolved), Notes (with ContentDocumentLink recreated for each linked record), Custom Objects (with all lookup references resolved at migration time).

    What this step covers

    The explicit link reconciliation step is embedded in the Contact import phase. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, delta sync, and workflow rebuild handoff

    We freeze Insightly writes during cutover, run a final delta migration of records modified during the migration window, then enable Salesforce as the system of record.

    What this step covers

    We validate relationship completeness one final time and deliver the written Workflow Inventory document listing every Insightly Workflow with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent. We deliver a separate Project and Attachment inventory noting what could not migrate and the recommended replacement path. We support a one-week hypercare window for reconciliation issues. We do not rebuild Insightly Workflows as Salesforce Flow inside the migration scope; that is a separate engagement.

Insightly CRM Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-6 weeksTypical, smaller accounts
8-14 weeksLarge or heavily customised accounts

A quote scales with record volume, custom object complexity, and link-relationship count. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Insightly CRM to Salesforce →

Why teams move from Insightly CRM to Salesforce

  • Teams requiring enterprise-grade reporting and territory management move from Insightly to Salesforce. Insightly's reporting is suited to standard pipeline and activity dashboards, but Salesforce's reporting engine supports multi-dimensional pipeline analysis across territories, product lines, custom fiscal periods, and non-standard attribution models that growing RevOps teams require. Gartner Peer Insights data shows Salesforce's feature breadth exceeds Insightly's for companies scaling past the SMB tier.
  • Salesforce's AppExchange offers over 9,000 listings versus Insightly's AppConnect at 500+, providing access to first-party or AppExchange-certified integrations for ERP, CPQ, contract lifecycle management, revenue intelligence, and data warehouse connectors that Insightly lacks. Companies requiring native NetSuite, SAP, Oracle, Conga, or DocuSign CLM integrations move to Salesforce specifically for that ecosystem depth.
  • Salesforce Flow provides a more capable automation engine from Professional tier ($80/user) compared to Insightly's Workflow Automations which require the same $49/user Professional tier but offer fewer action types, no screen flows, and no scheduled-trigger capabilities. Companies with complex routing, approval chains, and multi-object automation find Salesforce Flow's trigger model more flexible without upgrading to a higher-priced tier.
  • Insightly stores attachments as URL references or blob IDs only. Salesforce's ContentDocument and ContentVersion model provides native file versioning, sharing rules, and Lightning Locker compliance that Insightly's attachment handling does not. Companies requiring document management, e-signature tracking, or compliance-grade file audit trails find Salesforce's attachment model more suitable at scale.
  • Insightly's Plus plan at $29/user excludes Workflow Automations, leaving teams with automation needs to upgrade to Professional at $49/user. Salesforce Professional at $80/user includes Flow without gating automation behind a higher tier, and the unlimited Record Types and Sales Processes are available at the same tier level rather than requiring an Enterprise upgrade for pipeline complexity.

Questions, answered

Insightly CRM to Salesforce migration questions

Do Insightly Workflow Automations migrate to Salesforce Flow?

No. Insightly Workflow Automations live in the configuration layer and are not accessible via the API. They do not migrate to Salesforce Flow because the two automation models use different trigger types, action libraries, and delay mechanisms. We deliver a written inventory of every active Insightly Workflow with its trigger conditions, actions, and a recommended Salesforce Flow equivalent for the customer's admin to rebuild. Projects (Insightly's built-in project management) and attachment binaries also do not migrate; we provide a separate written inventory of these for the customer's admin to address in Salesforce through custom objects or Files management.

How long does an Insightly CRM to Salesforce migration take?

Most migrations land between three and six weeks for accounts under 10,000 Contacts and 2,000 Opportunities with no custom objects. Migrations with custom objects, complex Contact-to-Organization link graphs, large note histories, or multi-pipeline Opportunity structures move to eight to fourteen weeks because of the FIELD_NAME discovery work, explicit link reconciliation, Salesforce Sales Process configuration, and sandbox validation phases. Timeline is also gated by Salesforce admin responsiveness on User provisioning and validation rule relaxation.

Do we preserve historical Activity data (tasks, notes, project tasks)?

Yes. We migrate Task history from Insightly as Salesforce Task records with Subject, Status, Priority, ActivityDate, and OwnerId preserved. Notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Project tasks that are linked to Opportunities migrate as Tasks under the related Opportunity. Project tasks that are not linked to Opportunities require a custom object path that is scoped separately. All activity timestamp ordering is preserved by setting ActivityDate to the original Insightly creation date.

How does FlitStack AI handle Insightly's custom field FIELD_NAME requirement?

Insightly does not expose custom field IDs in record objects. Writing to a custom field requires the FIELD_NAME identifier from the /CustomFields/{objectName} endpoint. Without this step, writes silently ignore the custom field and data is dropped. We query all /CustomFields endpoints for Contacts, Organizations, Opportunities, Leads, Tasks, and any Custom Objects at the start of every migration, build a FIELD_NAME reference table, and use it across all API writes. This is a required step in our process for any Insightly migration, not an optional enhancement.

Can we migrate Insightly's Projects to Salesforce?

Insightly Projects that originated from closed Opportunities can migrate as Tasks under the related Salesforce Opportunity (WhatId = OpportunityId). Standalone Projects or Projects with complex task hierarchies require a custom Project__c object that we pre-create in Salesforce during schema design. Project custom fields migrate via the FIELD_NAME approach. Projects are scoped during discovery and priced as a separate line item if the customer requires the custom object path rather than the task-under-Opportunity path.

Do Insightly attachments migrate to Salesforce Files?

Insightly stores attachments as blob references or URLs. We export attachment metadata (filename, URL reference, associated record type, associated record ID) as a structured report. The binary file data itself is not migratable through the Insightly API. The customer can use the attachment metadata report to re-attach files from their source system or a file management tool into Salesforce Files after migration. We do not include binary file migration in standard scope.

What happens to our Insightly data after the migration?

We do not delete or modify Insightly data. The customer's Insightly account remains intact throughout the migration window. After cutover, the customer can choose to downgrade their Insightly plan, maintain read-only access for historical reference, or cancel the subscription directly through Insightly's billing portal. We do not manage Insightly account changes post-migration.

Get a quote

Moving from Insightly CRM to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote