Migrate from Insightly CRM to Freshsales

Insightly Leads map directly to Freshsales Leads. The Insightly Lead object has its own lifecycle separate from Contacts. We import Leads first since they are top-level records with no parent dependency. Lead status values from Insightly map to Freshsales Lead Status with a custom field insightly_lead_status__c preserving the original value for audit. Email address serves as the dedupe key during import.

Insightly Organizations map to Freshsales Accounts. This is the first record type we import in any migration because Contacts have a required AccountId lookup. We export all Organization records first, create them in Freshsales via the Accounts API, and resolve the Freshsales Account ID before importing any Contact records that reference them.

Insightly Contacts map to Freshsales Contacts. We import Contacts after Accounts are created so that the AccountId lookup relationship is satisfied at insert time. Standard fields (name, email, phone, address) migrate directly. Custom fields are retrieved via the /CustomFields/Contacts endpoint at migration start, a FIELD_NAME reference table is built, and all Contact custom field writes reference the correct FIELD_NAME. Contact-Organization links (stored as separate link records in Insightly) are reconstructed after both objects are present in Freshsales by setting the Contact's AccountId to the migrated Organization's ID.

Insightly Opportunities map to Freshsales Deals. Pipeline stage names in Insightly are custom strings requiring explicit mapping to Freshsales Deal stages. We create a stage mapping table during scoping, deploy the stage values in Freshsales before migration, and apply the mapping during Deal import. Probability percentages migrate to Freshsales probability fields where supported. Closed-won and closed-lost reasons map to Freshsales deal status notes.

Insightly Tasks are standalone records linked to any primary object (Contact, Organization, Opportunity). We import Tasks after their parent records exist in Freshsales and resolve the WhatId (Account or Deal) and WhoId (Contact or Lead) references at migration time. Task status values (Not Started, In Progress, Completed, Deferred) map to Freshsales Task status picklist. Note that Freshsales' native Insightly migration tool only supports default task fields; we use the API path to preserve all standard and custom task fields.

Insightly Notes (called Comments in Insightly's UI) are standalone objects that can be linked to any primary record. We preserve note body, author, and creation timestamp. The link relationship to the parent record (Contact, Organization, Opportunity) is reconstructed in Freshsales by resolving the WhatId and WhoId references after parent records are present. Note author is stored as a custom field if Freshsales does not have a native author field.

Insightly Projects do not have a direct Freshsales equivalent. We handle Project migration as a configuration decision made during scoping: either Projects map to Freshsales Tasks with project-level metadata stored in custom fields, or a Freshsales Custom Object named Project is created to hold project records with their associated tasks. The customer chooses the strategy based on how they use Projects in Insightly.

Insightly Tags are flat string labels applied to Contacts, Organizations, Opportunities, and Projects. We export tag arrays as plain string lists and import them to Freshsales' tag field on the corresponding object. Tag semantics are preserved as-is. If the customer uses tags for segmentation, we note that Freshsales tags serve the same flat-label purpose.