Migrate from OneHash CRM to Zoho CRM

OneHash Leads map directly to Zoho Leads with standard field mapping for name, email, phone, source, and status. Lead conversion history from OneHash — including conversion date and the resulting Customer or Contact record reference — is preserved as a custom text field for audit. Zoho Lead Status values are mapped from OneHash's lead status options; any OneHash-specific statuses are added to the Zoho picklist during schema setup.

OneHash Customer records (organization-level) map to Zoho Accounts. The Customer's primary contact email and billing address carry over. We use the Account Name as the dedupe key during import. OneHash's organization-level linkage to Contacts is preserved by creating Accounts first, then resolving the AccountId lookup on Contact records during the contact import phase.

OneHash Contacts follow ERPNext conventions (first_name, last_name, email, phone, organization linkage). They map 1:1 to Zoho Contacts, with the AccountId lookup resolved from the Account created from the associated OneHash Customer record. Any contact-level custom fields from OneHash DocTypes are mapped to Zoho Contact custom fields, subject to the 300-field module ceiling.

OneHash Opportunities track deal stages within Pipelines. They map to Zoho Deals with stage names, amount, probability, and party information preserved. The pipeline stage sequence from OneHash is mapped to Zoho Stage values; if OneHash uses multiple pipelines, each becomes a Zoho Deal Pipeline with its own stage sequence. Closed-Won and Closed-Lost reasons from OneHash custom fields become Zoho custom picklist fields.

OneHash pipeline stages map to Zoho Deal stages. We configure each Zoho Deal stage with probability percentages matching the OneHash stage values. If OneHash has custom probability settings per stage, these are applied to the corresponding Zoho stage during the Zoho configuration phase before migration begins.

OneHash Quotations carry line items linked to Items, with tax templates and terms. They map to Zoho Quotes. The Quotation-to-Opportunity linkage is preserved as a custom field Quote_Linked_Opportunity_ID__c on the Zoho Quote record so that the relationship is recoverable after migration even if Zoho's native opportunity-quote link requires reconfiguration. Item lookups are resolved against the Product records imported from OneHash Items.

OneHash Sales Orders reference Customers and Items and carry delivery and billing status flags. They map to Zoho Sales Orders. Order item rows are mapped field-by-field; custom Item fields from OneHash are preserved as custom fields on the Zoho Products where they appear, or consolidated into a JSON-encoded custom text field if they exceed the Zoho field ceiling. Delivery and billing status flags are preserved as Zoho Sales Order custom fields.

OneHash Items include product and service definitions with pricing, stock data, and custom attributes. They map to Zoho Products. Standard pricing migrates as Zoho's Standard Price Book entries. Any OneHash-specific Item fields (such as custom dimensions, HS codes, or industry-specific attributes) are mapped to Zoho Product custom fields, subject to the 300-field module limit. Items without a matching Zoho Product record are pre-created before the Sales Order import phase.

OneHash Employee records (designation, department, salary structure) include org-chart relationships that map to Zoho Users. We resolve OneHash Employee email addresses against the Zoho destination User table. Any OneHash Employee without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision. Salary structure and HR-specific fields do not map to Zoho CRM standard fields; they are preserved in a custom Notes field or excluded from migration scope depending on the customer's preference.

OneHash Projects carry Tasks, assignees, and time tracking. Zoho CRM does not have a native Projects module at the standard tier; Projects migrate as a Zoho custom module named Projects with a Tasks sub-module or linked custom module named Project Tasks. Open vs. completed status is preserved as a status field. Task-level comments are mapped as notes attached to the parent Project Task record.

OneHash allows unlimited custom fields per DocType via ERPNext's Customize Form tool. We run a pre-migration discovery pass that introspects each DocType's custom field definitions. We count the custom field total per destination Zoho module and compare it against the 300-field ceiling. Any DocType that exceeds the ceiling requires a field consolidation strategy: multi-value custom fields are encoded as JSON in a single text field, or the fields are split across a linked custom module. The consolidation approach is agreed with the customer during scoping.

Documents attached to any OneHash DocType are migrated as binary blobs. We preserve the original filename and linkage to the parent record. Zoho CRM stores attachments as ContentDocument records linked via ContentDocumentLink. Large attachments may require chunked download and upload due to API payload limits; we flag any attachment exceeding 10 MB during discovery for manual handling or alternative transfer.