Migrate from Intrix CRM to Microsoft Dynamics 365 Sales

Intrix Client records map directly to Microsoft Microsoft Dynamics 365 Sales Account. The Client record's 360-degree overview data, including industry classification, annual revenue, and custom fields, maps to Account standard fields and custom columns in Dataverse. We use the Client name as the dedupe key during import. Account must be created before any Contact import so that the parent AccountId lookup is satisfied at the moment of Contact insert. If the Intrix account has multiple addresses, we map the primary address to the Account Address fields and flag additional addresses for manual entry or custom address sub-grid configuration.

Intrix Contact records map to Microsoft Dynamics 365 Sales Contact with the parent Client mapped to AccountId via lookup resolution. We preserve the contact name, email, phone, job title, and any custom contact-level fields. If the Intrix account uses the Contact's primary Client assignment as a hierarchical link, we resolve that relationship using the AccountId field. Duplicate detection runs against the email address during import to avoid creating duplicate Contact records for existing accounts.

Intrix Opportunities map to Microsoft Dynamics 365 Sales Opportunity with stage, value, expected close date, and owner preserved. The Intrix pipeline stages are customer-specific and require a stage-name mapping table that we extract during scoping. We configure the corresponding Sales Process and stage values in Dynamics 365 before migration so that stage probabilities and picklist values are consistent with the source. Closed-Lost and Closed-Won dates map to CloseDate with the status inferred from the Intrix stage name.

Each distinct pipeline in Intrix becomes a Microsoft Dynamics 365 Sales Process whitelisted on the Opportunity record type. We extract the customer's active stage names and probabilities from the Intrix UI and configure matching stage values in Dynamics 365. Stage probability percentages migrate with rounding to the nearest integer allowed by Dynamics. If the customer uses multiple pipelines in Intrix, each pipeline maps to a separate Opportunity record type.

Intrix Activities logged against Clients or Opportunities migrate to Dynamics 365 Task, Event, and EmailMessage records. Calls map to Task with TaskSubtype set to Call and disposition preserved in custom fields. Meetings map to Event with StartDateTime, EndDateTime, and Location preserved. Email threads from the Intrix activity log require flattening into individual EmailMessage records linked to a parent Task. Activity timestamps are preserved as ActivityDate so that the timeline order is maintained in Dynamics 365.

Microsoft Dynamics 365 Sales does not have a native project management module. If the customer's Intrix Projects contain critical task dependency data, we create a custom Project entity in Dataverse before migration and map the project name, description, status, and owner. For customers with simple project tracking needs, we map Projects to Accounts with a project-name custom field and store tasks under the Account. The migration inventory notes the chosen strategy and any dependency logic that cannot be preserved without custom Power Apps development.

Intrix Project Tasks with predecessor dependencies require ordered import sequencing because Microsoft Dynamics 365 Sales has no native task-dependency model. We extract the dependency graph from Intrix, sort tasks so that predecessor tasks are imported before their dependent tasks, and store the original dependency reference in a custom field (intrix_dependency__c) for audit. The completion-blocking logic that Intrix enforces cannot be replicated in Microsoft Dynamics 365 Sales without custom Power Apps development, so we document this limitation in the migration handoff.

WHR data exists only on Intrix Advanced and Unlimited tiers. There is no standard Microsoft Dynamics 365 Sales object for time-tracking records, so we create a custom WHR entity in Dataverse before migration. The custom entity stores employee reference, date, hours worked, project reference, and any custom fields from the source WHR schema. If the destination does not require WHR data, we skip this object during migration after confirming scope during discovery.

Intrix Support Tickets (available on Advanced and Unlimited as an add-on) map to Microsoft Dynamics 365 Sales Case when the destination includes Service Cloud. Ticket status maps to Case Status, assignee maps to OwnerId, and email thread history migrates as EmailMessage records linked to the Case. We flatten threaded email content and store it in the Case Description or in a custom EmailThread__c field to preserve the full conversation history.

Intrix custom fields on any object migrate to Dataverse custom columns of equivalent type. We extract the full custom field schema per object during discovery and pre-create all columns in Dynamics 365 before any data import. Field types are mapped: text to Text, date to DateTime, number to Decimal or Whole Number, dropdown to Option Set, and checkbox to Two Option. Unsupported field types are flagged for the customer's admin to handle during post-migration configuration.

Intrix Owner records map to Microsoft Dynamics 365 Sales User by email match. We extract every distinct owner referenced on Client, Contact, Opportunity, Activity, Project, and WHR records and match against the destination org's User table. Owners without a matching Dynamics 365 User enter a reconciliation queue for the customer's admin to provision before record import resumes. Migration cannot proceed past this step because OwnerId references are required on standard objects.

Intrix file attachments stored per Client, Contact, or Project are downloaded from the Intrix UI and re-uploaded to the destination record. For Client and Contact attachments, we link files to the Account or Contact via SharePoint document locations configured in Dynamics 365 or via Notes attachments. File naming preserves the original Intrix filename and record association. We flag any file exceeding Dynamics 365 attachment size limits for manual handling.

Intrix integrations with MailChimp, Google Calendar, and AccountingBox store connection credentials and sync state that cannot be exported or migrated. We document every active integration during discovery so the customer can reconfigure connections manually in Dynamics 365. Email threads from integrated accounts that do not appear in the Intrix activity log must be exported directly from the email platform (Outlook or Gmail) rather than relying on Intrix as the source of record.