Migrate from webCRM to Freshsales

webCRM Organisations map to Freshsales Accounts. The Organisation Name maps to Account Name; the Organisation ID becomes the dedupe key for import. We export Organisations first as a standalone batch because every Contact in Freshsales requires an AccountId or must be imported as a lead without account linkage. Custom fields on Organisation migrate to Freshsales custom fields on Account, created before import.

webCRM Contacts link to Organisations via Organisation ID. We export both objects together, resolve the Organisation-to-Account ID mapping during the Organisations phase, then insert Contacts with AccountId populated from the lookup table. Email serves as the dedupe key for Contact uniqueness. Mobile and phone numbers migrate as custom fields if Freshsales standard phone fields are insufficient.

webCRM Deals represent pipeline opportunities tied to Organisations and Contacts. We map deal stages individually since pipeline stage names vary between webCRM and Freshsales. Deal value, close date, and pipeline assignment transfer directly. Owner assignment resolves via email match to Freshsales User records in the reconciliation queue.

webCRM Deliveries are exported in webCRM Delivery XML format via Zynk. The nested XML structure with parent delivery headers and child line-item detail requires flattening before Freshsales ingestion. We parse the XML into two record types: Order (parent) and Order Line Item (child), with the parent Deal linked via WhatId. Quantity, unit price, and product reference transfer to the line item.

webCRM maintains a Product Database with pricing and description fields. We export Products as standalone records and associate them with Deals or Order Line Items on the Freshsales side based on the customer's product-to-deal linking pattern observed during scoping. ProductCode maps from webCRM sku fields.

webCRM Tasks are activity records linked to Organisations or Contacts. We export them as Tasks in Freshsales, preserving task status, priority, due date, and the parent record reference. Task assignments migrate by resolving webCRM owner email to Freshsales User. Note that Freshsales Activities (Apideck: Considering, not live) are not yet a supported API resource, so task-based activity tracking is the primary engagement record type.

webCRM's Automation Module stores time-based and event-triggered workflows internally with no public export endpoint. These are not accessible via export and cannot be migrated. We identify every active automation during scoping, document its trigger conditions and actions, and deliver a written inventory mapping each webCRM automation to an equivalent Freshsales Workflow configuration. The customer's admin rebuilds them post-migration; budget 1-2 hours per automation rule.

Organisations, Contacts, Deals, and other objects in webCRM support custom fields. We extract the full custom field schema during scoping, including field type, required flag, and picklist values where applicable. Each field maps individually to the Freshsales equivalent (custom field on the corresponding object). Freshsales custom fields are created before any data import to avoid import errors from undefined field references.