Migrate from Intrix CRM to Twenty CRM

Intrix Clients are the primary entity and map directly to Twenty Companies. We extract Client records with their name, industry, address, phone, email, and any 360° overview custom fields stored against the client record. The Client ID is preserved as a reference field to support Contact-to-Company lookups during the Contact import phase. Company domain from any stored URL maps to the Twenty Website field.

Intrix Contacts are stored as separate records linked to a Client via Client ID or name. We extract Contacts with first name, last name, email, phone, title, department, and any custom fields. During import into Twenty People, we resolve the parent Company by matching on the Client reference or Company name field so that the People record attaches to the correct Company in Twenty's relationship graph.

Intrix Opportunities map to Twenty Opportunities with a 1:1 field mapping: opportunity name, stage, value (amount), expected close date, owner assignment, and description migrate directly. Custom stage names in Intrix require a stage-value mapping table that we build during scoping, then configure in Twenty's pipeline definition before migration begins.

Intrix uses a configurable pipeline stage model with customer-specific stage names and order. We extract the customer's active stage configuration from Intrix during audit and recreate it in Twenty's pipeline settings. Probability values per stage migrate from Intrix to Twenty StageProbability fields. Stage order is enforced through Twenty's stage sequencing on the Opportunity object.

Intrix Activities (calls, emails, meetings, and tasks logged against Clients or Opportunities) migrate to Twenty Tasks and Notes. We extract the full activity history including timestamps, owners, descriptions, and the linked record reference. Activity type determines the target object: logged calls and tasks become Tasks; standalone notes become Notes. Owner resolution uses email matching against the Twenty workspace Members list.

Intrix Projects contain Tasks with dependencies and deadline automation. Twenty does not have a native Project object, so Projects require a destination design decision during scoping: either map to a Twenty Custom Object named Projects, or roll project milestones into Opportunities with custom fields for milestone tracking. The choice depends on how the customer uses Intrix Projects day-to-day.

Intrix Tasks with predecessor dependencies inherit from their parent Project. We extract the full dependency graph (which task depends on which) and sequence imports so that parent tasks are inserted into Twenty before child tasks. In Twenty, dependencies must be recreated manually via custom fields (e.g., depends_on__c) or through a project management integration since Twenty lacks a native dependency model for Tasks.

Working Hours Records are only available on Intrix Advanced and Unlimited tiers. WHR data includes hours logged, date, employee reference, and any notes. Twenty has no native time-tracking object, so WHR records map to custom fields on the People object (e.g., wthr_total_hours__c) or to a dedicated Custom Object named Working Hours. The customer's Intrix tier must be confirmed during scoping to determine whether WHR data exists to migrate.

The Intrix Support module is a €2/user/month add-on on Advanced and Unlimited tiers. Tickets include status, assignee, email thread history, and custom fields. Twenty has no native ticketing object, so tickets migrate to a pre-configured Custom Object (e.g., Ticket) with fields for ticket ID, subject, status, assignee, description, and email thread flattened into a long-text Notes field. Email thread flattening is handled with a custom parser that consolidates threaded emails into a single body.

Intrix custom fields on Clients, Contacts, Opportunities, Projects, and Activities migrate to Twenty custom properties on the equivalent object. We extract the full custom field schema per object during audit, including field type (text, number, date, dropdown, checkbox), required flag, and any picklist values. Custom fields must be pre-created in Twenty Settings → Data Model before the data import phase begins; the CSV import creates records but not fields.

Attachments stored per Client, Contact, or Project in Intrix are downloaded individually and re-uploaded to the corresponding Company, People, or Opportunity record in Twenty. File-per-record structure means that migrations with large attachment volumes require a bulk download step that can extend the timeline. We document the attachment count during audit and advise on storage planning for the Twenty hosting environment.

Intrix User records include access levels and role assignments. We map Intrix users to Twenty Workspace Members by email match. Owner assignments on Opportunities, Projects, and Tasks migrate by resolving the Intrix owner reference to the corresponding Twenty Member. Inactive Intrix users require explicit handling: their records are assigned to an active user or marked as unassigned pending admin review.