Migrate from Insightly CRM to Salesforce Sales Cloud

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). 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.

Insightly Contacts map to Salesforce Contact. 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.

Insightly Organizations map to Salesforce Account. 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.

Insightly Opportunities map to Salesforce Opportunity. 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.

Each Insightly pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. 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.

Insightly uses explicit link records to associate Contacts with Organizations. 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.

Insightly Projects can be created from closed Opportunities. Projects that originated from closed Opportunities migrate as Tasks under the related Salesforce Opportunity (WhatId = OpportunityId). Standalone Projects or those 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. This is scoped during discovery and priced as a separate line item if the customer chooses the custom object path.

Insightly Tasks map to Salesforce Task. TASK_SEQUENCE or TITLE becomes Subject. STATUS maps to Salesforce TaskStatus (Not Started, In Progress, Completed, Waiting on someone else, Deferred). PRIORITY maps to Priority (High, Normal, Low). Due date maps to ActivityDate. Owner maps via email-to-User lookup against the Salesforce User table. Any LINK_RECORD_ID associations are noted for recreation as Task WhatId or WhoId lookups.

Insightly Notes map to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. The NOTE_BODY becomes the Note body (Body field). CREATED_DATE becomes ActivityDate for timeline ordering. Author information is preserved in a custom field. Note-to-record link relationships (which Insightly stores as separate LINK_RECORD entries) are reconstructed as ContentDocumentLink entries in Salesforce.

Insightly Custom Objects migrate to Salesforce Custom Objects with the __c API name suffix appended to match Salesforce naming conventions. We pre-create the destination schema including all custom fields, lookup relationships to standard and other custom objects, and picklist controlled-vocabulary values before importing any data. Lookup references are resolved at migration time against the imported standard object records.

Custom fields require FIELD_NAME discovery via the /CustomFields/{objectName} endpoint before any writes that reference them. We build a FIELD_NAME-to-Salesforce-API-name reference table at the start of every migration and use it consistently across all record writes. Picklist values in Insightly custom fields are mapped to Salesforce controlled-vocabulary picklist values during schema design. Without the FIELD_NAME discovery step, writes that reference custom fields silently drop those field values.

Insightly Tags are flat string labels applied to Contacts, Organizations, Opportunities, and Projects. We import them as Salesforce multi-select picklist fields on the relevant object. Tag arrays are flattened to pipe-delimited strings compatible with Salesforce's multi-select format. The customer selects which objects carry tags during scoping.