Migrate from CentraHub CRM to Zoho CRM

CentraHub Lead records map directly to Zoho CRM Leads. The Lead Source, Lead Status, and Owner fields migrate 1:1. We use Zoho's Leads API endpoint with field mapping against the CentraHub field schema extracted during discovery. Any lead scoring custom field on CentraHub maps to a Zoho Multi-Select Picklist or a numeric custom field depending on scoring granularity.

CentraHub Accounts map to Zoho Accounts. The Account Name becomes the Account Name in Zoho; the industry, website, phone, and address fields map to Zoho standard fields. Account is written first in the migration sequence so that the Account ID is available as a lookup anchor for Contacts and Deals that reference it by CentraHub ID.

CentraHub Contacts map to Zoho Contacts with the parent Account ID resolved via our lookup table. We extract the CentraHub account_id column from the Contacts CSV, match it against the Account ID lookup table generated during Account migration, and write the correct Zoho Account lookup ID on every Contact record. First Name, Last Name, Email, Phone, and Title migrate to Zoho standard fields.

CentraHub Deals map to Zoho Deals (Opportunities in Zoho terminology). The deal stage maps to Zoho Stage, the amount maps to Amount, and the close date maps to Closing Date. The parent Account ID is resolved using the same lookup table approach as Contacts. Pipeline assignment requires the customer to configure Zoho Pipeline and Stage values before migration so that we can map CentraHub pipeline IDs to the correct Zoho pipeline.

CentraHub Tasks map to Zoho Tasks. Subject, Due Date, Priority, and Status migrate directly. The Task owner maps via email-match lookup to the Zoho User table. Custom task types (priority values beyond High/Medium/Low) are validated against Zoho's picklist during transformation and flagged if they fall outside the destination's allowed values.

CentraHub Appointments map to Zoho Events. Start Date/Time, End Date/Time, Venue (Location), and description migrate directly. Timezone normalization occurs during transformation: all timestamps are normalized to UTC before writing to Zoho, and we flag any appointment that falls outside the destination user's timezone availability window.

CentraHub Activities (calls, emails, and notes) log against Leads, Accounts, Contacts, or Deals. We map the activity type picklist (Call, Email, Note) from CentraHub to the corresponding Zoho activity type. Call duration, disposition, and recording URL transfer to Zoho's Call custom fields if configured; email content migrates as a Zoho note linked to the parent record. The WhoId and WhatId are resolved via our lookup tables to produce the correct Zoho Contact or Deal link.

CentraHub custom fields per module (text, number, picklist, date, phone, email, website, geolocation) are extracted as a schema inventory during discovery. Each custom field is pre-created in Zoho CRM using the equivalent field type before any record migration begins. We validate CentraHub field values against the declared data type and flag records with type mismatches (e.g., a text string in a number field) because Zoho enforces type validation on import and will reject mismatched records.

Tags applied across objects in CentraHub migrate to Zoho Tags. Zoho Tags are a cross-module taxonomy; we map the tag values directly and flag any tag that does not have an exact match, presenting the customer with a rename option during validation.

CentraHub file attachments on records are exported from Dropbox or Box integrations (for Centra Hosted edition) or downloaded from the UI. We store them in temporary cloud storage, then re-attach them post-import using Zoho's Attachments API endpoint, preserving the parent record link. This step runs after all primary object migration completes.