Migrate from Cordis CRM to Zoho CRM

Cordis CRM contact profiles map to Zoho CRM Contacts. We survey the customer's Cordis instance during scoping to identify all standard and custom contact properties before mapping. Custom properties are created as Zoho custom fields before migration begins. Contact-company relationships are preserved by resolving the AccountId from the Company-to-Account migration phase before Contact import starts.

Cordis CRM Company records map to Zoho CRM Accounts. The Account-Contact relationship graph from Cordis is exported and remapped using company name matching against the newly created Zoho Accounts, or by using an external ID if one exists in Cordis. Account is created first so that the parent lookup is satisfied at the moment of Contact insert.

Cordis CRM Deal records map to Zoho CRM Deals with the deal name, value, stage, and owner preserved. The Cordis deal stage name maps to the corresponding Zoho pipeline stage by order position. We flag any Cordis Deals that reference an Account or Contact not yet migrated and hold those in a dependency queue until the parent records are in place.

Cordis CRM pipeline and stage configuration is not publicly enumerated, so we survey the customer's instance during scoping. Stage names and order are preserved during Zoho pipeline recreation. Each stage receives a probability percentage matching the customer's configured values, and the pipeline is associated with the Deals module before migration.

Cordis CRM automated and manual tasks map to Zoho CRM Tasks. Task status (open, completed, overdue), due dates, subject, and description migrate. Recurrence rules on Cordis tasks are flagged for manual reconfiguration in Zoho Blueprint because recurrence handling differs between platforms. Task owner maps by email match to Zoho User records validated in the owner reconciliation step.

Cordis document management stores files linked to CRM records. We export the latest version of each document (version history is not guaranteed complete in CSV export). Documents are re-associated as Zoho CRM attachments linked to the corresponding Contact, Account, or Deal record using the ID mapping table built during migration. If the customer is on a Zoho plan with WorkDrive, documents migrate there with a link stored in the CRM record.

Cordis CRM campaign tracking and engagement data map to Zoho CRM Campaign records if the customer is on a Zoho plan supporting Campaigns, or to Leads with a Campaign Source custom field if not. Campaign membership is preserved by linking the associated Contacts or Leads to the migrated campaign record.

Cordis CRM custom fields are identified during scoping by reviewing the customer's instance directly, since field names and data types are not publicly documented. We pre-create each custom field in Zoho CRM with the correct field type (text, picklist, date, number, checkbox) before importing any data. Custom field mapping is documented in the field mapping table delivered to the customer before migration begins.

File attachments linked to Cordis CRM records are exported individually with filename and record association preserved. We rebuild the record association in Zoho using the ID mapping table generated during migration. Attachments exceeding Zoho's size limits (typically 10 MB per file via standard import) are flagged for manual download from Cordis with customer coordination.

Cordis CRM's Google Workspace integration does not auto-export email history. If email history migration is in scope, we extract from Gmail directly with the customer's authorized access rather than relying on the CRM export. Emails land as Zoho Tasks (type Email) linked to the associated Contact, Account, or Deal, with the original timestamp preserved in Activity Date.

Cordis CRM notes migrate to Zoho CRM Notes linked to the parent record (Contact, Account, or Deal) via the record ID mapping table. Note body content migrates as plain text. Any embedded images in notes are exported as separate files and re-linked.