Migrate from Exsalerate to Zoho CRM

Discovery and export feasibility assessment

We audit the source Exsalerate deployment across all objects in scope (Accounts, Contacts, Opportunities, Pipelines, Stages, To-Do Items, Email Activities, Custom Fields, and Users). The primary focus of discovery is confirming the export mechanism: we test the CSV export output, identify which objects are included in each export file, and assess whether direct database access is available for the specific Exsalerate deployment. We also inventory WorkflowMax quote cross-references on Opportunities and the colour tile encoding scheme on To-Do Items. The discovery output is a written migration scope confirming export feasibility, a preliminary object mapping, and a custom field audit against Zoho's 300-field limit.

Schema design in Zoho CRM

We design the destination Zoho CRM schema based on the discovery findings. This includes creating custom fields (with Zoho field types matched to Exsalerate field types), configuring Pipelines and Stages to match Exsalerate's pipeline and stage structure, creating any required Zoho custom modules if Exsalerate custom objects do not fit into standard modules, and building the custom picklist fields for activity tile colour encoding. We verify the 300-field and 5-lookup limits per module before deploying the schema. Zoho schema is deployed into a Zoho Sandbox or staging environment first for validation.

Data export and transformation

We extract data from Exsalerate using the confirmed export mechanism. Multiple CSV files (Accounts, Contacts, Opportunities, To-Do Items, Email Activities) are reconciled to resolve cross-references between objects. The WorkflowMax quote reference on Opportunities is extracted into a dedicated column for custom field mapping. Colour tile values on To-Do Items are normalised into the encoding scheme defined during schema design. Custom field picklist values are normalised to match Zoho picklist option names exactly. Owner email addresses are extracted for Zoho User resolution. The transformed data is validated against the Exsalerate source record counts before import begins.

Sandbox migration and reconciliation

We run a full migration into a Zoho staging environment using the transformed CSV files. The customer's Zoho admin and RevOps lead reconcile record counts (Accounts in, Contacts in, Deals in, Tasks in, Emails in), spot-check 20-30 random records against the Exsalerate source, and verify that the WorkflowMax cross-reference fields and colour tile fields are populated correctly. Any field mapping corrections, picklist value mismatches, or lookup resolution failures are corrected in the transform layer and the sandbox migration is re-run. Sign-off on the sandbox migration is required before production migration begins.

Owner reconciliation and Zoho User provisioning

We extract every distinct Exsalerate user referenced as an Owner on Account, Contact, Deal, and Task records and match by email against the Zoho destination's User table. Users without a matching Zoho User are listed in a reconciliation queue for the customer's admin to provision before production migration. We provide a user provisioning template with the required fields (Name, Email, Role, Profile) so the admin can create the users in Zoho and confirm readiness before import resumes. If the customer has inactive Exsalerate users whose records need to be preserved, the admin decides whether to provision inactive Zoho users or reassign records to an active user.

Production migration in dependency order

We run production migration in record-dependency order: Accounts first (the parent entity for Contacts and Deals), then Contacts (with AccountId resolved), then Deals (with AccountId and OwnerId resolved), then Tasks (with WhoId and WhatId resolved for activity records), then Email activities (linked to Contacts and Accounts). Each phase emits a row-count reconciliation report before the next phase begins. The WorkflowMax quote reference field on Deals is populated during the Deals phase. Activity tile colour fields on Tasks are populated during the Tasks phase. Custom field values for all objects are imported in the same phase as their parent record to avoid field-value loss on lookups.

Cutover, validation, and automation rebuild handoff

We freeze Exsalerate writes during the cutover window, run a final delta migration of any records modified during the migration window, then designate Zoho CRM as the system of record. We validate the production migration by running record count reconciliation, field population checks, and lookup chain verification (every Contact has an Account, every Deal has an Account, every Task has a WhoId). We deliver the WorkflowMax integration reconnection plan, the Exsalerate automation inventory document, and the Blueprint rebuild recommendations to the customer's Zoho admin. We do not rebuild Exsalerate's pipeline automation, WorkflowMax sync configurations, or Xero integration settings as Zoho Blueprint or Workflow Rules — these are delivered as written design briefs for the customer's admin or a Zoho partner to implement post-migration.