Migrate from CompanyHub CRM to Zoho CRM

CompanyHub Contacts map directly to Zoho CRM Contacts. The email address serves as the primary dedupe key. We preserve all standard fields (First Name, Last Name, Phone, Mobile, Title) and custom fields (CompanyHub supports unlimited custom fields per contact). The API exposes custom field definitions alongside values, so we export both and create matching Zoho custom fields before import. The primary CompanyHub Company association maps to the Zoho Contact's Account Name lookup.

CompanyHub Companies map to Zoho CRM Accounts. The API returns company records with associated industry, address, website, and revenue fields. We use the CompanyHub Company ID as a reference for Contact lookups, creating Zoho Accounts before importing Contacts so that the Account Name lookup is satisfied at Contact insert time. Company-level custom fields export and map to Zoho Account custom fields.

CompanyHub Deals map to Zoho CRM Potentials. The dealstage property maps to Zoho Stage picklist values, which we configure before migration. Amount, Close Date, Probability (if set), and Deal Owner migrate to Zoho Potential Amount, Close Date, Stage, and Owner Name respectively. The associated CompanyHub Company maps to the Zoho Potential's Account Name lookup.

CompanyHub allows fully customized stage names and order. We capture the complete stage list during discovery and configure matching Zoho Stage values in the Potential module. Probability percentages per stage migrate from CompanyHub to Zoho Stage Probability fields. If the customer has multiple pipelines in CompanyHub, we map each to a separate Zoho Potential layout or Sales Process if the Enterprise edition is selected.

CompanyHub Custom Tables map to Zoho CRM Custom Modules. This is the most complex object in the migration. CompanyHub's API returns row data but does not always expose field type definitions programmatically. During discovery we request screenshots or documentation of each Custom Table's field layout. We pre-create the Zoho Custom Module with matching field types (text, picklist, lookup, date, currency, checkbox, etc.) before importing any rows. Lookup relationships between Custom Tables require us to resolve the target module row IDs, which we handle by ordering imports to satisfy foreign-key dependencies.

CompanyHub Tasks (manual and Utron-generated) map to Zoho CRM Tasks. We preserve Task Title, Due Date, Status, Priority, and the linked Contact or Company. Owner assignment migrates by resolving the CompanyHub user email to the Zoho User record. Tasks generated by Utrons do not carry the Utron logic forward; we document them separately as part of the Utron rebuild specification.

CompanyHub Quotes map to Zoho CRM Quotes if the destination Zoho edition includes the Quotes module (Standard tier and above). Quote line items migrate as Quote Items with Product Name, Quantity, Unit Price, and Total. Quote templates and PDF references do not migrate; we document the template structure for manual recreation in Zoho's layout editor.

CompanyHub Users (deal owners, task assignees) map to Zoho Users by email address match. During discovery we extract all distinct user references on Contacts, Companies, Deals, and Tasks. Any CompanyHub User without a matching Zoho User is placed in a reconciliation queue for the customer's Zoho admin to provision before the record import phase begins.

CompanyHub email activity logs (sent, opened, clicked) map to Zoho CRM email records in the Contact or Account related list. Note that CompanyHub's API may return only email metadata (timestamp, recipient, open status) without full message body text depending on the API response payload. We flag any missing body content during scoping so the customer can decide whether to supplement with a separate email platform export. We migrate what the API provides and document the gap.

CompanyHub custom fields on Contacts, Companies, and Deals export as typed field definitions (text, number, date, picklist, checkbox, currency) with their values. We create matching Zoho CRM custom fields in the corresponding modules before importing record data. The field type must match exactly to avoid validation errors during import; a CompanyHub picklist custom field maps to a Zoho picklist custom field with the same option values.

CompanyHub UTrons are flowchart-based automations with no API export capability. We document each active Utron during discovery (trigger type, conditions, actions, assigned owners) and deliver a written rebuild specification that maps each Utron to an equivalent Zoho Workflow rule or Blueprint stage. Zoho Workflows use action-based triggers rather than flowchart nodes, so the translation requires reimplementation by the customer's Zoho admin or a Zoho-certified consultant. This is out-of-scope for migration as code but is fully documented for handoff.