---
title: "Migrate to Zoho CRM: CRM Migration Guide & Service"
description: "Migrating to Zoho CRM? Import limits, the full migration checklist and every source FlitStack AI moves into Zoho CRM, with history and rollback."
url: "https://flitstack.ai/migrations/crm/zoho-crm"
---

# Migrate to Zoho CRM

Zoho CRM is a module-driven, edition-tiered CRM whose import success depends on pre-creating Modules, mapping picklist values exactly, and sequencing Layout-Pipeline-Stage before any deal row is loaded.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into Zoho CRM from 850+ CRMs, including Salesforce, Act!, HubSpot, Mailchimp. Every field is mapped to Zoho CRM's objects, history and associations come across, the Zoho CRM setup is configured alongside, and the whole migration stays reversible in one click.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [Zoho CRM implementation service →](https://flitstack.ai/services/zoho-crm-implementation)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

From Any source ![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp) ![](https://flitstack.ai/platforms-trim/act.webp) ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Destination Zoho CRM ![](https://flitstack.ai/platforms-trim/zoho-crm.webp)

Salesforce Act! HubSpot Mailchimp ActiveCampaign

850+ sources mapped into Zoho CRM

## Systems we move into Zoho CRM

The CRMs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

[Salesforce to Zoho CRM](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/zoho-crm) [Act! to Zoho CRM](https://flitstack.ai/migrations/crm/act/to/zoho-crm) [HubSpot to Zoho CRM](https://flitstack.ai/migrations/crm/hubspot/to/zoho-crm) [Mailchimp to Zoho CRM](https://flitstack.ai/migrations/crm/mailchimp/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/activecampaign.webp) ActiveCampaign to Zoho CRM](https://flitstack.ai/migrations/crm/activecampaign/to/zoho-crm) [Pipedrive to Zoho CRM](https://flitstack.ai/migrations/crm/pipedrive/to/zoho-crm) [monday CRM to Zoho CRM](https://flitstack.ai/migrations/crm/monday-crm/to/zoho-crm) [Dynamics 365 to Zoho CRM](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/zoho-crm) [Insightly CRM to Zoho CRM](https://flitstack.ai/migrations/crm/insightly-crm/to/zoho-crm) [Odoo CRM to Zoho CRM](https://flitstack.ai/migrations/crm/odoo-crm/to/zoho-crm) [ServiceTitan to Zoho CRM](https://flitstack.ai/migrations/crm/servicetitan/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/pbs-systems.webp) PBS Systems to Zoho CRM](https://flitstack.ai/migrations/crm/pbs-systems/to/zoho-crm) [Bigin by Zoho CRM to Zoho CRM](https://flitstack.ai/migrations/crm/bigin-by-zoho-crm/to/zoho-crm) [Sage CRM to Zoho CRM](https://flitstack.ai/migrations/crm/sage-crm/to/zoho-crm) [Close to Zoho CRM](https://flitstack.ai/migrations/crm/close/to/zoho-crm) [MarketSharp to Zoho CRM](https://flitstack.ai/migrations/crm/marketsharp/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/bitrix24.webp) Bitrix24 to Zoho CRM](https://flitstack.ai/migrations/crm/bitrix24/to/zoho-crm) [Daylite to Zoho CRM](https://flitstack.ai/migrations/crm/daylite/to/zoho-crm) [Jobber to Zoho CRM](https://flitstack.ai/migrations/crm/jobber/to/zoho-crm) [Zendesk Sell to Zoho CRM](https://flitstack.ai/migrations/crm/zendesk-sell/to/zoho-crm) [HoneyBook to Zoho CRM](https://flitstack.ai/migrations/crm/honeybook/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/act-on.webp) Act-On to Zoho CRM](https://flitstack.ai/migrations/crm/act-on/to/zoho-crm) [Attio to Zoho CRM](https://flitstack.ai/migrations/crm/attio/to/zoho-crm) [Homesnap Pro to Zoho CRM](https://flitstack.ai/migrations/crm/homesnap-pro/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/sugarcrm.webp) Sugarcrm to Zoho CRM](https://flitstack.ai/migrations/crm/sugarcrm/to/zoho-crm) [Twenty CRM to Zoho CRM](https://flitstack.ai/migrations/crm/twenty-crm/to/zoho-crm) [Housecall Pro to Zoho CRM](https://flitstack.ai/migrations/crm/housecall-pro/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/convertkit.webp) Convertkit to Zoho CRM](https://flitstack.ai/migrations/crm/convertkit/to/zoho-crm) [LeadSimple to Zoho CRM](https://flitstack.ai/migrations/crm/leadsimple/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/copper.webp) Copper to Zoho CRM](https://flitstack.ai/migrations/crm/copper/to/zoho-crm) [Kartra to Zoho CRM](https://flitstack.ai/migrations/crm/kartra/to/zoho-crm) [Snovio to Zoho CRM](https://flitstack.ai/migrations/crm/snovio/to/zoho-crm) [Practice by Numbers to Zoho CRM](https://flitstack.ai/migrations/crm/practice-by-numbers/to/zoho-crm) [Freshsales to Zoho CRM](https://flitstack.ai/migrations/crm/freshsales/to/zoho-crm) [Aweber to Zoho CRM](https://flitstack.ai/migrations/crm/aweber/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/clio.webp) Clio to Zoho CRM](https://flitstack.ai/migrations/crm/clio/to/zoho-crm) [Dubsado to Zoho CRM](https://flitstack.ai/migrations/crm/dubsado/to/zoho-crm) [Dynamics 365 Marketing to Zoho CRM](https://flitstack.ai/migrations/crm/dynamics-365-marketing/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/customer-io.webp) Customer.io to Zoho CRM](https://flitstack.ai/migrations/crm/customer-io/to/zoho-crm) [![](https://flitstack.ai/platforms-trim/sendcloud.webp) SendCloud to Zoho CRM](https://flitstack.ai/migrations/crm/sendcloud/to/zoho-crm)

## What Zoho CRM supports, and where its import tools stop

- Free tier is genuinely usable for up to 3 users with leads, pipeline management, and email tracking — no credit card required, making it easy to evaluate before committing.
- Pricing undercuts Salesforce by 80–90% at equivalent feature tiers, with Enterprise plans offering capabilities that cost 3–4× more on competing platforms.
- Deep ecosystem of 45+ integrated apps (Books, Desk, Creator, Campaigns) means companies already in the Zoho suite get native integrations without third-party connectors.
- Highly customizable: custom modules, custom fields, Canvas drag-and-drop layouts, and Blueprint workflow automation without requiring developer resources.

**Bulk API** OAuth 2.0 (Zoho-oauthtoken)

**Rate limits** Starter: 500 req/min | Professional: 2,500 req/min | Enterprise: 10,000 req/min, plus a credit-based system for complex queries (1–3 credits per COQL fetch)

| Object                                          | Support | Note                                                                                                                                                                                                                                                                                                                           |
| ----------------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Leads                                           | full    | 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.                                                                                         |
| Contacts                                        | full    | 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.                                                                                             |
| Accounts (Companies)                            | full    | 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.                                                                                                           |
| Deals (Opportunities)                           | full    | 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.                                                                                                |
| Products                                        | full    | 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.                                                                                                    |
| Quotes, Sales Orders, Purchase Orders, Invoices | mapped  | 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.                                                          |
| Tasks, Events, Calls                            | mapped  | 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                                     | mapped  | 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                                  | mapped  | 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                                      | none    | 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.                                                        |
| Users                                           | mapped  | 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                                            | mapped  | 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.                                                                                    |

## The Zoho CRM migration guide

## Why teams migrate to Zoho CRM

*The four shapes a Zoho CRM migration takes, and what makes the platform easier — or harder — than the category average.*

Zoho CRM is a cloud customer relationship management application developed by Zoho Corporation, an India-based technology company founded in 1996 by Sridhar Vembu and Tony Thomas and headquartered in Chennai[1](https://flitstack.ai/migrations/crm/zoho-crm#source-1). Sales-side CRM is the historical core, now sold standalone and inside the broader Zoho One bundle alongside Desk, Books, Campaigns, Projects and forty-plus sibling apps.

The typical Zoho CRM customer is a 20-to-500-employee business buying on price and bundle economics — Standard starts around $14 per user per month, and Zoho One bundles forty-plus apps at around $45 per user per month[4](https://flitstack.ai/migrations/crm/zoho-crm#source-4).

Compared with HubSpot, Zoho positions on cost-per-seat and breadth of suite; compared with Salesforce, on a 90 percent cost-saving claim and lighter admin overhead; compared with Pipedrive, on a deeper module model with Custom Modules, Blueprint state machines, and Deluge scripting.

The shapes of migration that land on Zoho CRM tend to fall into four patterns. First, HubSpot exits, driven by the contact-tier pricing model — practitioners cite saving $12,000 per year by moving a 35-person team off HubSpot's $1,600/month tier[2](https://flitstack.ai/migrations/crm/zoho-crm#source-2). Second, Salesforce exits, where Zoho pitches a minimum 90 percent cost saving as the headline trigger[4](https://flitstack.ai/migrations/crm/zoho-crm#source-4).

Third, suite consolidation: replacing Pipedrive plus Mailchimp plus Zendesk with Zoho CRM plus Campaigns plus Desk inside Zoho One. Fourth, legacy ACT! and Maximizer replacements where the source is a desktop database. The Data Migration wizard ships native presets for Salesforce, Pipedrive, HubSpot, Highrise, Insightly, MS Dynamics and Maximizer[9](https://flitstack.ai/migrations/crm/zoho-crm#source-9).

What makes migrating to Zoho CRM easier than the category average is the Data Migration wizard itself — it auto-creates Modules that do not exist on the destination, auto-maps file columns to fields, and supports CSV, XLS, XLSX and vCard formats[22](https://flitstack.ai/migrations/crm/zoho-crm#source-22).

What makes it harder than the average is the edition-tier architecture, which gates Custom Modules, Sandboxes, Multiple Pipelines and most Custom Field types behind Enterprise or Ultimate, plus storage caps that bite mid-migration on smaller editions[37](https://flitstack.ai/migrations/crm/zoho-crm#source-37).

The picklist value model rejects values that do not exist on the destination dropdown, the Layout-Pipeline-Stage dependency rejects deal rows on any mismatch[152](https://flitstack.ai/migrations/crm/zoho-crm#source-152), and Created Time and Modified Time on most modules are system-managed and cannot be overwritten on import[102](https://flitstack.ai/migrations/crm/zoho-crm#source-102).

Workflows, Blueprint state machines, assignment rules and scoring rules do not import — they are rebuilt from documentation. Teams that scope the rebuild work up front finish on time; teams that assume parity do not.

> Zoho's bundle economics get teams in the door; the edition-tier architecture and Layout-Pipeline-Stage coupling decide whether they stay on schedule.

## The Zoho CRM data model you need to map into

*Modules, Layouts, picklists, lookups, and the External-ID upsert keys you'll wire on every field — the destination schema decoded.*

Zoho CRM is built around Modules — the platform's term for what Salesforce calls Objects and HubSpot calls Objects. Each Module carries standard and custom fields, sits behind one or more Layouts, and connects to other Modules through Lookups and Multi-Select Lookups. Permission is governed by Profiles; record visibility by Roles and optionally Territories.

Before mapping any source field, you need to know which destination Module the row belongs in, which Layout it inherits, and which value will serve as its upsert key. The table below summarises the standard Modules a Zoho CRM migration will touch[10](https://flitstack.ai/migrations/crm/zoho-crm#source-10).

| Object                                                                      | What it stores                             | Required                                                     | Tier                         |
| --------------------------------------------------------------------------- | ------------------------------------------ | ------------------------------------------------------------ | ---------------------------- |
| Leads                                                                       | Unqualified prospects pre-conversion       | Last Name                                                    | All editions                 |
| Contacts                                                                    | Individual people associated with Accounts | Last Name                                                    | All editions                 |
| Accounts                                                                    | Companies / organisations                  | Account Name                                                 | All editions                 |
| Deals                                                                       | Revenue opportunities in a pipeline        | Deal Name, Stage, Closing Date, Pipeline (if multi-pipeline) | All editions                 |
| Tasks / Calls / Meetings                                                    | Activity records on a parent               | Subject, Owner (and times for Meetings)                      | All editions                 |
| Cases / Solutions                                                           | Service tickets and KB articles            | Subject, Account                                             | All editions                 |
| Products / Price Books / Quotes / Sales Orders / Purchase Orders / Invoices | Catalogue and quote-to-cash records        | Per-module — see field requirements                          | All paid editions            |
| Campaigns / Vendors                                                         | Marketing program and supplier records     | Campaign Name; Vendor Name                                   | All editions                 |
| Custom Modules                                                              | Customer-defined record types              | Schema defined first; per-field requirements                 | Enterprise and Ultimate only |

Records get matched by what Zoho calls duplicate check fields — fields marked with the Do not allow duplicate values property. Email is the common duplicate check on Leads and Contacts; Account Name on Accounts. Once marked unique, the import upsert flow uses it to decide insert-versus-update[43](https://flitstack.ai/migrations/crm/zoho-crm#source-43).

Deals, Cases, and Custom Modules have no natural unique key — create a custom single-line text field, mark Do not allow duplicate values, and populate from the source system's primary key. Zoho supports an explicit External ID field type that lets the upsert flow match against a foreign system's identifier without disturbing the internal Zoho ID[51](https://flitstack.ai/migrations/crm/zoho-crm#source-51).

When you upsert, Zoho checks the duplicate-check field set: if a match exists, the record updates; if none, it inserts. You can also pass Zoho's internal Record ID directly when re-importing your own export — the Record ID is the canonical primary key and bypasses duplicate-check matching entirely. Custom field types determine validation, storage and edition availability.

| Field type                                 | Limit                                                                                     | Notes                                                                                                           |
| ------------------------------------------ | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Single-line text                           | 255 characters                                                                            | Plain string; can be marked unique[70](https://flitstack.ai/migrations/crm/zoho-crm#source-70)                  |
| Multi-line text                            | Up to 32,000 chars (large)                                                                | Small / large variants; large is Enterprise+[70](https://flitstack.ai/migrations/crm/zoho-crm#source-70)        |
| Number / Decimal / Currency / Percent      | Up to 16 digits                                                                           | Currency respects org multi-currency setup                                                                      |
| Date / Date-Time                           | Org timezone                                                                              | Date format set per locale; mismatch rejects import[22](https://flitstack.ai/migrations/crm/zoho-crm#source-22) |
| Picklist (single-select)                   | Per-edition count limit                                                                   | Display label and reference value can differ[67](https://flitstack.ai/migrations/crm/zoho-crm#source-67)        |
| Multi-Select Picklist                      | Per-edition count limit                                                                   | Semicolon-delimited on import                                                                                   |
| Lookup                                     | One target Module                                                                         | One-to-many; populated by lookup name or ID                                                                     |
| Multi-Select Lookup                        | Enterprise and above                                                                      | Establishes many-to-many via hidden linking module                                                              |
| Formula                                    | Max 5,000 chars in expression[65](https://flitstack.ai/migrations/crm/zoho-crm#source-65) | Return type fixed at creation; cannot be changed[70](https://flitstack.ai/migrations/crm/zoho-crm#source-70)    |
| Rollup Summary / Auto-Number / External ID | Higher editions                                                                           | Rollup Summary is read-only post-creation[64](https://flitstack.ai/migrations/crm/zoho-crm#source-64)           |

Relationships in Zoho CRM model parent-child through Lookup fields and many-to-many through Multi-Select Lookup fields, which silently create a hidden linking Module visible in Developer Hub → Data Model. A Contact has a Lookup to one Account; a Deal has Lookups to one Account and one Contact. There is no native cascade delete — deleting a parent does not delete children, which is a behaviour your workflow logic must reproduce if the source platform relied on it.

**5,000 / 5M** Free-tier records vs Professional record cap The free edition stores 5,000 records (10 MB). Professional jumps to 10 GB and 5 million records — and that ceiling decides whether you can land your full historical activity log on day one.

Custom Modules participate in Lookups the same way standard modules do, with the same upsert semantics. They are Enterprise and Ultimate only, and their schema, Layouts and unique-ID fields must exist on the destination before any record can be imported[11](https://flitstack.ai/migrations/crm/zoho-crm#source-11). Subforms — Zoho's pattern for related-list inline rows — are limited to one per module and migrate as child records, not parent-row payloads.

## Pre-migration prep — the work before you touch Zoho CRM

*What must be true on the source, the destination, and across the team before the first row hits the Data Migration wizard.*

The single best predictor of a clean Zoho CRM migration is how much work happens on the source side before the first import button is pressed. Zoho's Data Migration documentation devotes most of its prep checklist to source-side hygiene — file format, date format, mandatory-field coverage, drop-down value alignment — because the wizard rejects rows quietly on any mismatch and surfaces the reasons in Import History after the fact[22](https://flitstack.ai/migrations/crm/zoho-crm#source-22).

> Zoho's Data Migration wizard is fast when the source file is clean and unforgiving when it isn't — pre-processing is where the time savings come from.

Treat the source export as raw material that must be shaped to Zoho's expected formats — emails lowercased, picklist labels converted to the values on Zoho's destination drop-downs, dates rewritten in the org locale format, currency stripped of symbols, and owners resolved to Zoho user emails or IDs.

### Source-side prep

- Audit and dedup the source database before export — Zoho's de-duplicate tool runs post-import and is slow on large datasets[156](https://flitstack.ai/migrations/crm/zoho-crm#source-156). Catch case-only email duplicates and trailing-whitespace duplicates in the source export, not after they land.
- Convert picklist display labels to the picklist values that exist on the Zoho destination for every drop-down field — Lead Status, Lead Source, Deal Stage, Industry, every Custom Picklist. The Data Migration wizard rejects values not in the destination picklist and surfaces a row-level error in the result file[22](https://flitstack.ai/migrations/crm/zoho-crm#source-22).
- Save every CSV as UTF-8 before upload. Zoho's troubleshooting docs explicitly call out character-encoding errors as the most common import failure mode — non-UTF-8 files produce garbled accented characters or full row rejection[113](https://flitstack.ai/migrations/crm/zoho-crm#source-113).
- Stamp a stable external ID on every record in the source export — a UUID or the source platform's primary key — so re-runs and reconciliation are deterministic. This is the value you populate into Zoho's External ID field type on import[51](https://flitstack.ai/migrations/crm/zoho-crm#source-51).
- Decide what is in scope for historical activities. Tasks, Calls and Meetings can be imported, but Created Time on these modules is system-managed in many cases, and the original activity date often must be carried in a custom Activity Date field[102](https://flitstack.ai/migrations/crm/zoho-crm#source-102).

### Destination-side prep

- Create a Sandbox from Setup → Data Administration → Sandbox on Enterprise or Ultimate. Sandboxes accept a Configuration-only copy or a Configuration + Sample Data copy — use the former to test schema and workflows, the latter to dry-run the full migration with representative volumes[76](https://flitstack.ai/migrations/crm/zoho-crm#source-76) [77](https://flitstack.ai/migrations/crm/zoho-crm#source-77).
- Provision Users, Profiles and Roles before importing — owner assignment fails silently if a referenced user email does not exist in Zoho, and the row imports with the import-user set as owner instead.
- Pre-create every custom field on the right Module and Layout with the right type — Field Type cannot be changed after creation (you cannot turn a Text field into an Integer later)[70](https://flitstack.ai/migrations/crm/zoho-crm#source-70).
- Build Layouts, Pipelines and Stages before importing Deals — Pipelines belong to Layouts and Stages belong to Pipelines, and the import skips any row whose Layout-Pipeline-Stage triple is inconsistent[152](https://flitstack.ai/migrations/crm/zoho-crm#source-152).
- Define Custom Modules, their unique-ID fields, and their Lookups before importing. Custom Module schemas must exist before records of that type can be created, and Custom Modules are gated to Enterprise and Ultimate editions[11](https://flitstack.ai/migrations/crm/zoho-crm#source-11).

### People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every department that touches the CRM. Train sales reps on Zoho's daily-workflow patterns, Deal stage transitions and Blueprint enforcement before go-live, not after. A clean Pipedrive-to-Zoho or HubSpot-to-Zoho migration of under 25,000 records can land inside one business day; a Salesforce-to-Zoho with Custom Modules and Blueprint rebuilds runs two to four weeks of elapsed time.

## Import mechanisms: UI wizard and Data Migration

*Two paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at the edition-tier ceiling.*

Zoho CRM exposes two load paths and the right one depends on dataset size, Module mix, and whether the load must be re-run idempotently. The native Import wizard handles most one-shot migrations under a few hundred thousand records. The Data Migration wizard adds source-CRM presets and auto-Module creation.

### Native Import wizard

The per-Module Import wizard lives at the top right of any Module list view or under \*Setup → Data Administration → Import\*[22](https://flitstack.ai/migrations/crm/zoho-crm#source-22). It accepts CSV (UTF-8), XLS, XLSX and vCard (VCF). Each Module is imported as a separate file. The wizard maps columns to fields, lets you set assignment rules, choose Clone / Skip / Overwrite behaviour for duplicates, and run a sample before committing the full file.

Per-file size limits are edition-tiered: CSV files cap at 5 MB on Free, 10 MB on Standard and Professional, and 25 MB on Enterprise and Ultimate; VCF caps at 5 MB across all editions. Per-batch row limits are also edition-tiered — Zoho CRM Plus lists 10,000 records per batch as the import-data ceiling[39](https://flitstack.ai/migrations/crm/zoho-crm#source-39).

The right call: the Import wizard for one-shot loads under 100,000 records on standard Modules, or whenever you want a visual mapping review before commit.

### Data Migration wizard

The Data Migration wizard, under Setup → Data Administration → Data Migration, is the larger-scope tool. It ships pre-built presets for Salesforce, Pipedrive, HubSpot, Highrise, Insightly, MS Dynamics, Maximizer and other Zoho CRM accounts, and supports direct connector-driven transfer from Pipedrive, Capsule, HubSpot, Insightly, Highrise, Bitrix and Bigin without intermediate file generation[9](https://flitstack.ai/migrations/crm/zoho-crm#source-9).

When a source Module does not match an existing Zoho Module, the wizard auto-creates the destination Module and maps the columns to its fields.

The wizard is the right pick when the source is one of the supported CRMs and the migration is largely one-shot. It is the wrong pick when the migration requires repeated dry-runs over weeks or reconciliation against a parallel source-of-truth.

### Third-party staging tools

Tools like Fivetran, Airbyte, Stitch, Workato and Make sit between source and destination. They are used in two ways: (a) reverse-ETL where the source loads into a warehouse, gets transformed in SQL, then syncs into Zoho; and (b) staging-and-validate, where the tool handles type coercion and dedup before the result feeds the importer. Workato and Make are also common for ongoing post-migration sync, paired with Deluge.

Under 10,000 records on standard Modules → native Import wizard. 10,000–100,000 with a supported source preset → Data Migration wizard. Larger or repeatable loads → staged through a warehouse with an iPaaS layer feeding the importer.

## Mapping your data into Zoho CRM

*The longest section — because field mapping is where almost every Zoho CRM migration that fails actually breaks.*

Mapping is where every migration earns its scars. Schema decisions in your mapping spreadsheet determine whether reports work on day two, whether Blueprint fires on day five, and whether sales trusts the data on day thirty.

Work Module by Module in import order: Users first, then Accounts (so Contacts and Deals can associate), then Contacts, then Deals, then Activities, then Custom Modules. The Data Migration wizard enforces this implicitly with a source preset; through the Import wizard, you enforce it by file order[26](https://flitstack.ai/migrations/crm/zoho-crm#source-26).

### Leads vs Contacts vs Accounts

Zoho splits unqualified prospects (Leads) from qualified people (Contacts associated with Accounts). On migration, decide up front which source records become Leads and which become Contacts — a HubSpot Contact with a Lifecycle Stage of Lead is usually a Zoho Lead; a HubSpot Contact with Customer is usually a Zoho Contact with a populated Account Lookup.

The wizard does not split for you. Once a Lead is converted to Contact + Account + Deal in Zoho, the original Lead row is closed, not deleted.

| Source                      | Destination                                        | Note                                                                                                                               |
| --------------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| email                       | Email (duplicate check field)                      | Lowercased pre-import; mark as duplicate check field for upsert                                                                    |
| first\_name / last\_name    | First Name / Last Name                             | Last Name is mandatory in Contacts and Leads[10](https://flitstack.ai/migrations/crm/zoho-crm#source-10)                           |
| phone                       | Phone / Mobile                                     | Normalise to E.164; Zoho does not enforce a phone format                                                                           |
| owner / account\_owner      | Record Owner                                       | Map by Zoho user email; unresolved owners fall back to the importing user                                                          |
| account / company           | Account Name (Lookup)                              | Import Accounts first; populate Lookup by Account Name or Account ID                                                               |
| created\_at                 | Custom Date-Time field (e.g., Legacy Created Date) | Created Time on Contacts is system-managed and cannot be overwritten[110](https://flitstack.ai/migrations/crm/zoho-crm#source-110) |
| source / utm\_source        | Lead Source picklist                               | Reference value must exist on the destination picklist[22](https://flitstack.ai/migrations/crm/zoho-crm#source-22)                 |
| external system primary key | External ID field                                  | Use this for upsert matching by external identifier[51](https://flitstack.ai/migrations/crm/zoho-crm#source-51)                    |

### Accounts

| Source           | Destination                  | Note                                                      |
| ---------------- | ---------------------------- | --------------------------------------------------------- |
| company\_name    | Account Name                 | Mandatory; mark as duplicate check field to enable upsert |
| website / domain | Website                      | Free text; Zoho does not strip http(s) or www on match    |
| industry         | Industry                     | Picklist; map source labels to existing Zoho values       |
| annual\_revenue  | Annual Revenue               | Currency field; respects org base currency setup          |
| parent account   | Parent Account (self-Lookup) | Import parents first; populate Lookup in a second pass    |
| territory        | Territory (Enterprise+)      | Territory hierarchy must exist before assignment          |

### Deals, Layouts, Pipelines and Stages

Recreate every Layout, Pipeline and Stage in Zoho before importing Deals. Zoho's Multiple Sales Pipelines feature couples three things: a Deal belongs to a Layout, the Layout owns one or more Pipelines, and each Pipeline owns its own ordered Stages[152](https://flitstack.ai/migrations/crm/zoho-crm#source-152).

The import wizard checks the triple on every row and skips rows on either a Layout-Pipeline mismatch (the Pipeline does not belong to the chosen Layout) or a Pipeline-Stage mismatch (the Stage is not part of the chosen Pipeline)[152](https://flitstack.ai/migrations/crm/zoho-crm#source-152). Skipped rows surface in Import History with the reason; the wizard does not stop, it just leaves them out.

If you are consolidating multiple source pipelines, the cleanest approach is to keep them as separate Pipelines on a single Layout for at least 90 days post-migration, then merge once reporting has stabilised. Stage Duration history does not migrate natively — Zoho only records stage duration when a Deal exits a stage, so historical durations must be carried in custom Days in \[Stage] numeric fields.

| Source                         | Destination           | Note                                                                                                                       |
| ------------------------------ | --------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| deal\_name / opportunity\_name | Deal Name             | Mandatory                                                                                                                  |
| pipeline                       | Pipeline              | Mandatory when multi-pipeline; must belong to chosen Layout[152](https://flitstack.ai/migrations/crm/zoho-crm#source-152)  |
| stage                          | Stage                 | Must be a Stage on the chosen Pipeline — skipped on mismatch[152](https://flitstack.ai/migrations/crm/zoho-crm#source-152) |
| amount                         | Amount                | Currency; respects org base currency and per-deal currency override                                                        |
| close\_date                    | Closing Date          | Mandatory; format must match org locale date format[22](https://flitstack.ai/migrations/crm/zoho-crm#source-22)            |
| owner                          | Deal Owner            | Map by Zoho user email; controls forecasting territory                                                                     |
| primary\_contact               | Contact Name (Lookup) | Import Contacts first; Lookup populated by ID or name                                                                      |
| account                        | Account Name (Lookup) | Mandatory in standard config; populated by Account Name or ID                                                              |

### Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Zoho's custom-field count limit is edition-tiered, with Standard at the lowest cap and Ultimate at the highest — bringing dead fields across burns the budget you will need for legitimate new requirements[62](https://flitstack.ai/migrations/crm/zoho-crm#source-62). Migrate only the fields used by an active process or report in the last 12 months.

For picklist fields whose source values do not match the destination, either: (1) extend the destination picklist with the missing values through Setup → Customization → Modules and Fields, (2) collapse adjacent values during transform, or (3) introduce a parallel custom picklist that holds the legacy value verbatim.

Formula fields do not import as data — Zoho recomputes them on-platform from the formula expression, so the source formula logic must be rebuilt in Zoho's formula syntax (Abs, Ceil, Floor, If, Concat, etc.) under a 5,000-character expression limit[65](https://flitstack.ai/migrations/crm/zoho-crm#source-65).

### Historical activities — Tasks, Calls, Meetings, Notes

Zoho stores Tasks, Calls and Meetings as their own Modules, related to the parent Lead, Contact, Account or Deal through a Related-To Lookup. On import, you build a multi-file load: first the parent records, then a separate activity file per type that carries the parent Record ID or unique identifier in the What ID / Who ID / Related To column.

The activity's Activity Date / Due Date / Start Time fields accept the original timestamp from the source — those are user-editable, unlike Created Time[82](https://flitstack.ai/migrations/crm/zoho-crm#source-82) [90](https://flitstack.ai/migrations/crm/zoho-crm#source-90).

Notes import via a dedicated file mapped to the Notes scope with a parent-Module reference and a parent Record ID. The Note title and content fields support rich text as of mid-2025[83](https://flitstack.ai/migrations/crm/zoho-crm#source-83), so HTML-flavoured note bodies can be brought across with a sensible amount of formatting preservation.

Historical emails are the hardest piece: there is no native bulk-email-import wizard, and practitioners typically use third-party services or build a custom Deluge function to attach historical messages per record[86](https://flitstack.ai/migrations/crm/zoho-crm#source-86).

### Files and attachments

Attachments do not import in the CSV flow. The supported path is per-record attachment, associating a binary with the parent record. The per-record attachment cap is 100 MB total across all files, with individual file size capped at 10 MB per file via attachment[91](https://flitstack.ai/migrations/crm/zoho-crm#source-91). Email-template attachments cap at 10 files totalling 3 MB[91](https://flitstack.ai/migrations/crm/zoho-crm#source-91).

File storage itself is now powered by Zoho WorkDrive on new orgs, with edition-tied storage allowances that you can extend by paying for additional WorkDrive capacity[100](https://flitstack.ai/migrations/crm/zoho-crm#source-100).

For large attachment estates (hundreds of GB), the pattern most teams adopt is: keep originals in S3, Google Drive or WorkDrive, store a deep link in a custom URL field on the Zoho record, and only inline-upload the most recent or most-referenced subset. The Reddit thread on the historical 4 GB attachment cap is a forcing function for this design[99](https://flitstack.ai/migrations/crm/zoho-crm#source-99).

### Audit trail, ownership and original timestamps

Zoho's standard Created Time and Modified Time fields are system-managed on most Modules and cannot be overwritten on import — they stamp to the moment the row was processed[110](https://flitstack.ai/migrations/crm/zoho-crm#source-110) [102](https://flitstack.ai/migrations/crm/zoho-crm#source-102). To preserve the original audit trail, create custom Date-Time fields Legacy Created Date and Legacy Modified Date on every Module and populate from the source export, then rewrite historical reports to filter on the legacy fields.

Record ownership during import works through a Field Mapping column on Owner — Zoho resolves the value against existing user email or user ID; rows whose owner cannot be resolved silently fall back to the importing user. Pre-provisioning all users and adding their emails to the source export's Owner column is the only reliable defence.

Account-level Audit Log captures Add, Update and Delete actions on records, plus configuration changes to Workflows, Profiles and Layouts. Administrator and CEO roles access the full log; other users see only own and sub-ordinates' actions[128](https://flitstack.ai/migrations/crm/zoho-crm#source-128). Audit log export covers up to the last three years by default[129](https://flitstack.ai/migrations/crm/zoho-crm#source-129).

### CRM-specific: deal stage history, Blueprint, scoring, Deluge

Deal stage history does not migrate. Zoho captures stage duration only when a Deal exits a stage, which means historical Days in Stage and stage-entry timestamps must be carried in custom Date-Time fields per stage (Stage 1 Entered, Stage 2 Entered, etc.) and back-filled from the source export.

Blueprint state machines do not import. Recreate the source's process gates as Blueprint transitions in Setup → Process Management → Blueprint, mapping the source's stage-permission rules to Blueprint Transition Settings. The same applies to Scoring Rules, Assignment Rules and Workflow Rules — rebuild from documentation rather than trying to migrate accumulated outputs.

Email and calendar sync (Zoho Mail, Gmail, Outlook) is set up per user under Settings → Channels → Email and Calendar Sync in `calendar.zoho.com` [151](https://flitstack.ai/migrations/crm/zoho-crm#source-151) after users are provisioned. Do not enable it during the import window or you will get a flood of duplicate emails as the connector backfills against the same contacts you are loading.

Deluge custom functions are the in-platform scripting layer — they do not import, but they are the right place to write the post-migration glue logic (de-dup loops, batch-tagging, legacy-ID lookups) that pure import flows cannot express.

## The pitfalls that derail Zoho CRM migrations

*Specific failure modes — ranked by impact, each tied to the exact Zoho mechanism that breaks.*

**high Layout-Pipeline-Stage mismatch silently skips Deal rows**

Zoho's Multiple Pipelines model couples three settings: a Deal belongs to a Layout, the Layout owns Pipelines, and each Pipeline owns Stages[152](https://flitstack.ai/migrations/crm/zoho-crm#source-152). The import wizard validates the triple per row and skips rows on any mismatch — Layout-Pipeline mismatch or Pipeline-Stage mismatch — without aborting the load. Skipped rows surface in Import History after the fact. Build the mapping table source-stage → Layout + Pipeline + Stage explicitly and validate against the wizard's sample step before committing the full file.

**high Created Time and Modified Time stamp to import day**

Standard Created Time and Modified Time on most Modules are system-managed and cannot be overwritten during import[102](https://flitstack.ai/migrations/crm/zoho-crm#source-102) [110](https://flitstack.ai/migrations/crm/zoho-crm#source-110). Teams discover this on day two when reports filtered by Created Date return everything stamped to the import date. The mitigation is to create custom Date-Time fields Legacy Created Date and Legacy Modified Date on every Module, populate them from the source export, and rewrite all historical-period reports to use the legacy fields rather than the system fields.

**high Edition-tier storage and feature ceiling discovered mid-migration**

Zoho's record-storage caps are edition-tiered — Free 5,000 records / 10 MB, Standard 100,000 / 200 MB, Professional 10 GB / 5 million records, Enterprise 10–15 GB / 5–7.5 million records, Ultimate up to 30 GB / 15 million[37](https://flitstack.ai/migrations/crm/zoho-crm#source-37). Custom Modules, Sandboxes, Multi-Select Lookups and Multiple Pipelines are gated to Enterprise and above. Teams that buy Standard for low monthly cost discover mid-import that historical activities push past 100,000 records and the load halts. Pick the edition against your full migrated volume, not your live working set.

**high Picklist value rejected because the destination drop-down does not list it**

Zoho's picklists store a display value and a reference value that can differ[67](https://flitstack.ai/migrations/crm/zoho-crm#source-67). The Data Migration wizard rejects rows whose picklist value does not exist on the destination drop-down, returning a per-row error in Import History[22](https://flitstack.ai/migrations/crm/zoho-crm#source-22). Extend the destination picklist with every value the source contains before import — through the UI under Setup → Customization → Modules and Fields — or collapse adjacent source values during transform.

**high Owner falls back to import user on unresolved email**

Zoho resolves the Record Owner column against existing user email or user ID at import time; rows whose owner email is not yet a provisioned Zoho user silently import with the import-running user as owner, not the intended owner. The downstream effect breaks owner-based workflows, assignment rules and forecasting territories. Pre-provision every user (including deactivated ones from the source if you need their historical attribution) before the first import row goes in.

**medium Character encoding corruption on non-UTF-8 CSV**

Zoho's troubleshooting documentation explicitly calls out character encoding as the most common import failure mode — non-UTF-8 CSVs produce garbled accented characters, mojibake on Asian-language records, or full row rejection[113](https://flitstack.ai/migrations/crm/zoho-crm#source-113). Excel saves CSVs as Windows-1252 by default on Western locales and as Shift-JIS or GBK on Asian locales. Always export source data as UTF-8 explicitly (in Excel: File → Save As → CSV UTF-8), and verify a sample row through a hex viewer before bulk upload.

**medium Attachment 100 MB per-record cap silently truncates large estates**

Zoho caps total attachments per record at 100 MB and per individual attachment at 10 MB[91](https://flitstack.ai/migrations/crm/zoho-crm#source-91). Migrations from Salesforce or HubSpot, where attachment caps were looser, discover this when contracts, signed PDFs and call recordings get rejected. The mitigation is to migrate only the most recent or most-referenced subset inline and store the rest in S3, Google Drive or Zoho WorkDrive with a deep-link custom URL field on the parent record[100](https://flitstack.ai/migrations/crm/zoho-crm#source-100).

**low Regional data centre cannot be flipped after account creation**

Zoho operates regional data centres for US, EU, India, Australia, China and Japan, and accounts are pinned to a region at signup. There is no self-serve cross-region migration — Zoho Support runs it as a ticketed operation[16](https://flitstack.ai/migrations/crm/zoho-crm#source-16). If your migration is into an account already created in the wrong region, plan for the regional migration first, or you will move all your records twice. Always check the org's data centre under Setup → Company Settings before the first row goes in.

## Validation and cutover

*What to verify after the import job, in what order — and how to fail safely when something is wrong.*

Validation is the bridge between the import finishing and users being allowed in. The pattern that works on Zoho is three stages: a Sandbox dry-run on 5–10 percent of records with stakeholder spot-checks; a production load with real-time monitoring of Import History per Module; and a 30-day post-migration data-quality audit. Department reps verifying their own records is the most reliable signal — they know what right looks like.

Build a reconciliation queries spreadsheet that compares source and destination on each count. Anything outside a 0.5 percent variance gets investigated before users get login access.

- Total records per Module imported vs source — Import History under Setup → Data Administration → Import History lists added, updated and skipped counts per file for 60 days post-import[122](https://flitstack.ai/migrations/crm/zoho-crm#source-122).
- Total Deals per Pipeline per Stage vs source, plus sum of Amount per Pipeline — a non-trivial currency variance usually signals a stage-mapping error or a number-format drop during transform.
- Total activities per Module (Tasks, Calls, Meetings) imported vs source — and a date-bucketed comparison to confirm Activity Date and Start Time round-tripped.
- Lookup integrity per Module pair — count Contacts with a populated Account Lookup and compare against the source-derived expected count.
- Owner distribution — group by Record Owner and confirm no Module landed with the import-running user owning the majority of records (the silent fallback signature).
- Duplicate-check field integrity — count distinct Email on Contacts and Leads, distinct Account Name on Accounts; any duplicates indicate the dedup transform missed cases that Zoho's import then merged.

On top of reconciliation, run a manual spot-check protocol: pick 30 random records across Modules and verify each field against the source UI. Trace the full Lookup graph on five high-value Deals — Contact, Account, related Tasks, Calls, Notes. If a discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import by Record ID or External ID.

Zoho ships an Undo Import option directly inside Import History — entries from the last 60 days expose an Undo action that reverses the import for that file[122](https://flitstack.ai/migrations/crm/zoho-crm#source-122). The catch is that detailed undo metadata (added / updated / skipped lists) is retained for only 7 days after the import[122](https://flitstack.ai/migrations/crm/zoho-crm#source-122), so any rollback decision needs to happen inside that window.

After 7 days, your fallback is the same as on any CRM: export everything before the import, stamp every imported row with an Import Batch ID custom field, and bulk-delete by that batch ID if catastrophe strikes.

Recycle Bin and Restore sit alongside Undo Import: deleted records can be restored individually or in bulk for 60 days before permanent purge. Audit Log under Setup → Security Control → Audit Log tracks every Add, Update, Delete action and is exportable for up to three years of history[129](https://flitstack.ai/migrations/crm/zoho-crm#source-129).

Cutover sequencing: (1) source goes read-only; (2) final delta export captures everything that changed during the test-import window; (3) delta is imported via the same Data Migration flow; (4) reconciliation runs against the delta; (5) users get login access and a 48-hour hyper-care window; (6) source decommission is scheduled for 30 to 90 days out, never the same day.

## Migration partners and tools

*Authorized Zoho Partners, iPaaS vendors, specialist migration shops — what each is good for and how to choose.*

The Zoho Partner Program credentials Authorized, Advanced and Premium Partners through certifications, customer count and revenue tiers, and exposes them through the Find a Zoho Partner directory at zoho.com/partners[141](https://flitstack.ai/migrations/crm/zoho-crm#source-141). For Zoho CRM migrations specifically, partners with explicit Salesforce-to-Zoho, HubSpot-to-Zoho or ACT!-to-Zoho practices tend to ship cleaner than generalist implementation shops.

Zoho also runs an in-house migration assistance team at migration\@zohocrm.com that handles complex Salesforce or Pipedrive migrations directly, often at no incremental fee on Enterprise or Ultimate contracts[60](https://flitstack.ai/migrations/crm/zoho-crm#source-60). The trade-off is throughput — the in-house team is best for clean source schemas and lighter customisation; deeper Custom Module work, Blueprint rebuilds and historical activity preservation tend to land with the certified-partner channel.

On the ETL and iPaaS side, Fivetran, Airbyte, Stitch, Workato, Make and Integrate.io all sit alongside Zoho CRM migrations. Their role is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts picklist values and resolves owner emails, and the ongoing-sync layer that takes over once the one-time migration is complete.

Make and Workato are common picks where the migration is bundled with workflow rebuilds; Fivetran and Airbyte are more common where the warehouse is the long-term source of truth.

Managed-migration cost ranges vary widely. A clean Pipedrive-to-Zoho or HubSpot-to-Zoho move of under 25,000 records with no historical activities and standard Modules only often lands in the $2,500–$8,000 range with a setup fee plus per-Module pricing. A Salesforce-to-Zoho project with Custom Modules, Blueprint rebuilds, historical activities and integration re-pointing typically runs $20,000–$100,000, with the upper end driven by record count, custom-field complexity, historical-data depth, and the number of integrations that need rebuilding rather than re-pointed.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Zoho CRM migrations and handles the Layout-Pipeline-Stage sequencing, picklist-value alignment, External ID upsert wiring, Created-Time-to-Legacy-Date custom-field pattern, owner-resolution pre-checks, and the reconciliation and spot-check validation described in Sections 5 and 7 of this guide. Pricing is fixed-fee based on record count and source platform, with separate line items for Custom Modules, historical activity depth and Blueprint rebuilds so the scope is transparent before signature.

This is one of several legitimate paths — the right choice depends on whether the team wants a Premium Partner, Zoho's in-house migration team, an iPaaS-first approach, or a specialist vendor. \[Explore FlitStack →]\(/contact)

In this guide

## Zoho CRM migration checklist

Sequenced punch list for moving CRM data into Zoho CRM across Modules, Layouts, Pipelines, and Stages — covering export, transform, sandbox test, cutover, and validation. Typical timeline: 4–12 weeks.

0\. Decide & Plan 9 tasks

- **Document the in-scope Zoho CRM Modules.** List every standard Module you will load (Leads, Accounts, Contacts, Deals, Tasks, Calls, Meetings, Notes, Products, Quotes, Sales Orders, Invoices, Cases, Campaigns, Vendors, Price Books) and every custom Module you will create. Anything not on this list is out of scope.*If skipped: Late-discovered Modules force schema changes mid-migration and trigger re-runs of upstream transform jobs.*
- **Pick the Zoho CRM edition before any provisioning.** Edition gates storage ceiling (Free 5k records / 10 MB, Standard 100k records / 200 MB, Professional 10 GB, Enterprise 10–15 GB, Ultimate up to 30 GB for >200 users), Sandbox availability (Enterprise and above), Multi-Select Lookup fields (Enterprise and above), and custom field counts per Module.*If skipped: Choosing a lower edition than the data requires blocks Sandbox testing and many-to-many relationships entirely.*
- **Define the historical-data scope window.** Decide how many years of closed Deals, completed Tasks, logged Calls, sent Emails, and Notes are in scope. Decide whether Attachments are in scope or stay in the legacy archive.
- **Decide the audit-timestamp strategy.** Zoho CRM stamps Created Time and Modified Time at the moment of insert and does not let bulk imports override them. Pick one strategy and document it: capture source CreatedDate in a custom date field per Module, or accept that Created Time equals migration date.*If skipped: Without a decision, reports and activity timelines look like every record was created on cutover day.*
- **Document data-residency and compliance requirements.** Zoho operates regional data centers (US, EU, IN, AU, JP, CN, CA). Confirm which DC the org must live in, GDPR enablement for Leads/Contacts/Vendors, and whether SOC 2 + HIPAA scope is required.*If skipped: Provisioning in the wrong DC cannot be reversed by moving data later — it requires a fresh org and a second migration.*
- **Name a single accountable migration owner (DRI).** One person signs off on Phase 0, Phase 4 sandbox results, and Phase 6 reconciliation. No committee.
- **Set the cutover date, time, and source-system freeze window.** Pick a low-volume window. Confirm with sales, support, and finance that no campaigns, billing runs, or quarter-end closes overlap.
- **Write the success criteria.** Concrete pass/fail statements: total record count per Module matches source within 0.1 percent, total open pipeline value matches source within $1, every active user can log in and see their assigned records.*If skipped: Without written criteria, the migration drags on indefinitely because nobody can declare it done.*
- **List explicitly out-of-scope items.** Examples: source-system custom dashboards (rebuild manually post-cutover), source-system Workflow Rules (rebuild in Zoho), deleted records in the legacy recycle bin, system-audit logs older than 12 months.

1\. Pre-Migration Prep 25 tasks

- **Export current record counts per source object as a baseline.** Capture exact counts for every object you will load. This is the reference number for Phase 6 reconciliation.*If skipped: Without a baseline, you cannot prove what was lost in transit.*
- **Run deduplication on source Contacts using email as the match key.** Zoho CRM uses unique fields to block duplicate inserts; resolving duplicates upstream is faster than untangling them after load.*If skipped: Duplicate Contacts post-load split activity history across two records and break reporting.*
- **Run deduplication on source Accounts using domain as the match key.** Pick one canonical Account per company; merge child Contacts and Deals onto it.
- **Standardize email casing and trim whitespace across all email fields.** Convert to lowercase. Strip leading/trailing spaces. Email is a common upsert key in Zoho CRM.
- **Normalize phone numbers to E.164 with country code.** Pick one format and apply it uniformly before export.
- **Identify and fix records missing required Zoho CRM fields.** Last Name is mandatory on Leads and Contacts. Subject is mandatory on Tasks. Account Name is mandatory on Accounts. Deal Name, Closing Date, Stage, and Pipeline are mandatory on Deals.*If skipped: Rows with empty required fields are silently skipped by the importer and do not appear in the destination.*
- **Inventory custom fields on the source system.** Export name, type, picklist values, validation rules, and whether the field is required. This becomes the source side of the Phase 3 mapping spreadsheet.
- **Document source pipeline names and stage values per pipeline.** Zoho CRM models Deals as a triple: Layout + Pipeline + Stage. You need the full source list to plan the destination triples.*If skipped: Missing source stages cause Deal rows to be skipped with a pipeline-stage-mismatch error during import.*
- **Provision the production Zoho CRM org in the chosen data center.** Confirm the DC URL (.com, .eu, .in, .com.au, .jp, .com.cn, .ca) matches the Phase 0 residency decision.
- **Provision a Sandbox org from production.** Sandbox is available on Enterprise and above. Use Configuration + Sample Data type so Layouts, Pipelines, Profiles, and Roles import alongside test records.*If skipped: Skipping Sandbox forces every test to happen in production where errors are visible to end users.*
- **Create all destination Users with email matching source-system user emails.** Matching emails lets you assign record ownership during Phase 5 load via the Owner field by email lookup.
- **Build the Role hierarchy and Profiles before any import.** Roles control record-sharing scope; Profiles control field-level permissions. Records load against whatever Profile rules exist at insert time.
- **Set org-level Currency, Time Zone, Fiscal Year, and Date Format.** These affect how imported timestamps and currency values are parsed. Lock them before any sandbox test.*If skipped: Changing time zone after import does not retroactively re-stamp records and creates an off-by-N-hours bug on every datetime field.*
- **Create custom Modules required by the source schema.** Use Setup > Customization > Modules and Fields. Decide naming, primary field, and singular/plural labels now — these are hard to change later.
- **Create every custom field on every Module before any import.** Zoho CRM cannot create destination fields on the fly during bulk import. Importing into a field that does not exist drops the column silently.*If skipped: Silent column drops are the single most common cause of Phase 6 reconciliation gaps.*
- **Create every picklist value that any record will use.** Use the Setup UI under Modules and Fields. Capture both the display label and the reference value — these can differ and Bulk Write keys off reference value.*If skipped: Unknown picklist values are rejected row-by-row and the row is skipped.*
- **Build the Layouts, Pipelines, and Stages for the Deals Module.** Each Layout is bound to one or more Pipelines. Each Pipeline contains an ordered list of Stages. A Deal row must reference a triple (Layout, Pipeline, Stage) that exists.*If skipped: Importing Deals without the matching triple in place causes every Deal in that pipeline to be skipped.*
- **Create an External ID custom field on every Module you will upsert into.** External ID is a designated field type in Zoho CRM (Setup > Customization > Modules and Fields > New Custom Field > External). Populate it with the source-system primary key so reruns are idempotent.*If skipped: Without External ID, re-running a failed import duplicates every record.*
- **Configure field-level permissions per Profile.** Hide or mark read-only any field that should not be editable by lower-permission Profiles.
- **Pause all Workflow Rules, Assignment Rules, and Blueprint state transitions.** Inserts during bulk load otherwise trigger workflows that fire welcome emails, recalculate scores, and move Deals into the wrong Blueprint state.*If skipped: An active welcome-email workflow during a 50,000-Contact load emails every contact at cutover.*
- **Disable email-notification recipients on Modules being imported.** Turn off Notify Owner and any subscription-based email triggers during the import window.
- **Set Assignment Rules for record ownership assignment, or plan to use email-based field mapping.** Two options exist at import time: Assignment Rule based on conditions, or Field Mapping where ownership is supplied as the user's login email in the CSV.
- **Announce the source-system freeze window to all end users.** Pin the announcement in chat and email it at T-7 days, T-1 day, and T-1 hour.
- **Schedule training sessions on Zoho CRM basics segmented by role.** Sales users, marketing users, and admins need different content. Aim for sessions within 5 business days of cutover.
- **Designate first-responder support contacts for the 48 hours post-cutover.** At least one Zoho CRM admin on call. Name them publicly.

2\. Source Export 14 tasks

- **Export Leads as CSV with all standard and custom fields.** Include source primary key as a column so it can be loaded into the destination External ID field.
- **Export Accounts (Companies) as CSV with all fields plus parent-account ID.**
- **Export Contacts as CSV with all fields plus the Account ID lookup.** *If skipped: Exporting Contacts without the Account foreign key forces a manual re-association later, which is error-prone at volume.*
- **Export Deals as CSV with Layout, Pipeline, Stage, Closing Date, Amount, and Account/Contact lookups.** Include any deal-stage-history fields the source surfaces.
- **Export Tasks, Calls, and Meetings as three separate CSVs.** Each has a different schema in Zoho CRM. Include the parent record ID (What ID / Who ID equivalents).
- **Export Notes as a CSV linked to their parent record IDs.** Note content can include line breaks and quotes; ensure the exporter quotes correctly.
- **Export Email message history with parent record associations.** Zoho CRM has no native bulk import for past emails into the email-history timeline. Plan to load them into a custom Email Log Module or attach as Notes with an Email Date custom field.*If skipped: Treating email history as a standard Note loses the threading and sender metadata.*
- **Export attachment metadata: file name, size, MIME type, and parent record ID.** Separate file from metadata; both are required at re-upload time.
- **Download attachment binaries to a staging bucket.** Per-record attachment cap in Zoho CRM is 100 MB total, with per-file cap of 20 MB. Flag any oversize file for the Phase 3 decision.*If skipped: Files larger than the per-file cap will not load and silently leave records unlinked.*
- **Export the full User list with email, role, profile, and active/inactive flag.**
- **Export source Pipeline and Stage definitions as a reference document.** This becomes the source side of the Layout-Pipeline-Stage triple mapping in Phase 3.
- **Export Products, Price Books, Quotes, Sales Orders, and Invoices if in scope.**
- **Capture screenshots of source dashboards, reports, and Workflow Rules.** These do not migrate. They will be rebuilt manually in Phase 7.
- **Record the exact UTC timestamp of each export.** This is the baseline for the Phase 5 delta export.

3\. Transform & Map 29 tasks

- **Build a master mapping spreadsheet covering every source field.** Columns: Source Module, Source Field, Source Type, Destination Module, Destination Field, Destination Type, Transformation Rule, Required (Y/N), Upsert Key (Y/N), Notes.*If skipped: Without a single mapping document, transform logic drifts between engineers and reconciliation finger-pointing becomes unavoidable.*
- **Confirm field-type compatibility row by row.** Zoho CRM does not let you change field type after creation. A source Text field cannot be loaded into a destination Integer field; either change the destination field type now or transform the source value.
- **Decide upsert key per Module.** Typical pattern: email on Leads/Contacts; source primary key in External ID on every other Module. Document the choice on the mapping sheet.
- **Decide what to do with source fields that have no destination equivalent.** Three options per field: drop, create a custom field, or concatenate into Description/Notes.
- **Resolve every picklist value mismatch.** Source 'Won-Closed' → Destination 'Closed Won'. Build a value-translation lookup that maps every distinct source value to a valid destination value before export. Watch the distinction between picklist reference value (used by bulk loads) and display label (shown in UI).*If skipped: Mismatched picklist values cause row-level skips at insert time, with the row reported in the import error log but not loaded.*
- **Map Profiles and Roles between source and destination.** Source 'Sales Rep' → Destination 'Sales Manager' Profile, for example. This drives the Owner assignment in Phase 5.
- **Convert all dates and datetimes to ISO-8601.** Bulk Write expects yyyy-MM-dd for Date and yyyy-MM-ddTHH:mm:ss±hh:mm for DateTime. Zoho CRM rejects ambiguous formats like DD/MM/YYYY.*If skipped: Date-format mismatches cause the entire CSV to be rejected at the validation step.*
- **Re-encode every CSV as UTF-8.** Zoho CRM importer requires UTF-8. Files exported from older systems often land as Windows-1252 or UTF-16; verify with a hex check on the byte-order mark.*If skipped: Non-UTF-8 files cause accented characters to corrupt to mojibake (e.g., 'café' → 'café').*
- **Normalize currency values to the org default currency or include the per-record currency code.** Zoho CRM supports multi-currency on Enterprise+. For single-currency orgs, pre-convert at the historical FX rate.
- **Truncate text fields that exceed Zoho CRM character limits.** Single-line Text fields cap at 255 characters; Multi-line Text caps at 32,000. Decide whether to truncate or split oversize source values into a paired Description field.*If skipped: Rows exceeding field width are skipped during Bulk Write.*
- **Escape commas, quotes, and newlines in long-text fields.** RFC 4180 quoting: wrap any field containing a comma or newline in double quotes and double any embedded double quotes.
- **Convert boolean source fields to Zoho CRM checkbox values.** Use 'true' / 'false' literals in the CSV; the importer rejects 1/0 in some columns.
- **Split combined Name fields into First Name and Last Name where the destination Module requires it.** Leads, Contacts, and Vendors store Last Name as the mandatory field.
- **Compress attachment archives into ZIP and pre-stage them by parent record ID.** Bulk attachment loads typically use a COQL + Attachments loop; staging by parent ID lets you script the loop deterministically.
- **Implement the historical-timestamp strategy chosen in Phase 0.** Zoho CRM does not let bulk imports override Created Time / Modified Time. Populate a 'Source Created Date' custom date field per Module instead, and use it for reporting.*If skipped: Reporting on Created Time will show every record dated to migration day, which destroys time-series trend analysis.*
- **Decide the Owner assignment strategy and encode it on every export row.** Option A: best-match by email against the Zoho User list. Option B: assign everything to a single 'Data Migration' user. Option C: use Assignment Rules. Pick one and apply uniformly.
- **Decide the attachment strategy.** Option A: re-upload binaries into each record via the Attachments path. Option B: store binaries in Zoho WorkDrive and link via a URL custom field. Option B preserves storage quota.*If skipped: Re-uploading 100 GB of attachments into a Professional org (10 GB cap) saturates storage and blocks new records.*
- **Resolve one-to-many parent/child relationships via standard lookup fields.** Account → Contacts uses the built-in Account Name lookup. Contact ID must be loaded after Account ID.
- **Resolve many-to-many relationships via Multi-Select Lookup fields.** Multi-Select Lookup is Enterprise+. On lower editions, create a junction custom Module with two lookups instead.*If skipped: Attempting to model many-to-many on Standard or Professional editions silently flattens to one-to-many and loses associations.*
- **Build the Layout-Pipeline-Stage triple mapping table.** For every distinct (source layout, source pipeline, source stage) combination, write the matching (destination Layout, destination Pipeline, destination Stage). This is the #1 source of Deal-import skips in Zoho CRM.*If skipped: Records are skipped on layout-pipeline mismatch (deal pipeline does not belong to selected layout) and pipeline-stage mismatch (stage does not belong to deal pipeline). Both errors live in import history.*
- **Verify every destination picklist's reference value, not just its display label.** Each picklist option carries a display\_value, reference\_value, and id. Bulk Write and upsert match against reference\_value. Pull the option list from the destination before encoding the transform.*If skipped: Loading the display label instead of the reference value causes every row to fail picklist validation.*
- **Encode lifecycle-stage transitions for Leads vs Contacts.** Decide which source records become Leads and which become Contacts post-conversion in Zoho. Build the rule (e.g., 'has a closed-won Deal' → Contact; otherwise Lead) and apply it during transform.
- **Plan Blueprint state placement for Deals.** If a Blueprint state machine governs Deals in production, every imported Deal lands in the state matching its Stage. Disable the Blueprint during import or pre-stage records to the initial state, then transition them after load.*If skipped: Active Blueprints reject Stage updates that violate transition rules, causing import partials.*
- **Recompute lead scoring instead of importing source scores.** Zoho CRM Scoring Rules apply on record events. Import a clean score of 0 and let rules re-derive, or import as a custom 'Migrated Score' field for historical reference.
- **Map Deal Close Date carefully across timezones.** Closing Date is a Date field, not DateTime. Confirm the source value was already in the org timezone before stripping the time component.
- **Decide how to represent source Deal-stage-history.** Zoho CRM auto-captures Stage History going forward but does not let you backfill it via Bulk Write. Either import the source stage history into a custom child Module, or accept that pre-migration stage history lives only in archived exports.*If skipped: Pipeline velocity reports for periods before cutover will be empty.*
- **Map source Cases / Tickets to the Cases Module if in scope.** Cases is a standard Zoho CRM Module. Map case status, priority, and parent Account/Contact like any other lookup-bearing object.
- **Translate source email-marketing opt-out flags to Email Opt Out.** Zoho CRM has a built-in Email Opt Out boolean on Leads and Contacts. Honor source unsubscribes before any campaign sync.*If skipped: Loading opted-out contacts as opted-in is a CAN-SPAM and GDPR violation.*
- **Identify Multi-Select Picklist fields and pre-split values with semicolons.** Bulk Write expects multi-select values as a semicolon-delimited string within a single CSV cell.

4\. Sandbox Test Migration 14 tasks

- **Load a 1–5 percent representative sample of every in-scope Module into the Sandbox.** Use the Data Migration wizard or Bulk Write depending on planned production path. Match the production method exactly.
- **Validate field-by-field on 10 random Sandbox records per Module.** Open each record in the UI and compare every field to the source export. Document any discrepancy.*If skipped: Sampling fewer than 10 records misses field-level drops that only surface on certain record subtypes.*
- **Test the Layout-Pipeline-Stage triple by loading Deals across every Pipeline.** Confirm every combination produces a loaded Deal, not a skip.*If skipped: An untested triple discovered in production blocks the entire Deal-load wave.*
- **Test picklist reference values against display labels.** Confirm the value lands in the right picklist option by inspecting the underlying reference value, not just the rendered UI label.
- **Test datetime timezone handling on at least 3 records.** Pick records with timestamps near midnight to surface off-by-one-day errors.
- **Test special-character handling: emoji, accents, quotes, newlines.** Pick at least 5 source records containing each.*If skipped: Character-encoding bugs are invisible until a user opens the record and sees mojibake.*
- **Test Multi-Select Lookup associations end to end.** Load both sides and the junction; confirm the related list shows the expected counts on each side.
- **Test Attachment upload on at least 25 records.** Verify file integrity (size matches source) and that the attachment appears in the related list.
- **Run a Bulk Write job at full volume against Sandbox where possible.** Bulk Write caps at 200,000 records per job and 5 concurrent jobs per org. Time the job end-to-end and extrapolate to production volume.*If skipped: A 'works on 5 percent' test does not surface throughput cliffs that only appear at 50,000+ records.*
- **Confirm the Phase 3 audit-trail strategy actually worked.** Spot-check the 'Source Created Date' custom field is populated on every record.
- **Have a domain expert from sales spot-check Deal records in Sandbox.** Real users find issues data engineers miss: missing notes, wrong stage names, lost Account associations.
- **Have a marketing user spot-check Lead and Contact records in Sandbox.** Validate email opt-out flags, campaign associations, and lead source values.
- **Capture timing for every Bulk Write job for production planning.** Job submit → completion times let you size the production cutover window realistically.
- **Get written sign-off on Sandbox results before scheduling production cutover.** Email or ticket; do not proceed on verbal approval.*If skipped: Verbal sign-offs evaporate when reconciliation surfaces an issue post-cutover.*

5\. Production Cutover 12 tasks

- **Confirm source-system freeze.** Inspect source-system audit logs to verify no record-modifying activity in the last hour.
- **Take the final delta export of every in-scope object.** Same exporter as Phase 2, same field set, new timestamp suffix on filenames.*If skipped: Skipping the delta loses every record created between Phase 2 export and cutover.*
- **Confirm Workflow Rules, Assignment Rules, and Blueprints are paused.** Spot-check the Setup UI. Inadvertent activation between Phase 1 and Phase 5 is a common cause of surprise side effects.*If skipped: An active welcome-email workflow at cutover sends thousands of accidental emails in minutes.*
- **Load Users first (or confirm Users were created in Phase 1).** Users must exist before any Owner field can resolve.
- **Load parent Modules before child Modules.** Order: Accounts → Contacts → Deals → Tasks/Calls/Meetings/Notes → Attachments → custom child Modules. Each layer references IDs created in the previous layer.*If skipped: Out-of-order loads leave lookup fields blank with no error and require a second pass to repair.*
- **Use upsert keyed off External ID for every load step that supports it.** The per-call upsert path accepts 100 records per batch; Bulk Write upsert handles up to 200,000 per job. Idempotent reruns will not duplicate records.*If skipped: Insert-only loads on partial failure create duplicate records on retry.*
- **Capture the Bulk Write job ID, row count, and error log for every load step.** Store these in a cutover run-book alongside timestamp and operator name.
- **Cross-check destination row counts against source row counts at each step.** Stop the cutover if any per-Module count differs by more than the agreed tolerance (typically 0.1 percent).*If skipped: Pushing through with an unexplained count delta makes Phase 6 reconciliation impossible.*
- **If any step fails, halt — diagnose — fix the transform — re-run idempotently.** Never push partial data through to the next step.
- **Re-enable Workflow Rules, Assignment Rules, and Blueprints after all loads complete.** Document the exact reactivation time in the run-book.
- **Run a Blueprint state-correction pass if required.** If Blueprints were disabled at load time, walk each Deal through the appropriate state transition via Deluge or manual UI action.
- **Snapshot the production org backup immediately after cutover completes.** Use Zoho CRM's Data Backup feature. This is your rollback point if Phase 6 surfaces a fatal issue.*If skipped: Without a clean post-load snapshot, partial rollback requires per-record manual cleanup.*

6\. Validate 20 tasks

- **Compare total record count per Module: source vs Zoho CRM.** Use COQL (CRM Object Query Language) to count destination rows. Investigate any delta beyond the agreed tolerance.*If skipped: Unexplained deltas typically trace to skipped picklist values, missing required fields, or layout-pipeline mismatches.*
- **Compare total open pipeline value between source and destination.** Sum Amount across open Deals (Stage != Closed Won / Closed Lost) and compare to the source sum.
- **Compare closed-won pipeline value over the last 12 months.** Catches Stage-mapping errors that move historical wins into the wrong stage.
- **Compare counts per Pipeline.** Iterate every Pipeline and compare source-stage counts to destination-stage counts.
- **Spot-check 25–50 randomly selected records field-by-field.** Pick records across Modules, owners, and stages. Open each in the UI and compare against the source export.
- **Verify all External ID values are populated.** Run a COQL query for null External ID. Any null breaks future incremental syncs.*If skipped: Null External IDs force every subsequent upsert to treat the record as new, creating duplicates.*
- **Verify a sample of Account → Contact associations.** Pick 20 random Accounts and confirm child Contact counts match source.
- **Verify Deal → Account and Deal → Contact lookups.** Sample 20 Deals; confirm both lookups resolve.
- **Verify Tasks, Calls, and Meetings attach to the correct parent record.** Open the parent record's related list and confirm activity counts match source.*If skipped: Orphaned activities sit in the global Activities view but never appear in a sales rep's record-level timeline.*
- **Verify Multi-Select Lookup junctions in both directions.** Pick a record from each side of every many-to-many relationship and confirm the related list.
- **Verify Attachment files open and download correctly.** Click 10 random Attachments per Module; confirm file integrity.
- **Confirm the 'Source Created Date' custom field is populated everywhere.** Run a COQL query: count of records where the custom date is null should equal zero.
- **Run a GDPR compliance check on Leads, Contacts, and Vendors.** Enable Compliance Settings if required; verify Data Privacy section appears on each record.
- **Export the Zoho CRM Audit Log for the cutover window.** Capture as SOC 2 evidence of who imported what when. Use the Initiate Export Audit Log option in the Setup UI.*If skipped: Audit logs are retained 3 years by default; pulling them now is cheap, retrieving them later may not be possible.*
- **Have 3–5 power users validate their day-to-day workflows in production.** Hands-on: log a Call, create a Deal, send an Email, close a Task. Document every snag.
- **Run reports from the source and from Zoho CRM side by side.** Pick the 5 reports the business actually uses. Confirm totals reconcile.
- **Validate Calendar sync if integrated with Zoho Mail / Google Calendar / Outlook.** Sync direction, conflict handling, and event-creation source can all surprise users.
- **Validate the Zoho CRM mobile app shows migrated data correctly.** Mobile uses different rendering paths and can surface field-permission bugs the web app hides.
- **Document every UAT issue with severity and owner.**
- **Get written sign-off from the migration sponsor.** Email or ticket with the success-criteria document attached and each criterion marked pass.*If skipped: Proceeding without sign-off leaves the project in a perpetual 'almost done' state.*

7\. Post-Migration Cleanup 14 tasks

- **Communicate go-live to all end users.** Login URL, who-to-ask-for-help, link to the role-specific training recording.
- **Run live training sessions segmented by role.** Sales reps, sales managers, marketing, support, and admins each get a 30–60 minute focused session.
- **Set the source system to read-only and announce the date.** Read-only prevents accidental new writes that would never reach Zoho.
- **Rebuild Workflow Rules in Zoho CRM.** Workflow Rules do not migrate from any source system. Use the Phase 2 screenshots as the spec.
- **Rebuild Assignment Rules and territory definitions.**
- **Rebuild Blueprint state machines for any process that needs them.**
- **Rebuild dashboards and standard reports.** Reports do not migrate. Recreate the most-used 5–10 first, then expand.
- **Rebuild any Deluge custom functions or scheduled jobs from the source automations.** Source-system scripts (Apex, custom code) have no direct port; rewrite in Deluge.
- **Re-enable integrations: email sync, calendar sync, marketing automation, BI tools.** Run each integration in dry-run mode first to confirm no duplicates are created against migrated records.*If skipped: Marketing-automation re-sync without External-ID checks duplicates every contact.*
- **Configure the Zoho CRM Data Backup schedule.** Set automatic backups per the retention policy decided in Phase 0.
- **Schedule a 30-day post-migration retrospective.** Capture what went well, what didn't, and update the migration runbook for the next org.
- **Document the source-system decommission date.** Typical pattern: 90 days read-only, then archive the final export to long-term storage and cancel the subscription.
- **Archive all source-system exports and Zoho CRM migration logs to long-term storage.** Retain per the legal-hold and retention policies from Phase 0.*If skipped: Discarding exports too early eliminates forensic options if a data-quality issue surfaces months later.*
- **Close the migration project formally.** Final status report, lessons-learned doc, project closure.

Questions, answered

## Migrating to Zoho CRM: questions

How long does migration to Zoho CRM take?

A small-business migration with under 5,000 records, standard Modules and no Custom Modules runs one to two business days end-to-end using the Data Migration wizard. A mid-market project with Custom Modules, Blueprint rebuilds and historical activities runs two to four weeks of elapsed time, including Sandbox dry-runs, validation, training, and a 48-hour hyper-care window.

Can I migrate from Salesforce to Zoho CRM?

Yes — Salesforce is the most common Zoho CRM migration source, with a dedicated preset in the Data Migration wizard. Standard Modules map cleanly (Leads, Accounts, Contacts, Opportunities to Deals), but Apex code, Flows and Process Builder do not transfer and must be rebuilt as Workflows, Blueprint transitions and Deluge functions.

Can I migrate from HubSpot to Zoho CRM?

Yes, and HubSpot-to-Zoho is supported by a direct connector-driven transfer in the Data Migration wizard. The object map is Contacts to Contacts, Companies to Accounts, Deals to Deals, Tickets to Cases. Lifecycle Stage requires manual conversion to Lead Status and Account Type picklists during the transform pass.

Does Zoho CRM preserve original timestamps on import?

Partially. Activity Date, Due Date and Start Time on Tasks, Calls and Meetings can be backdated and show on the timeline correctly. But Created Time and Modified Time on most Modules are system-managed and stamp to the import date. Use custom Legacy Created Date fields to preserve the original audit trail.

Can I migrate Custom Modules to Zoho CRM?

Yes, but Custom Modules require an Enterprise or Ultimate subscription. The schema, Layouts, fields and Lookups for each Custom Module must exist before any record of that type can be imported. Custom Module records are loaded via the native Import wizard or the Data Migration wizard.

What happens to deal stage history and pipeline transitions during migration?

Recreate every Layout, Pipeline and Stage in Zoho before importing Deals — rows whose Layout-Pipeline-Stage triple does not match are skipped. Stage transition history does not auto-preserve because Zoho only records stage duration on exit; export per-stage entry timestamps and store them in custom Date-Time fields.

Is there an undo or rollback for Zoho CRM imports?

Yes — Import History under Setup, Data Administration exposes an Undo action on entries from the last 60 days, though detailed added, updated and skipped lists are retained for only 7 days after import. Beyond that window, stamp every imported row with a custom Import Batch ID field instead.

### [Zoho CRM implementation](https://flitstack.ai/services/zoho-crm-implementation)

[Set up Zoho CRM (pipelines, properties, automation, permissions) and migrate into it as one engagement.](https://flitstack.ai/services/zoho-crm-implementation)

[See the service →](https://flitstack.ai/services/zoho-crm-implementation)

### [All crm migrations](https://flitstack.ai/migrations/crm)

[Every destination we migrate pipelines, contacts, and deals into.](https://flitstack.ai/migrations/crm)

[Back to CRM →](https://flitstack.ai/migrations/crm)

## Sources

1. [Zoho CRM (application) — Wikipedia](https://en.wikipedia.org/wiki/Zoho_CRM_\(application\))
2. [We ditched HubSpot at $2M revenue and saved $12K/year — r/CRMSoftware](https://www.reddit.com/r/CRMSoftware/comments/1seflc1/we_ditched_hubspot_at_2m_revenue_and_saved_12kyear/)
3. [How to Migrate from Salesforce to Zoho CRM — zoflowx](https://www.instagram.com/reel/DWnhUTpERXd)
4. [Data Migration: An Introduction — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/data-administration/data-migration/articles/data-migration-overview)
5. [Standard Modules & Fields — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/standard-modules-fields)
6. [Custom Modules — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/custom-modules)
7. [Zoho One Changes have taken my business offline — r/Zoho](https://www.reddit.com/r/Zoho/comments/1rqampk/zoho_one_changes_have_taken_my_business_offline/)
8. [Importing Data — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/data-administration/import-data/articles/import-data)
9. [Importing Into Zoho CRM — Zoho Community](https://help.zoho.com/portal/en/community/topic/importing-into-zoho-crm)
10. [Edition-wise Data Storage limits in Zoho CRM](https://help.zoho.com/portal/en/community/topic/introducing-edition-wise-data-storage-limits-in-zoho-crm-10-1-2020)
11. [Feature Availability — Zoho CRM Plus](https://www.zoho.com/crm/crmplus/complete-feature-list.html)
12. [Upsert Records — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/data-administration/articles/upsert-records)
13. [Upsert Records Using External ID — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/data-administration/articles/external-id)
14. [Migrating Data — Zoho CRM (migration@zohocrm.com)](https://help.zoho.com/portal/en/kb/crm/data-administration/data-migration/articles/data-migration-overview)
15. [Zoho CRM Feature Availability and Limits](https://www.zoho.com/crm/help/feature-availability.html)
16. [Rollup Summary fields — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/rollup-summary)
17. [Creating Formula Fields — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/create-formula-fields)
18. [Picklist Values — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/picklist-values)
19. [Types of Custom Fields — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/types-of-fields)
20. [Zoho CRM Sandbox Testing Environment](https://www.zoho.com/crm/developer/sandbox.html)
21. [Creating and Using Sandbox — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/data-administration/sandbox/articles/creating-sandbox)
22. [FAQs on Activities (Calls, meetings and tasks) — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/faqs/activity-management/articles/faqs-on-activities)
23. [Rich Text For Notes in Zoho CRM](https://help.zoho.com/portal/en/community/topic/rich-text-for-notes-in-zoho-crm-29-5-2025)
24. [Import past emails into Zoho CRM — Zoho Community](https://help.zoho.com/portal/en/community/topic/import-past-emails-into-zoho-crm)
25. [Adding history for events — Zoho Community](https://help.zoho.com/portal/en/community/topic/adding-history-for-events)
26. [Attachment limits — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/manage-crm-data/attachments-and-notes/articles/attachment-limits)
27. [ZohoCRM Attachment Storage — r/Zoho](https://www.reddit.com/r/Zoho/comments/k7fg20/zohocrm_attachment_storage)
28. [Manage File Storage in Zoho CRM (WorkDrive)](https://help.zoho.com/portal/en/kb/crm/manage-crm-data/storage-space/articles/managing-file-storage)
29. [Import Created Time and Modified Time — Zoho Community](https://help.zoho.com/portal/en/community/topic/import-created-time-and-modified-time)
30. [Zoho Create Date workaround — HubSpot Community](https://community.hubspot.com/t5/CRM/Zoho-CRM-Migration-Data-not-Properly-Migrated/m-p/927008?profile.language=fr)
31. [Troubleshooting Data Import and Export — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/troubleshooting-tips/articles/troubleshooting-data-import-export)
32. [Viewing Import History — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/data-administration/import-data/articles/view-import-history)
33. [Monitoring Audit Logs — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/security-control/audit-log/articles/monitor-audit-log)
34. [Export Audit Log — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/security-control/audit-log/articles/export-audit-log)
35. [Find a Zoho Partner — Zoho](https://www.zoho.com/partners/find-zoho-partner.html)
36. [Zoho CRM Calendar Sync setup — Zoho Community](https://help.zoho.com/portal/en/community/topic/my-calendar-is-not-updated-with-my-events-created-into-the-crm)
37. [Multiple Sales Pipeline — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/pipelines/articles/multiple-sales-pipeline)
38. [Merging Duplicate Records — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/manage-crm-data/duplication-management/articles/merge-duplicate-record)

Get a quote

## Moving to Zoho CRM?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Zoho CRM setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
