Migrate from Insightly Marketing to Salesforce Sales Cloud

Insightly Contact records map directly to Salesforce Contact. Standard fields (FirstName, LastName, Email, Phone, Title) map 1:1. We map custom Contact fields and preserve any tags as a custom multi-select picklist field. Owner assignment resolves by email match against Salesforce User records in the destination org.

Insightly Organization records map to Salesforce Account with direct field mapping (OrganizationName to AccountName, Website, Industry, Phone, Address). Insightly's Organization-to-Organization parent relationship maps to Salesforce Account hierarchy (ParentId) if the destination org uses hierarchical accounts, or to a custom Account_Parent__c lookup field if flat cross-reference is preferred. We determine the hierarchy strategy during scoping based on the customer's sales model.

Insightly Lead records map directly to Salesforce Lead. Lead_Status maps to Salesforce Lead Status. Any custom Lead fields migrate as custom Lead fields. Insightly does not require a separate Lead-to-Contact conversion step like Salesforce, so we preserve the full Lead record in Salesforce rather than converting unless the customer requests it.

Insightly Opportunity records map to Salesforce Opportunity. Pipeline name maps to a Salesforce Record Type or Sales Process. Stage names and probability percentages migrate to StageName and StageProbability. Expected Close Date and Amount map directly. Custom Opportunity fields migrate as custom Opportunity fields.

Insightly's native Project object has no direct Salesforce standard equivalent. We create a Project__c custom object in Salesforce and map Project fields (Name, Status, StartDate, EndDate, MilestoneTitle, TaskListName) to custom fields on the new object. Project-to-Contact and Project-to-Organization links migrate as lookup relationship records.

Insightly Task records map to Salesforce Task with Status, Priority, ActivityDate, Subject, and Description preserved. Task ownership resolves by email match to Salesforce User. The related-to reference (Contact, Organization, Opportunity, or Project) maps to the corresponding WhatId or WhoId in Salesforce.

Insightly custom objects vary per customer implementation, so we require a schema discovery phase before migration to map the actual custom object structure, field types, and relationships. We pre-create the destination schema in Salesforce (with __c API names), including all custom fields, lookup relationships, and validation rules, before any data import. Field type translation is required because Insightly field types (Lookup Relationship, Calculated Field) do not map directly to Salesforce field types without logic.

Insightly custom fields organized into custom field groups migrate as Salesforce custom fields on the corresponding object. We map field names, field types, and values but flag any validation rules that restrict what can be imported. Field type differences (Insightly's Lookup Relationship vs Salesforce's Lookup, Insightly's Calculated Field vs Salesforce's Formula Field) require transformation logic during import. Plus tier is limited to 50 custom fields per object; Professional to 100; Enterprise to 200.

Insightly tags on Contacts, Organizations, Opportunities, and Projects migrate to Salesforce as either native Tags (using Topic and TopicAssignment) or as custom multi-select picklist fields on the respective object. The customer chooses the strategy during scoping. Tag names are preserved as-is.

Insightly user records referenced as owners on Contacts, Organizations, Opportunities, and Projects map to Salesforce User records via email match. We extract every distinct owner email and resolve against the destination org's User table. Owners without a matching User go to a reconciliation queue for admin provisioning before record import proceeds.

Insightly engagement history (emails, calls, meetings, notes attached to records) migrates to Salesforce as Task, Event, EmailMessage, and Note records. We use the Salesforce Bulk API 2.0 for large engagement volumes (over 100,000 records) with chunking and parent-record lookup resolution (WhoId, WhatId). Activity timestamps are preserved to maintain timeline ordering. This mapping requires the parent Contact, Lead, Organization, or Opportunity to exist in Salesforce before the engagement insert.

Insightly marketing email templates export in a proprietary or HTML format that varies by tier. We extract the HTML content and provide a content package (HTML, images, styles) for rebuilding in Salesforce. Salesforce Classic Email Templates or Lightning Email Templates require manual reconstruction using the extracted content. This is a manual step; we do not deliver a plug-and-play template import.