Migrate from Intrix CRM to Zoho CRM

Intrix Client records map directly to Zoho CRM Accounts. The Intrix Client name becomes Account Name, industry becomes Industry picklist, and the 360-degree overview data migrates as a rich text custom field or into Zoho's native Notes section. Client ID from Intrix is preserved in a custom field intrix_client_id__c for cross-system reference and delta-sync reconciliation. The dedupe key during import is Account Name with a fuzzy match on domain if the Website field is populated.

Intrix Contact records map to Zoho Contacts with the parent Account lookup resolved by matching the Intrix Client ID or Client name to the Zoho Account record inserted in the previous phase. Intrix contact roles on Opportunities map to Zoho Contact Roles on the linked Deal. Email, phone, address, and title fields migrate directly. Custom fields on Intrix Contacts map to Zoho custom fields of matching type (text, number, date, picklist).

Intrix Opportunities map to Zoho Deals with stage mapping defined during scoping. The Intrix pipeline stage names (customer-specific) map to Zoho Stage picklist values that we configure in the destination org before migration. Deal amount, expected close date, and owner assignment migrate directly. Intrix custom fields on Opportunities (such as deal type or product line) map to Zoho custom fields with type preservation.

Intrix uses a configurable pipeline stage model with customer-specific stage names and order. We extract the customer's active stage configuration (stage name, probability, order) during audit and configure the matching Zoho Stage picklist values and probabilities before Deal import. If the customer uses multiple Intrix pipelines, each maps to a separate Zoho pipeline with separate Stage picklist values scoped to that pipeline.

Intrix Activities (calls, emails, meetings, tasks) logged against Clients or Opportunities migrate to Zoho Tasks and Events. Activity type from Intrix determines the Zoho record type: calls and tasks become Task records, meetings become Event records, and emails become Task records with an email subtype. Timestamps, owner assignments, and descriptions migrate directly. The related Client or Opportunity lookup resolves by matching the Intrix Client ID or Opportunity ID to the Zoho Account or Deal inserted earlier.

Intrix Projects with task dependencies have no direct Zoho CRM equivalent. If the customer uses Zoho Projects (a separate product in the Zoho suite), we migrate Projects as Zoho Projects records and Tasks as Zoho Project Tasks with the dependency graph reconstructed using predecessor links. If the customer does not license Zoho Projects, we migrate Project metadata and task summaries into a Zoho CRM custom module, noting that dependency automation does not transfer without Zoho Projects. Project assignment to Contacts or Accounts links via Zoho custom module lookups.

Intrix Tasks with project dependencies inherit context from their parent Project. We extract the dependency graph (predecessor task ID, lag days, dependency type) and sequence imports so that parent tasks land before child tasks. In Zoho CRM without Projects, tasks migrate as standalone Tasks with a custom field project_context__c pointing to the parent Project record. In Zoho Projects, tasks migrate with their predecessor links intact using the Projects API. Incorrect sequencing results in tasks stuck in an unresolvable incomplete state.

WHR is available only on Intrix Advanced and Unlimited tiers. WHR records include date, hours worked, project or task association, and employee reference. Zoho CRM has no native time-tracking object. We migrate WHR to a Zoho CRM custom module (WHR_Record__c) with fields for Date, Hours, Project__c lookup, Task__c lookup, and Employee__c lookup, provided the destination org is on Professional tier or above. If the customer licenses Zoho Projects, WHR migrates as Zoho Project Log Hours entries. Time-tracking reporting must be rebuilt using Zoho Analytics or custom reports.

Intrix Support module (€2/user/month add-on on Advanced and Unlimited) includes ticket status, assignee, and email thread history. Zoho Desk is a separate product that provides full ticketing capabilities with SLA management and multi-channel support. If the customer licenses Zoho Desk, we migrate Intrix tickets to Zoho Desk Tickets with status mapping (Open to Open, In Progress to On Hold, Resolved to Solved) and email thread history as Ticket comments. If Zoho Desk is not licensed, tickets migrate to Zoho CRM Cases with custom fields for priority and resolution type.

Intrix allows custom fields on most objects. We extract the full custom field schema per object during audit, including field name, data type, required flag, and default value. Custom field types map to Zoho field types: text to Single Line, textarea to Multi Line, number to Number, date to Date, picklist to Picklist, checkbox to Checkbox. Multi-select picklists in Intrix map to Zoho Multi-Select picklists. Validation rules in Zoho must be reviewed post-migration to ensure they do not conflict with imported values that were valid in Intrix.

Intrix attachments stored per Client, Contact, or Project are downloaded individually and re-uploaded to the matching Zoho record. Zoho's Q1 2026 WorkDrive-based document storage migration provides cleaner attachment handling. For large attachment volumes (over 1,000 files), we use Zoho's bulk file upload API and link files to records via ContentDocumentLink. File-per-record structure in Intrix can create bulk import overhead for record sets above 5,000.

Intrix User records include access levels and role assignments. We map Intrix users to Zoho Users by email match. Inactive Intrix users require explicit handling: their records are assigned to a Zoho admin user as placeholder owner. Active Intrix users without a matching Zoho User in the destination org go to a reconciliation queue for the customer's admin to provision before record import resumes. Role mappings (Intrix role to Zoho role profile) are documented in the migration handoff.