Migrate from Intrix CRM to monday CRM

Intrix Client records carry the 360-degree client view: company name, industry, contact details, and overview data. We split this into two destination records. Company-level fields (name, industry, address) create a Monday.com Company Item. Contact-level fields (name, email, phone, role) create a Person Item linked to that Company via a relation column. We use the Intrix Client ID as a reference in a custom column to preserve the relationship without relying on name-based matching alone.

Intrix Contact records attach to Clients as child records. We merge Contact-level fields (first name, last name, email, phone, role) into the Person Item created from the parent Client, using Client ID as the linking key to resolve the parent Company Item. If a Contact has no Client parent in Intrix, we create a standalone Person Item and flag it for the customer to link manually in Monday.com.

Intrix Opportunity records map to Monday.com Deal Items with stage, value, expected close date, and owner preserved as typed columns. Intrix deal stages (customer-configured names and probabilities) become Monday.com status column values. We sequence the Deal import after Person and Company import so that the contact relation column resolves at import time rather than requiring a post-import link pass.

Intrix Activities (calls, emails, meetings, tasks) log against Clients or Opportunities. We create dedicated activity Items on the relevant board with type, description, timestamp, and owner as columns. For calls and meetings, we add duration columns. For emails, we store subject and body as text columns, noting that threaded email view requires a separate email integration to restore context rather than flat notes.

Intrix Projects contain task hierarchies with predecessor dependencies. We create a Monday.com Board as the project container, preserving project name, description, start date, and deadline as board or group metadata. Monday.com's dependency column type supports predecessor linking at the Item level. We extract Intrix's dependency graph and rebuild it using Monday.com's dependency column, noting that circular dependency detection is handled by Monday.com and may flag Intrix dependencies that are logically invalid.

Intrix Task records carry project context, assignee, deadline, status, and predecessor dependencies. We import Tasks as Items on the parent Project board after the Project board exists. Dependencies use Monday.com's dependency column with Items sequenced so that predecessor Items are created before dependent Items to avoid broken dependency references. Tasks without a project context in Intrix map to Items in a catch-all Task board.

Available only on Intrix Advanced and Unlimited tiers. WHR data (date, employee reference, hours logged, project or task reference) maps to Items on a dedicated Time Tracking board with date, person, duration, and project columns. We confirm WHR module status during scoping and exclude WHR from the migration scope if the source account is on the Basic tier.

Available only on Intrix Advanced and Unlimited tiers (€2/user/month add-on). Ticket records (subject, status, assignee, email thread history) map to Items on a dedicated Support board with status, priority, assignee, and created date columns. Email thread history from Intrix tickets flattens into a text column per Item; the customer rebuilds email threading by connecting their email platform directly to Monday.com after migration.

Intrix custom fields per object map to Monday.com column types. We match Intrix field types to Monday.com column types: text to text, number to numbers, date to date, dropdown to status or dropdown, checkbox to checkbox, and currency to numbers with formatting. Multi-select dropdown values require explicit mapping to Monday.com status or dropdown column values during import.

Intrix stores file attachments per Client, Contact, or Project record. We download each attachment from the Intrix UI, associate it with the migrated Item in Monday.com via the file column type, and validate that the file links resolve correctly. Files are re-uploaded per Item, which requires the migrated user account to have write access to each board receiving files.