CRM migration
Field-level mapping, validation, and rollback between Close and Zoho CRM. We move data and schema; workflows are rebuilt natively in Zoho CRM.
Close
Source
Zoho CRM
Destination
Compatibility
10 of 12
objects map 1:1 between Close and Zoho CRM.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Close and Zoho CRM take different approaches to record architecture, automation scope, and calling stack. Close stores prospects as Leads and Contacts in a unified thread view with built-in Power Dialer and Predictive Dialer; Zoho CRM separates Leads and Contacts under a module-based structure and requires third-party VoIP integration for calling. We extract Close data via JSON export (CSV silently drops activity history), resolve the Lead-to-Zoho-Lead mapping, and configure Zoho Pipelines and Stages before Opportunity records import. Custom Activities in Close follow a three-phase migration sequence that must execute in strict order: create the type, create type-scoped Custom Fields, then import activity instances. Workflows built in Close's Growth or Scale tiers do not migrate as automation code; we deliver a written inventory of every active Workflow for the customer's admin to rebuild in Zoho Workflows, Blueprint, or Deluge.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Close object lands in Zoho CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Close
Lead
Zoho CRM
Lead
1:1Close Leads map to Zoho CRM Leads. We preserve all standard fields (name, email, phone, status, source, owner) and map the Close lead status label to Zoho's Lead Status picklist values. If the customer has used Close's lead status labels that don't exist in Zoho, we create custom picklist values to avoid data truncation. Custom Fields scoped to Leads are created in Zoho before Lead import so field mapping resolves at insert time.
Close
Contact
Zoho CRM
Contact
1:1Close Contacts map to Zoho CRM Contacts. We resolve the Zoho Account reference at migration time by matching Close's organisation field to a Zoho Account by name. If multiple Accounts share the same name, we apply a dedupe key (domain or phone) to avoid creating duplicates. Contact Custom Fields migrate alongside the parent Contact record.
Close
Opportunity
Zoho CRM
Deal
1:1Close Opportunities map to Zoho CRM Deals. The mapping uses Deal Name, Amount, Closing Date, and Stage. We create the Zoho Pipeline first, then map each Close pipeline stage to a Zoho Stage with probability weight preserved. If Close uses multiple pipelines, we configure multiple Zoho Sales Processes and assign a Record Type per pipeline.
Close
Pipeline
Zoho CRM
Pipeline
lossyClose Pipelines map to Zoho CRM Pipelines. We create the pipeline structure in Zoho first, then configure stages in display order. Stage probability weights migrate to Zoho Stage Probability values. Custom pipeline columns from Close become Deal Custom Fields scoped to the Opportunities module.
Close
Pipeline Stages
Zoho CRM
Stage
lossyClose Pipeline Stages map to Zoho CRM Stages within their parent Pipeline. Stage names, display order, and probability weights migrate directly. If a Close stage name contains characters not allowed in Zoho picklists, we normalise them during import.
Close
Activities (Calls, Emails, SMS, Tasks)
Zoho CRM
Notes / Activity History
1:1Close activity records (calls, emails, SMS, tasks) are retrieved via JSON export because CSV export silently omits all activity data. Calls and tasks migrate to Zoho Notes attached to the corresponding Lead or Contact record, with the activity type, direction, duration, and disposition preserved in the Note body. Email content migrates to Zoho Notes with a structured header. We cannot replicate Close's threaded conversation view in Zoho without manual customisation; the timeline will be sequential by date.
Close
Custom Fields (Lead, Contact, Opportunity)
Zoho CRM
Custom Fields
1:1Custom Fields scoped to Lead, Contact, and Opportunity are read from Close's field definition API (field type, choices, required flag) and created in Zoho with matching field types. Multi-select picklists from Close map to Zoho multi-select picklists; date fields map to Zoho date fields; currency fields map to Zoho currency fields. Choice-option labels are preserved verbatim.
Close
Custom Activities
Zoho CRM
Custom Modules or Notes
1:1Close Custom Activities require a three-phase migration pipeline. Phase one creates the Zoho Custom Module (or repurposes a standard module) that receives the activity data. Phase two creates all Custom Fields scoped to that type in Zoho. Phase three imports activity instances referencing the type and field schema created in phases one and two. Skipping phases or running them out of order returns validation errors from Zoho. If the customer uses Zoho without a Custom Module equivalent, we document the closest available structure (Notes, Tasks, or a Custom Module) for the customer to approve before migration.
Close
Custom Objects
Zoho CRM
Custom Modules
1:1Close Custom Objects map to Zoho CRM Custom Modules. We create the Custom Module definition in Zoho first (API name, label, plural label), then create all fields on the module, then import records. Custom Object records can reference Leads, Contacts, or Deals via lookup fields; we resolve those lookups after the parent standard object migration is complete.
Close
Attachments
Zoho CRM
Attachments
1:1Attachments on Close Leads and Contacts are retrieved via the Close API as binary files. We re-upload them to the corresponding Zoho Lead or Contact record as Zoho Attachments. If the attachment filename contains characters not supported by Zoho, we sanitise the filename before upload. Attachment count and file type are preserved.
Close
Smart Views
Zoho CRM
Saved Filters
1:1Close Smart Views (saved Lead searches) are exported as named saved filter configurations. Since Smart Views can only be created from the Leads tab in Close, we query Leads directly via the Close API to retrieve all contacts regardless of how the saved views are structured in the UI. The filter criteria migrate as named Saved Filters in Zoho CRM.
Close
User / Team Member
Zoho CRM
User
1:1Close Users map to Zoho CRM Users. We match by email address. Any Close Owner referenced on a record without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision the User before record import resumes. Role and team membership are noted in a separate handoff document for manual configuration in Zoho; we do not replicate Zoho permission structures during data migration.
| Close | Zoho CRM | Compatibility | |
|---|---|---|---|
| Lead | Lead1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Pipeline Stages | Stagelossy | Fully supported | |
| Activities (Calls, Emails, SMS, Tasks) | Notes / Activity History1:1 | Mapping required | |
| Custom Fields (Lead, Contact, Opportunity) | Custom Fields1:1 | Fully supported | |
| Custom Activities | Custom Modules or Notes1:1 | Mapping required | |
| Custom Objects | Custom Modules1:1 | Mapping required | |
| Attachments | Attachments1:1 | Mapping required | |
| Smart Views | Saved Filters1:1 | Mapping required | |
| User / Team Member | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Close gotchas
CSV exports drop all activity history silently
Smart Views can only export from the Leads tab
Workflows gatekept behind Growth and Scale plans
Custom Activities require strict dependency ordering
Rate limits enforced per endpoint group
Zoho CRM gotchas
API access requires Professional tier or above
Subform fields do not export cleanly via CSV
API credit consumption is non-linear
Export download links expire in 7 days
Owner (User) assignments require pre-mapped user IDs
Pair-specific challenges
Migration approach
Discovery and export audit
We audit the source Close account across tier (Solo/Essentials/Growth/Scale), pipeline count, Custom Fields per module, Custom Activities, Custom Objects, and Smart View structure. We specifically verify whether the customer has JSON exports of activity data or only CSV exports (which would require re-export before scoping begins). We also identify any Workflows on Growth or Scale tiers that require documentation for rebuild. The discovery output is a written migration scope document covering record counts, field inventory, and any known migration blockers.
Schema design and Zoho module configuration
We design the destination Zoho CRM schema. This includes creating Custom Modules for any Close Custom Activities or Custom Objects, creating Custom Fields with type-matched field definitions (picklist values, required flags, default values), configuring Zoho Pipelines and Stages in display order with probability weights, and setting up Sales Processes tied to each pipeline. We configure this in a Zoho Sandbox or development org first for validation before production migration begins.
Data export and JSON validation
We request and validate Close JSON exports for all modules including activity history. If the customer has only CSV exports, we escalate immediately that activity data must be re-exported as JSON before any migration work begins. We validate field completeness in the JSON export, flag any missing mandatory Zoho fields for manual backfill, and confirm record counts per module against the discovery inventory before proceeding to the transform step.
Transform and field mapping
We apply the field mapping transformation: Close Lead fields to Zoho Lead fields, Close Contact fields to Zoho Contact fields with Account lookup resolution, Close Opportunity fields to Zoho Deal fields with Pipeline and Stage assignment, and Custom Field values type-mapped to Zoho field types. Any picklist value normalisation happens here. We build a reconciliation report showing source record count versus transformed record count before any Zoho insert begins.
Production migration in dependency order
We run production migration in dependency order: Users (validated), Accounts (from Close organisations), Leads, Contacts (with AccountId resolved), Deals (with Pipeline and Stage assigned), Custom Fields data, Custom Activities (phase one: create type; phase two: create type-scoped fields; phase three: import activity records), Custom Object records, Attachments, then activity history via Notes. Each phase emits a row-count reconciliation report before the next phase begins. Owner references without a matching Zoho User are held in a reconciliation queue.
Cutover, validation, and Workflow rebuild handoff
We freeze Close writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho CRM as the system of record. We deliver the Close Workflow inventory document to the customer's admin team for rebuild in Zoho Workflow Rules, Blueprint, or Deluge. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild Workflows as Zoho automation inside the migration scope; that is a separate engagement or internal admin task.
Platform deep dives
Close
Source
Strengths
Weaknesses
Zoho CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Close and Zoho CRM.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Close: Per endpoint group with a lower limit on write operations; 429 response includes rate_reset value; limits enforced at the organisation level across all API keys.
Data volume sensitivity
Close doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Close to Zoho CRM migration scoping. Not seeing yours? Book a call.
Walk through your Close to Zoho CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Close
Other ways to arrive at Zoho CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.