Migrate from erxes to Zoho CRM

Discovery and plugin audit

We audit the source erxes instance across all active plugins, GraphQL schema availability, custom field definitions (including field types and any type mismatches in existing data), pipeline and stage configurations, and user count. We confirm that all relevant plugins are active so that associated data objects are API-accessible. We also audit data volume (record counts per object) and engagement history size (conversation and task counts) to size the extraction architecture. The discovery output is a written migration scope document listing all objects to migrate, the extraction method per object, and any pre-migration cleanup flags.

Zoho edition selection and schema design

We recommend a Zoho CRM edition based on the migration scope. Standard ($14/user/mo annual) covers basic pipeline, contact, and account migration. Professional ($23/user/mo) is required if Blueprint process management or advanced automation is needed. Enterprise ($40/user/mo) is needed for custom modules, multi-pipeline configurations, or large team territories. We design the destination schema including custom fields on each module, pipeline and stage configuration, and layout assignments per record type. If the migration exceeds Zoho's 300-field limit on any module, we resolve the excess during this phase.

GraphQL extraction engineering

We build the GraphQL extraction scripts for each erxes object, implementing pagination over the erxes query results with checkpointing for resumable runs. For objects with large record volumes (over 10,000), we implement chunking and rate-limit handling with exponential backoff. We extract all objects in parallel where possible and in dependency order (Companies before Contacts, Accounts before Deals) so that parent-record IDs are available for lookup resolution during transform. The extraction phase produces structured CSV or JSON files per object with original erxes IDs preserved for reconciliation.

Data validation and field mapping

We validate the extracted erxes data against the target Zoho schema. This includes field type validation for custom fields (rejecting any value that does not conform to the Zoho field type), duplicate detection for Accounts and Contacts (using email and company name as dedupe keys), and owner reconciliation (matching erxes userId to Zoho User by email). Any erxes contacts without company associations that are candidates for Zoho Lead conversion are flagged in a split report for the customer to review before import. We also flag records with missing required fields and ask the customer to supply defaults or accept null values.

Sandbox migration and reconciliation

We run a full migration into a Zoho CRM Sandbox (or a trial org if Sandbox is not available) using production-equivalent data volume. The customer's admin reviews record counts, spot-checks 20-30 random records against the erxes source, and validates field mappings. Any mapping corrections (field name errors, incorrect picklist values, missing lookups) are corrected in the transform scripts and re-run in sandbox before production migration begins. This step prevents schema errors in production.

Production migration and cutover

We run the production migration in dependency order: Accounts (from erxes Companies), Contacts (with parent AccountId resolved), Leads (for unassociated contacts), Deals (with pipeline and stage IDs resolved), Tasks (with owner lookup resolved), and custom fields (mapped to Zoho layouts). Conversations migrate as Notes with channel metadata preserved in the Note body. After each object phase, we emit a row-count reconciliation report and pause for admin sign-off before proceeding. We freeze erxes writes during the cutover window, run a final delta migration of records modified during migration, and hand off to the customer's admin for Zoho user provisioning and role configuration.

Handoff and automation inventory delivery

We deliver the written inventory of erxes Automation Workflows, Channel configurations, and any excluded objects (custom objects that exceed Zoho's 300-field limit, or channel integrations that require separate Zoho product activation). We support a five-business-day hypercare window to resolve any reconciliation issues raised by the customer's team after cutover. We do not rebuild erxes automations in Zoho as part of the migration scope; that work is a separate Zoho configuration engagement. We do not provide post-migration admin training; Zoho's own onboarding documentation and partner ecosystem cover that scope.