Migrate from X2CRM to Zoho CRM

X2CRM Contacts map to Zoho CRM Leads if the contact represents an unqualified prospect, and to Zoho CRM Contacts if the contact is associated with an Account and represents a known customer or sales-ready record. We evaluate the X2CRM contact record for associated Account links, lifecycle stage properties, and tag flags during migration to determine the split. The original X2CRM contact ID is preserved in a custom field x2crm_contact_id__c on both the Zoho Lead and Contact for cross-system audit. Standard fields—name, email, phone, address, and social URLs—map directly; custom fields from the X2CRM module builder are inspected via API discovery and mapped to equivalent Zoho custom fields created before import.

X2CRM Accounts map directly to Zoho CRM Accounts. The X2CRM account name becomes the Account Name field; website, industry, phone, and address fields map by field name. X2CRM's lifetime value field migrates to a Zoho custom field if the customer's Zoho edition supports custom fields at the target tier. All X2CRM tag associations are extracted and re-applied post-import as Zoho Tags or as a custom multi-select picklist field depending on tag volume. Accounts are created before any Contact import to satisfy the Account-Contact lookup dependency in Zoho.

X2CRM Deals map to Zoho CRM Potentials (internally called Deals in Zoho UI). The X2CRM deal stage maps to the Zoho Potential Stage; pipeline assignment maps to a Zoho Sales Pipeline that we configure before migration. Deal value, probability, expected close date, and owner map directly. X2CRM deal activity history logs migrate as Zoho Activity records linked to the Potential. Closed-Lost and Closed-Won status from X2CRM become Zoho Stage values. If X2CRM deal records include custom fields tracking deal type, source, or renewal flag, these migrate to Zoho custom fields on the Potential module.

X2CRM Products map directly to Zoho CRM Products. The product name, SKU (mapped from X2CRM's product code field), unit price, and description migrate directly. Associated price book entries in X2CRM become Zoho Price Book entries. If the customer uses X2CRM's product-to-deal linking for line-item tracking, we migrate the association by creating Product Details records on the mapped Potential during the deal import phase.

X2CRM's Services module tracks recurring service contracts or subscriptions linked to Accounts. Zoho CRM has no native Services module at any tier. We create a custom Zoho module named Services (with API name Services_CF) during schema setup, replicating the X2CRM field schema: contract name, associated account link, status (active/expired/pending), start date, renewal date, and contract value. The custom module is created before data import using Zoho's Module Builder, and module-level permissions are configured to match the customer's role hierarchy from X2CRM.

X2CRM Marketing Campaigns map to Zoho CRM Campaigns. Campaign name, type (email, event, social, etc.), status (planned, active, completed, archived), and linked contact lists migrate directly. Campaign history records and associated contact memberships map to Zoho Campaign Members with status values (Sent, Opened, Clicked, Responded). Email campaign templates from X2CRM migrate as static HTML stored in a custom Zoho field or as documents in Zoho's file library; the customer rebuilds active email campaign workflows in Zoho Campaigns post-migration.

X2CRM Activities map to Zoho CRM Activities: call records become Tasks with Task Subtype set to Call; meeting records become Events with start and end times preserved; standalone tasks map to Zoho Tasks with Status, Priority, and Activity Date preserved. X2CRM Notes map to Zoho Notes linked via the Notes module to the parent record (Lead, Contact, Account, or Potential). Activity timestamps are preserved in the Zoho Activity Date field. Owner resolution follows the User mapping: X2CRM owner references are resolved by email match against Zoho Users before Activity import begins. Zoho's per-user Activity limits apply and are checked during scoping.

X2CRM Tags are standalone label records that can be applied across multiple object types. For migrations with fewer than 100 distinct tags per object, we create Zoho CRM Tags and re-apply them to migrated records post-import using Zoho's tagging API. For migrations with high tag volume or tags used as structured classification fields (industry tags, account tier tags), we recommend a Zoho custom multi-select picklist field instead, as Zoho Tags do not support advanced filtering across all modules in the same way X2CRM tags do. The customer chooses the strategy during scoping.

X2CRM custom fields added via the module builder vary by module and are not consistently named across deployments. We inspect the X2CRM field schema via API discovery (GET /api/contacts, GET /api/accounts) to extract all custom field definitions including field type, required flag, and picklist values. We then create equivalent Zoho CRM custom fields via the Setup > Modules and Fields interface before migration begins, matching field types (text, number, date, picklist, multi-select, checkbox, currency) to their Zoho equivalents. Any X2CRM calculated or formula fields are noted as non-migratable; their values are computed at migration time and stored as static fields in Zoho.

X2CRM User records (name, email, role, assignment permissions) export via the X2CRM REST API. We match X2CRM users to Zoho CRM Users by email address. If a matching Zoho User does not exist at migration time, the X2CRM user record is held in a User reconciliation queue and the customer's Zoho admin provisions the User account before record import resumes. X2CRM role configurations (Viewer, Editor, Admin) map to Zoho's role hierarchy; we document the mapping and the customer applies the role assignments post-migration. Zoho's Profile and Role permissions model differs structurally from X2CRM's role system, so role parity is documented rather than programmatically enforced.

X2CRM attachments are stored as file references or blobs linked to Contact, Account, Deal, and other records. We attempt to download attachments via the X2CRM API during export. For cloud-hosted X2CRM instances, attachments are accessible via the REST API file endpoint. For self-hosted X2CRM instances, the file store may be on local disk paths; we coordinate with the customer's IT team during discovery to expose the upload directory for extraction via SFTP or admin panel access. Attachments are re-uploaded to Zoho CRM via the Zoho REST API (max 20 MB per file). If attachment count exceeds Zoho's per-user storage limits on the target tier, we advise on Zoho One storage add-ons before migration.

X2Flow stores automation logic as trigger-action pairs with drag-and-drop UI configurations that are not accessible via the REST API in a portable format. We do not migrate X2Flow workflows as executable code. During discovery, we extract every X2Flow rule's trigger type (record create, record update, field change, scheduled), condition criteria (field values, user assignments), and action sequence (field update, email send, task creation, lead assignment). We produce a Workflow Reconstruction Document that maps each X2Flow rule to an equivalent Zoho Blueprint (for step-by-step process enforcement) or Zoho Workflow Rule (for trigger-action automation), specifying the trigger, conditions, and actions in Zoho's configuration interface. The customer's Zoho admin or a Zoho partner rebuilds the automations post-migration.