Migrate from NetHunt CRM to Zoho CRM

NetHunt Contact records map to Zoho CRM Contacts. Standard fields (Full Name, Email, Phone, Company Name) translate directly. Custom fields on Contact-type Records are translated to Zoho custom fields on the Contact module. We enumerate every NetHunt Folder containing Contact records and consolidate the per-folder field definitions into a single Zoho Contact module schema, creating Zoho custom fields for any field that does not have a Zoho standard equivalent.

NetHunt Lead records map to Zoho CRM Leads. Lead-specific fields like lead status, source, and score translate to Zoho Lead fields. NetHunt's lead lifecycle stages map to Zoho Lead Status values. We preserve the original NetHunt lead status value in a custom text field nethunt_lead_status__c on the Zoho Lead for audit continuity.

NetHunt Company records map to Zoho CRM Accounts. Company name maps to Account Name. Address, domain, industry, and employee count fields translate to standard Zoho Account fields. The Contact-to-Company linkage from NetHunt becomes a Zoho Contact lookup relationship to an Account. We build the Account records first so that AccountId is available for Contact import.

NetHunt Deal records map to Zoho CRM Deals. Deal name, value, stage, owner, and expected close date translate directly. Custom fields on NetHunt Deals create Zoho custom fields on the Deal module. NetHunt's deal stage values map to Zoho Stage values, with the stage probability percentages translated to the Zoho Stage Probability field.

NetHunt Pipelines are folder-level pipeline configurations with stage sets. We read every NetHunt pipeline definition during discovery, capture the stage names and order, and recreate them as Zoho CRM stage sets accessible via Custom Views. Multiple NetHunt pipelines map to separate Zoho Custom Views filtered by a Pipeline Name custom field on Deal records, preserving the visual pipeline separation teams rely on.

NetHunt Activities include notes, meeting records, and logged communications attached to Records. We parse the activity type indicator from NetHunt and route to Zoho Task (for calls and notes) or Event (for meetings). The original timestamp is preserved as Activity Date in Zoho. The activity is linked to the parent Zoho record (Contact, Lead, Account, or Deal) via the WhatId field.

NetHunt Call Logs stored as a record type map to Zoho Tasks with a Call disposition and duration preserved. The call direction (inbound/outbound) maps to a Zoho custom field. Duration in seconds is preserved in a custom field. We link the Task to the parent Contact, Lead, or Deal record via the WhatId field.

NetHunt custom fields are defined per folder, meaning the same record type can have different field schemas depending on which folder it lives in. We enumerate every unique custom field definition across all folders during discovery, deduplicate by field name and type, and create Zoho module-level custom fields for each. Where a field type does not match (e.g., NetHunt multi-select vs Zoho picklist), we translate to the nearest Zoho equivalent. This per-folder field enumeration is the primary scoping work for complex NetHunt migrations.

NetHunt Folders are the top-level organizational unit and contain mixed record types. We tag every migrated record with a custom text field nethunt_source_folder__c containing the original folder name. This allows Zoho users to recreate folder-based segmentation using Zoho Custom Views filtered by the source folder tag, preserving the organizational logic without migrating Folders as a separate object.

NetHunt Tags are string labels applied to Records for segmentation. Tags migrate as-is to Zoho CRM Tags. We flag any tags that exceed Zoho's tag character limit or contain special characters that may cause import errors and clean them during the transform phase.

NetHunt attachments linked to Records may reference files stored in the NetHunt UI or integrated services. We extract attachment URLs and metadata during export and attach them to the corresponding Zoho records via Zoho's attachment API. Attachments stored in third-party services integrated with NetHunt (e.g., DocHub) are flagged as links rather than embedded files; we verify the linked files remain accessible post-migration and update URLs if the integration credentials change.

NetHunt Owner assignments on Records map to Zoho CRM Users by email match. We extract every distinct owner referenced in the export and resolve against the destination Zoho org's User table. Any NetHunt owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes.