Migrate from Insider to Twenty CRM

Insider User records map to Twenty Person records. Standard profile attributes (email, firstName, lastName, phone, city, country) transfer directly via the Insider Unification API upsert endpoint. Custom user attributes export as flat key-value columns and map to custom fields on the Twenty Person object. We pre-create the custom field schema in Twenty via the /metadata API before importing. Any Insider user with no email is flagged as a partial record and held for admin review because Twenty Person requires an email as the primary identifier.

Insider Company records map to Twenty Company records. The company name, domain, industry, size, location, and custom company attributes transfer directly. Companies with no domain are created with a placeholder domain and flagged for manual enrichment post-migration. We resolve Person-to-Company relationships using Insider's companyId field on the user record to populate the Twenty Person.work Company link.

Insider behavioral events (page views, purchases, funnel steps, custom events) have no native equivalent in Twenty CRM's activity model. Twenty supports Tasks, Events (meetings), and Notes attached to Person or Company records, but not a generic event stream. We export the full event log via Insider's Raw Export API and make one of three disposition decisions per customer: (1) archive the event log as a JSON or CSV file in a designated storage location, (2) create a Note record per user summarizing key lifecycle events, or (3) create a custom OpportunityEvent custom object in Twenty if the customer requires event history on the CRM side. The customer chooses the disposition during scoping.

Insider segments are defined by attribute rules and event conditions in the CDP. The rule logic itself does not migrate. We export the member list (user ID + segment name + membership timestamp) and recreate segment membership in Twenty as Person Label tags or as a static list stored as a custom field. The customer chooses label strategy during scoping. Segment names with spaces are converted to Twenty-compatible label slugs.

Insider Journeys are multi-step event-driven workflows with entry triggers, conditional gates, and channel actions. There is no API endpoint to export Journey definitions. We run a Journey audit during discovery and document every active Journey with its trigger logic, conditional branches, channel steps, and exit conditions in a written handoff document. The customer's admin rebuilds journeys in their chosen automation tooling post-migration. We do not migrate Journeys as code.

Insider Product catalog data (sku, name, price, category, images, custom attributes) maps to Twenty Opportunity products if the customer uses Twenty's Opportunity feature for deal management. Products without associated deals are stored as a custom Product catalog object that we create in Twenty before import. Price list management in Twenty is handled via custom fields rather than a native price book object.

Insider Transaction records (order_id, total, items, currency, timestamps) map to Twenty Opportunity records when the customer uses Opportunities to track deals and revenue. Each transaction becomes an Opportunity with the transaction total as the amount, the order_id in the Opportunity name or a custom field, and line items as custom fields or a related custom object. Historical closed-won transactions become closed Opportunities with a historical flag.

Insider User tags export as an array per user. We preserve the full tag array and recreate each unique tag as a Twenty Label on the Person record. Tags with spaces or special characters are slugified to Twenty's label format. The customer chooses whether tags apply to Person, Company, or both during scoping.

Insider allows arbitrary key-value custom properties beyond the standard profile schema. All custom attributes export as flat key-value columns from the Unification API. We create matching custom fields in Twenty for each unique custom attribute key, with field type inferred from the value format (string, number, date, boolean). Multi-value arrays are stored as text or multi-select depending on Twenty's field type support at migration time.

Insider Lists are static user collections beyond dynamic segment membership. We export list membership (user ID + list ID) and recreate each list as a Person Label or a boolean custom field (e.g., VIP_List = true). The list name becomes the label or field name, and the customer chooses the strategy during scoping.

Insider Owners (assigned users on records) map to Twenty WorkspaceMember records. We resolve owners by email match. Any Insider Owner without a matching Twenty WorkspaceMember is held in a reconciliation queue for the customer's admin to provision the user before record import resumes. Owner assignment on Person and Company records transfers after WorkspaceMember resolution is complete.