Migrate your Insightly CRM data

Leads are a top-level object in Insightly with their own lifecycle. We map them 1:1 for most destinations, converting Lead status to a custom Contact property when the target CRM does not have a separate Lead object.

Contacts are a standard object with standard fields (name, email, phone) plus optional custom fields. We preserve all standard fields and custom fields via the FIELD_NAME approach. Link relationships to Organizations must be re-established using the Add/Update Link endpoints after import.

Organizations store company-level data and serve as the parent record for Contacts. We import Organizations first, then Contacts, then re-link them via the link endpoints to preserve the Contact-to-Organization relationship in the destination.

Opportunities contain pipeline stage, probability, and monetary value fields. Pipeline stages are custom-named strings in Insightly and require explicit mapping to destination stage names. We flag stage mismatches during scoping and apply a customer-approved mapping table at import.

Insightly Projects can be created from closed Opportunities. Project task structure, custom fields, and status fields map but require field-level alignment since task schemas vary across PM tools.

Tasks in Insightly are linked to any primary object (Contact, Organization, Opportunity). Task status values are enumerated strings that require value mapping against the destination system's task status schema.

Notes are standalone objects that can be linked to any primary record. We preserve note body, author, and creation date. The link relationship to the parent record must be reconstructed in the destination using the target system's association method.

Insightly supports user-defined Custom Objects with their own fields and relationships. Custom Object schemas are migrated via field-level mapping; we validate field types (text, date, picklist, currency) against the destination schema and flag unsupported field types.

Custom fields are handled per-object via POST/PUT endpoints. The FIELD_NAME identifier must be looked up via the /CustomFields/{objectName} endpoint before writes. We retrieve all custom field metadata per object at migration start and reference FIELD_NAME in every record write to avoid silent failures.

Pipeline stages are custom-named strings attached to Opportunities. We treat them as controlled-vocabulary fields, not enumerated schemas. During migration, we apply a stage name mapping table so stage semantics are preserved in the destination pipeline.

Tags are flat string labels applied to Contacts, Organizations, Opportunities, and Projects. We export and import tag arrays as plain string lists. Tag semantics are preserved as-is unless the destination requires tag normalization.

File attachments are stored as URLs or blob references in Insightly's object model. We do not migrate attachment binary data directly. We can export attachment metadata (filename, URL, associated record) and provide a reference mapping so attachments can be re-linked in the destination system.