Migrate your Zoho CRM data

Standard module with full CRUD via REST API v8. Exports include standard fields plus custom fields. We map Lead_Status and Lead_Source to destination equivalents and handle the lead-to-contact conversion lifecycle during import.

Core module backed by a well-documented schema. Supports custom fields, lookup relationships to Accounts, and multi-address records. We preserve the Contact-to-Account link by sequencing Account imports before Contact imports.

Account module supports multiple addresses, custom fields, and related Contact and Deal lookups. API returns Account_ID as a stable external identifier, which we use for cross-object relationship reconstruction.

Zoho's deal module supports multiple pipelines and custom stage names. We map pipeline stage names and preserve Stage, Amount, Closing Date, and Owner (user) assignments. Multi-pipeline support requires Enterprise or above.

Product catalog module with price book support. Standard fields include Product_Code, Unit_Price, and Quantity_Unit. We migrate Products before Quotes and Sales Orders to preserve product references in child records.

These subform-heavy modules reference Products and Contacts. Zoho nests line items as related records rather than inline fields, requiring separate API fetches. We pull parent and child records together and reconstruct the document hierarchy in the destination.

Activity modules track sales engagement history. Zoho stores these with polymorphic relationships to parent records. We migrate open activities and preserve the linked-to-record association, but completed historical activities may be excluded by scope to reduce API credit consumption.

Attachments are stored as separate file records linked to parent modules via lookup IDs. They do not appear in standard CSV exports and must be fetched via the Attachments API endpoint. We handle attachment re-upload via the destination platform's file API, using original filenames and MIME types preserved from Zoho.

Custom modules are supported via the Custom API endpoint and can be discovered via GET /settings/fields. Schema varies per tenant. We introspect the custom module's field metadata before mapping, since field types and picklist values differ across implementations.

Blueprints are Zoho's workflow automation engine, storing process rules as configuration rather than records. They do not export as data. We document which Blueprints exist so customers can rebuild equivalent automation in the destination platform post-migration.

User records carry role, profile, and territory assignments. Migration target systems require user email matching or external ID assignment. We flag that inactive users may need to be activated or marked separately in the destination.

Tags are cross-module label objects. They export with the parent record in CSV but require separate API extraction for bulk migration. We parse tag arrays and reconstruct them in the destination using the target platform's tagging API.