Migrate from eZnet CRM to Freshsales

Export feasibility assessment and discovery

We audit the source eZnet CRM environment including tier (Standard, Professional, or Enterprise), total record counts by object type (Accounts, Contacts, Leads, Opportunities, Activities), presence of custom fields, Document Library volume, and any existing export history. Because eZnet CRM has no documented API, we confirm which CSV export mechanisms are available within the customer's tier and whether manual in-app exports are feasible given the data volume. If the account is on Standard tier and record counts approach or exceed 100K, we recommend a Professional tier upgrade before export proceeds. We deliver a written discovery report with record counts, field inventory, and export approach.

Schema design and Freshsales configuration

We design the destination Freshsales schema before any data moves. This includes creating custom fields mapped from eZnet's custom field definitions, configuring Deal pipelines and stages to match eZnet's pipeline structure, setting up Freshsales Lead fields and status values, defining Lead conversion rules in coordination with the admin, and configuring the Freshsales user profile to match eZnet's role-based assignments. We build the schema in a Freshsales sandbox or trial environment first and validate the field type mappings before committing to production configuration.

Sandbox migration and reconciliation

We run a full migration into the Freshsales staging environment using production-like data volume. The customer's admin reconciles record counts (Accounts in, Contacts in, Deals in, Leads in, Activities in) against the eZnet source exports, spot-checks 25-50 records for field accuracy, and reviews the pipeline stage and user assignments. Any field mapping corrections, missing picklist values, or custom field additions happen in this phase. Admin sign-off on the sandbox migration is required before production migration begins.

Owner reconciliation and user provisioning

We extract every distinct owner referenced on Accounts, Contacts, Deals, Activities, and Documents from eZnet CRM and match by email against the Freshsales destination. Owners without a matching Freshsales User are held in a reconciliation queue for the admin to provision before record import continues. Migration cannot reliably proceed past object creation without resolved owner references. We deliver a user mapping report listing matched owners, unmatched owners, and the admin actions required for each.

Production migration in dependency order

We run production migration in record-dependency order: Accounts first, then Contacts with Account IDs resolved, Deals with owner IDs and stage assignments resolved, Leads with status and custom fields populated, Activities (Tasks, Events, Notes) attached to parent Contacts and Accounts, and Document metadata as Notes. Each phase emits a row-count reconciliation report before the next phase begins. Document file blobs are exported as a separate package for the admin to re-upload post-migration. We pause writes in the source during the cutover delta to capture any records modified during the migration window.

Cutover, validation, and workflow rebuild handoff

We freeze eZnet CRM writes during the cutover delta, run a final delta migration of records modified during the window, then confirm Freshsales as the system of record. We validate record counts, spot-check pipeline data, and confirm user access. We deliver a written inventory of any eZnet Workflows, automations, or campaign sequences present in the source with a description of their trigger, conditions, and actions, plus a recommended Freshsales Workflow equivalent. We do not rebuild automations as code; that is a separate engagement or an internal admin task. We support a one-week post-cutover window for reconciliation issues raised by the customer's team.