Migrate from Intrix CRM to Salesforce Sales Cloud

Intrix Client records map directly to Salesforce Account. The Client name becomes Account Name; industry, address, and contact metadata map to typed Salesforce fields. Client ID is preserved as a custom field intrix_client_id__c for reconciliation. Account is the parent of every Contact import, so it migrates first to satisfy the AccountId lookup on Contact.

Intrix Contact records map to Salesforce Contact with AccountId resolved by matching the parent Client ID to the newly created Account record. FirstName, LastName, Email, Phone, and Title map directly. Any custom contact properties become custom Contact fields with __c suffix. Inactive Intrix users linked as Contact owners are flagged for explicit reassignment before Contact import.

Intrix Opportunities map to Salesforce Opportunity. Stage name maps to StageName via a customer-specific mapping table; probability migrates to StageProbability. Expected Close Date and Deal Value migrate to CloseDate and Amount. OwnerId resolves by email match against Salesforce Users. If the customer uses multiple pipelines in Intrix, each pipeline becomes a Salesforce Record Type with a corresponding Sales Process.

Intrix stage names and ordering are customer-specific. We extract the active stage configuration from the source account and configure matching Salesforce Stage values within a Sales Process. Probability percentages map from Intrix to StageProbability, rounded to Salesforce-allowed integers. If Intrix has custom stage colors or labels, these are noted for Salesforce Lightning UI rebuild by the admin.

Intrix Activity records tagged by type (call, email, meeting, task) map to Salesforce Task with TaskSubtype, Event, or EmailMessage respectively. Timestamp, owner, and description preserve. WhoId on the Salesforce activity resolves to the migrated Contact or Lead; WhatId resolves to the related Account or Opportunity. For large activity histories, we use the Salesforce Bulk API 2.0 with batch chunking and exponential backoff.

Intrix Projects have no direct Salesforce equivalent. We evaluate whether the customer uses Projects primarily for task tracking (map to grouped Salesforce Tasks with a Project custom field) or for deliverable management (create a Salesforce custom object Project__c with lookup to Account). The choice is made during scoping based on how the customer uses the data post-migration.

Intrix Tasks with predecessor dependencies require ordered import to prevent an unresolvable incomplete state. We extract the full dependency graph, sort by topological order, and import parent tasks before child tasks. In Salesforce, predecessor logic is implemented as custom Task fields (Predecessor_Task__c) or via a Flow that enforces dependency completion, since Salesforce Tasks do not natively enforce predecessor blocking.

WHR is only present on Intrix Advanced and Unlimited tiers. Each WHR record maps to a Salesforce Task with custom fields whr_hours__c, whr_date__c, and whr_employee__c. The HRM staff monitoring data maps to Salesforce custom fields on User or a custom Employee object. If the destination org does not have a compatible time-tracking setup, we create the target schema during migration so WHR lands without data loss.

Support Tickets are an add-on module active on Intrix Advanced and Unlimited tiers. Ticket records map to Salesforce Case, with status mapping to Case Status, priority to Priority, and email thread history to EmailMessage records linked to the Case. Email thread flattening (nested email chains into a flat timeline) is handled as a custom transform step since Intrix stores threaded email differently from Salesforce's flat activity model.

Intrix custom fields on any object map to Salesforce custom fields of the equivalent data type (text, number, date, picklist, checkbox, currency). We extract the full custom field schema per object during scoping, create the target Salesforce custom fields in the Sandbox before production migration, and note any unsupported field types (e.g., complex multi-select formats that require reformatting). Custom field API names in Salesforce follow the __c naming convention.

Intrix stores attachments per Client, Contact, or Project record. We download files individually from the Intrix UI, then re-upload to Salesforce as ContentDocument records linked via ContentDocumentLink to the target Account, Contact, or custom Project object. File-per-record structure can create bulk import overhead for records with multiple attachments; we batch uploads in groups of 25 to stay within Salesforce file processing limits.

Intrix users referenced as Opportunity owners, Project managers, or Activity owners map by email match to Salesforce User records. Any Intrix user without a matching Salesforce User is held in an owner reconciliation queue. The customer's Salesforce admin provisions missing Users (active or inactive per the original Intrix user's status) before record import resumes. Migration cannot proceed past Opportunity and Activity phases without resolved OwnerId references.