Migrate from webCRM to Zoho CRM

webCRM Organisations map directly to Zoho CRM Accounts. We use Organisation Name as the deduplication key during import and map the webCRM Organisation ID to a custom field webcrm_id__c on Account for reconciliation. If webCRM stores a website URL on the Organisation, it maps to the Account Website field. Any Organisation-level custom fields are extracted individually during scoping, their Zoho field types are verified against the target edition's supported types, and missing custom fields are created before the Account import phase.

webCRM Contacts map directly to Zoho CRM Contacts. The Contact-to-Organisation lookup is preserved by resolving the webCRM Organisation ID or Organisation Name match during import. If the destination Account does not yet exist at import time, Contacts are held in a staging import batch until the Account import completes and the Account ID is available for the Contact.Organisation_ID lookup. Contact-level custom fields are extracted and mapped individually against Zoho's supported field types for the target edition.

webCRM Deals map to Zoho CRM Potentially Lost Deals. The Deal Stage name from webCRM maps to a Zoho CRM Stage value, which requires pre-import configuration of the Sales Process picklist to include all active webCRM Deal Stages. We check stage availability in the target Zoho edition during scoping and extend the Sales Process with any missing stage values before Deal import begins. Closed-Lost and Closed-Won reasons from webCRM custom properties map to Zoho Loss Reason and Win Reason fields if those fields exist in the target layout.

webCRM Deal Stage is a property of the Deal object, not a standalone entity. Each unique stage value from webCRM is pre-loaded into Zoho CRM's Sales Process stage picklist before Deal records are imported. Stage probability percentages from webCRM are mapped to Stage Probability values in Zoho, with rounding to Zoho's integer format. We configure one Sales Process per webCRM pipeline if the customer uses multiple pipelines.

webCRM Pipelines are containers for Deal Stages and represent lines of business or sales processes. Each webCRM Pipeline maps to a Zoho CRM Record Type on Potentially Lost Deal, with a corresponding Sales Process that scopes the relevant stage values to that pipeline. We configure Record Types and Sales Processes in Zoho before Deal import so that Deal records can be assigned to the correct Record Type at migration time.

webCRM Deliveries are order records with nested line-item detail, exported in webCRM Delivery XML format via the Zynk connector. We transform the nested XML into two flat CSV files: an Orders header table (Order ID, Account ID, Contact ID, Order Date, Delivery Date, Delivery Status) and an Order Line Items detail table (Order ID, Product, Quantity, Unit Price, Discount). We validate the relationship between Order header and Line Items after transformation. Note that the Orders module requires Zoho CRM Professional edition or higher; Standard edition does not include the Orders module.

webCRM Product Database records map to Zoho CRM Products. We map Product Name, Product Code (from webCRM hs_sku or equivalent), and Unit Price directly. If webCRM tracks inventory quantity, we map it to the Product Stock Quantity field, which requires Zoho Inventory to be enabled in the Zoho CRM Professional edition or higher.

webCRM Tasks linked to Organisations or Contacts map to Zoho CRM Tasks attached to the corresponding Account or Contact. Task Status, Priority, Due Date, and Description are mapped directly. webCRM task status labels are reconciled against Zoho's picklist values (Not Started, In Progress, Completed, Pending Input) during the field mapping phase. Activity timestamps are preserved as the Zoho Task Activity Date.

webCRM Automation Module rules are not exportable and cannot be migrated programmatically. We extract a full inventory of active automations during scoping, documenting each rule's name, trigger type (time-based, event-triggered, inactivity), conditions, and actions. This inventory is handed off to the customer's Zoho admin for rebuild in Blueprint or workflow rules post-migration. webCRM time-based automations may not have a direct Zoho Blueprint equivalent; some may require a Zoho extension or a Zoho Flow webhook-based rebuild.

webCRM custom fields on Organisations, Contacts, Deals, Products, and Tasks are extracted individually during scoping with their field names, field types, and picklist option values. We verify each against Zoho CRM's supported field types for the target edition and create any missing custom fields before data ingestion. Note that Zoho CRM Free edition does not support custom fields; customers on the Free plan must upgrade to Standard or above. Standard edition limits custom fields to 75 per module across 5 modules; Professional and above allow higher limits.

webCRM notes attached to Organisations, Contacts, or Deals map to Zoho CRM Notes linked via ContentDocumentLink to the corresponding Account, Contact, or Potentially Lost Deal. Note body and creation timestamp migrate directly. File attachments are mapped to Zoho Attachments where webCRM exports them as separate files; embedded attachments within webCRM records may require a separate extraction step and are flagged during scoping.