Migrate from Insightly Marketing to Twenty CRM

Insightly Contact records map 1:1 to Twenty CRM Contact. Standard fields including name, email, phone, address, title, and owner assignment migrate directly. Lifecycle stage from Insightly's Lead_Status or custom lifecycle field is preserved as a custom Contact property in Twenty. We resolve the Insightly Contact-to-Organization link by mapping the foreign key to the corresponding Company record created in Twenty before Contact import.

Insightly's separate Lead object merges into Twenty CRM Contact records because Twenty does not maintain a distinct Lead object by default. We extract Lead records, apply the original Lead_Status value as a custom property on the merged Contact, and flag any Lead-specific fields (lead source, lead score, custom lead fields) for mapping to equivalent Contact custom fields. This N:1 merge step happens during the transform phase before import.

Insightly Organization records (Insightly's term for companies and accounts) map directly to Twenty CRM Company records. Organization name maps to Company name, domain maps to Website, and industry, employee count, annual revenue, and address fields map to equivalent Company fields. Organization-to-Organization hierarchy relationships migrate as parent-company lookups where supported in Twenty's schema.

Insightly Opportunities map to Twenty CRM Opportunities. Pipeline names, stage names, probability percentages, expected close dates, and deal amounts migrate directly. Custom Opportunity fields map to custom Opportunity fields in Twenty. We flag any pipeline stage values that differ between Insightly and Twenty and normalize them during the import sequence so that Opportunity stage assignments are valid in the Twenty configuration.

Insightly pipeline configurations (stage names, stage order, probability values) require replication as Twenty Opportunity stage configurations. Each Insightly pipeline maps to a separate stage set in Twenty. Stage probabilities are rounded to valid percentages and mapped to Twenty's stage probability fields. This step requires coordination with the customer to confirm which Insightly pipelines map to which Twenty stage configurations.

Insightly Projects (with status, milestones, task lists, and assignees) are a native Insightly object that has no direct equivalent in Twenty CRM's standard schema. We map Project records as a custom object in Twenty or as linked association records attached to the relevant Contact and Company. Project-to-Contact and Project-to-Organization links are preserved as lookup relationships. The customer chooses the target schema during scoping based on how they track project-work in Twenty.

Insightly Task records (including due dates, assignees, status, and related-to reference) map to Twenty CRM Task. Task ownership migrates by resolving Insightly user IDs to Twenty User references. The related-to reference (Contact, Organization, Opportunity, or Project) migrates as a lookup field in Twenty, provided the target record has already been imported in the dependency sequence.

Insightly custom objects are defined per customer implementation, meaning field names, field types, and relationships are unique to each instance. We require a schema discovery phase before migration to map the actual custom object structure, identify any dependencies between custom objects and standard objects, and determine how relationships should be represented in Twenty CRM. We pre-create the equivalent custom object schema in Twenty before any data import.

Insightly custom fields organized into custom field groups map to custom fields in Twenty CRM. We extract field names, types, and values, but flag any validation rules in Insightly that may restrict what can be imported into Twenty. Multi-select picklist fields, date fields, and numeric fields are type-mapped to their Twenty equivalents. Custom field groups in Insightly do not have a direct Twenty equivalent and are flattened into the object-level field list.

Insightly tags on Contacts, Organizations, Opportunities, and Projects are extracted as tag name values. We re-apply tags as native Twenty CRM tags if the Twenty version supports them, or as a custom multi-select text field on the relevant object if native tagging is not available. The customer chooses the tag strategy during scoping.

Insightly user records map to owner fields on Contacts, Organizations, Opportunities, and Projects. We preserve user-to-record assignment by extracting the Insightly user ID and mapping it to a Twenty User by email match. Any Insightly user without a matching Twenty User is flagged for the customer's admin to provision before record import resumes. Inactive Insightly users can be mapped as inactive Twenty Users to preserve historical assignment.

Insightly marketing email templates are stored in a proprietary or HTML format that cannot be directly imported into Twenty CRM. We extract the HTML content from templates and deliver a content file with preserved template text, images, and styling. The customer's admin rebuilds templates in Twenty's template editor or a connected email tool. We advise budgeting for template reconstruction time as a separate task outside the migration scope.