Migrate from noCRM.io to Zoho CRM

noCRM Leads map to Zoho Leads if unqualified, or to Zoho Contacts attached to Accounts if qualified. We use noCRM's status field (Won, Lost, Cancelled map to Zoho Lead Status) and any custom qualification fields to determine the split. The original noCRM Lead ID is preserved in a custom Zoho field nocrm_lead_id__c for reconciliation. Unqualified Leads land in the Zoho Leads module; Leads at Won status with company name data are converted to Account-Contact pairs in Zoho during migration.

Each Pipeline Step in noCRM maps to a Zoho Deal Stage value. We export the step name, probability percentage, and order from noCRM Admin > Sales process and create matching Stage entries in Zoho CRM Setup > Pipelines. The stage-transition history is preserved as custom multi-select picklist field stage_history__c on the Deal record. Starter accounts with one pipeline map directly; Expert and Dream accounts with multiple pipelines create separate Zoho Pipelines or use Record Types for scoping.

noCRM Pipelines (Expert and Dream only; Starter is limited to one) map to Zoho CRM Pipelines. Each Pipeline and its Steps are exported together, and matching Pipelines are created in Zoho Setup > Pipelines before any Deal records are imported. The pipeline assignment on each noCRM Lead record resolves the Which Pipeline question at migration time.

Tags are freeform labels on noCRM Leads. We preserve all tag values and map them to a Zoho custom multi-select picklist field lead_tags__c on the Leads module. If the customer uses tags for segmentation, we also create matching Zoho Segments with the same membership logic documented separately for the admin to rebuild as Zoho Workflow Rules or CRM Filters.

Prospecting Lists in noCRM group Leads for outbound campaigns. We export list membership (Lead ID plus list assignment) and map it to Zoho Segments under the Leads module. Zoho Segments use filter criteria rather than explicit membership, so we document the membership logic and recommend the customer rebuild these as Zoho CRM Filters or Assignment Rules post-migration. If the customer requires static lists, we create Zoho custom fields tracking list membership.

The noCRM activity log (comments, status changes, step transitions) migrates to Zoho Notes linked to the Lead or Contact record. Each activity entry becomes a Zoho Note with the entry type noted in the Note title (e.g., 'Comment', 'Status Change: Won', 'Step Transition: Qualified to Demo'). The original timestamp is preserved in the Note body. Activity ordering is maintained by chronological sequence during import.

noCRM Users assigned to Leads (as owners) map to Zoho Users by email match. We extract every distinct owner_id from noCRM and cross-reference against the Zoho destination User table. Unmatched owners go to a reconciliation queue for the customer's Zoho admin to provision before record import resumes. Role and permission structures do not transfer directly and must be reconfigured in Zoho Setup > Users and Control.

noCRM Predefined Fields (custom lead fields configured under Admin > Sales process > Predefined Fields) are account-specific. We extract the field name, data type, and picklist values from noCRM and create matching custom fields in Zoho CRM Leads module (or Contacts module for qualified leads). Field type mapping: text fields map to Zoho Single Line, number fields map to Zoho Number or Currency, date fields map to Zoho Date, picklist fields map to Zoho Picklist. The field labels and API names are preserved to minimize downstream reporting disruption.

Files attached to noCRM Leads are exported as binary blobs alongside the lead record. We map them to Zoho CRM Attachments linked to the corresponding Lead or Contact record. The original file name and attachment reference are preserved. Zoho's 5 GB per-file import limit applies; files exceeding this are flagged during scoping for manual alternative handling. Attachments larger than 25 MB per file may require chunking or cloud storage linking.

noCRM Statistics exports (company performance, team activity, forecasts, lead performance per Prospecting List) are aggregate reports exported as Excel or JSON. We import the raw lead data underlying these reports and map aggregate metrics to Zoho Custom Report configurations documented for the admin to rebuild in Zoho Analytics or Zoho Reports. The performance data itself does not have a direct report equivalent and requires manual rebuild in Zoho's reporting module.

Custom Actions in noCRM are account-specific menu items on Lead cards that trigger external workflows (e.g., adding won leads to an invoicing system). These are non-standard and require individual documentation. We inventory every Custom Action name, trigger condition, and target URL or API call, then document a Zoho equivalent (Custom Button, Deluge Function, or Webhook) for the admin to rebuild post-migration. Custom Actions do not migrate as code.

Quotes and Invoices integrated in noCRM Dream tier are stored as separate documents linked to Leads. These are not part of the standard lead export and require a separate document migration step outside the standard scope. We flag Quote and Invoice records during scoping and offer a separate document migration engagement if the customer requires them moved to Zoho Books or a Zoho-supported quoting tool.