Migrate from Insightly CRM to Twenty CRM

Insightly Leads are top-level records with their own lifecycle separate from Contacts. We map them 1:1 to Twenty Persons flagged as leads based on the source record type. The original Insightly Lead status and source fields migrate to corresponding Twenty Person fields. If Twenty's Person schema uses a role or type property to distinguish leads from contacts, we apply that field during import to preserve the lifecycle distinction.

Insightly Contacts map to Twenty Persons with all standard fields (name, email, phone, address) and custom fields preserved. The Insightly FIELD_NAME for each custom field is retrieved via the /CustomFields/Contacts endpoint before writing. The challenge specific to this pair is that Insightly Contacts must be explicitly linked to Organizations via link records, not by embedding the Organization reference in the Contact record. We handle this by importing Organizations first, then Contacts, then reconstructing the link by setting the Contact's Organization relationship field in Twenty to the migrated Organization's ID.

Insightly Organizations (company-level records) map directly to Twenty Companies. All standard fields (name, domain, address, phone) and custom fields migrate. We import Organizations first in the dependency order so that Contact imports can reference valid Company IDs. Deduplication uses the Organization name and domain as the matching key.

Insightly's link records are the pair-specific complexity in this migration. Insightly does not store the Organization ID directly in the Contact object; instead it uses a separate link record with its own link_id. We export all link records for Contact-to-Organization relationships during discovery, then after both Organizations and Contacts are migrated, we update each Contact in Twenty by setting the relationship field to the migrated Organization's ID. We sequence this as Organizations → Contacts → Link resolution. Without this step, migrated Contacts have no associated Company and appear as orphaned records in Twenty.

Insightly Opportunities map to Twenty Opportunities with pipeline stage, probability, monetary value, and expected close date. Pipeline stage names in Insightly are custom strings, not enumerated values, so we apply an explicit stage name mapping table during migration to match Twenty's pipeline stage definitions. Probability values migrate as integers. Closed-Won and Closed-Lost reasons migrate as custom fields if Twenty supports them.

Insightly pipeline stages are custom-named strings associated with each Opportunity's pipeline. We extract all unique stage names from the source account during discovery, then create corresponding stage definitions in Twenty's pipeline configuration before importing any Opportunity records. Probability percentages from Insightly stage settings map to Twenty stage weights.

Insightly Tasks are linked to any primary object (Contact, Organization, Opportunity) via the link API. We export tasks with their linked object type and ID, then import tasks into Twenty and link them to the migrated record using the target record's new ID. Task status values (not started, in progress, completed, deferred) map to Twenty's task status enumeration.

Insightly Notes are standalone objects that can be linked to any primary record. We export note body, author, creation timestamp, and the link records specifying which object each note is attached to. Notes migrate as Twenty Notes linked to the migrated parent record. If Twenty does not support rich-text note bodies, we fall back to plain-text migration.

Insightly Projects have no direct Twenty CRM equivalent since Twenty does not include project management as a native module. We treat Projects as a configuration decision: the customer's admin chooses to map them to Twenty Tasks (for lightweight project tracking) or to a custom object matching Insightly's Project schema. We export the full Project structure including tasks, custom fields, and linked Opportunities, and deliver a written mapping recommendation for the admin to implement based on their post-migration workflow preference.

Insightly Custom Objects (available from Plus tier at $29/user) migrate to Twenty custom objects with equivalent field schemas. We pre-create the destination schema in Twenty, including all custom field definitions, before importing any custom object records. Field types (text, date, picklist, currency, checkbox) map to their closest Twenty equivalents. Lookup relationships between custom objects require parent-record import ordering.

Tags in Insightly are flat string labels applied to Contacts, Organizations, Opportunities, and Projects. They migrate as string arrays to Twenty's tag field. Tag semantics are preserved as-is. If Twenty uses a separate tagging system rather than a flat string list, we apply the customer's preferred target format during scoping.

File attachments in Insightly are stored as URL references or blob references. We do not migrate attachment binary data. We export attachment metadata (filename, URL, associated record type and ID) as a written inventory for the customer's admin to review and re-attach manually post-migration if the files are accessible via the original URL or document store.