Close to Zoho CRM migration
We migrate Leads, Contacts, Opportunities, and activity history from Close into Zoho CRM with JSON export required for the full engagement timeline, pipeline stages configured in Zoho before Opportunity import, and Custom Activity types sequenced in dependency order so type-scoped fields validate on insert.
FlitStack AI migrates leads, contacts, deals, pipelines and stages from Close to Zoho CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Close to Zoho CRM?
Close and Zoho CRM take different approaches to record architecture, automation scope, and calling stack.
Read the full summary
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.
Lead → Lead
Close Leads map to Zoho CRM Leads.
How it maps
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.
Contact → Contact
Close Contacts map to Zoho CRM Contacts.
How it maps
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.
Opportunity → Deal
Close Opportunities map to Zoho CRM Deals.
How it maps
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.
Pipeline → Pipeline
Close Pipelines map to Zoho CRM Pipelines.
How it maps
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.
Pipeline Stages → Stage
Close Pipeline Stages map to Zoho CRM Stages within their parent Pipeline.
How it maps
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.
Activities (Calls, Emails, SMS, Tasks) → Notes / Activity History
Close activity records (calls, emails, SMS, tasks) are retrieved via JSON export because CSV export silently omits all activity data.
How it maps
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.
- LeadLead1:1
- ContactContact1:1
- OpportunityDeal1:1
- PipelinePipelinetransformed
- Pipeline StagesStagetransformed
- ActivitiesNotes1:1
+ 6 more in the mapping below
How Close and Zoho CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Close | Zoho CRM |
|---|---|---|
| Record model for prospects | Leads and Contacts share a unified thread inbox with no separate Convert step | Separate Leads and Contacts with explicit Convert-to-Contact action tied to an Account |
| Calling stack | Built-in Power Dialer and Predictive Dialer on Growth and Scale tiers | No native calling; phone integrations via third-party VoIP or Zoho Voice (paid add-on) |
| Custom Activities | Custom Activity Types with their own schema, available on Growth and Scale | No direct equivalent; custom modules or Notes serve as the closest alternative for event logging |
| Automation scope | Automated Workflows with triggers, steps, and goals on Growth and Scale | Workflow Rules, Blueprints, Assignment Rules, and Deluge scripting from Professional tier |
| Pipeline structure | Multiple pipelines with stages, probability weights, and owner assignment | Multiple pipelines with Stages, but stages are tied to a Sales Process and Page Layout per module |
| Free tier | Solo at $9/seat with no calling, no workflow | Free tier up to 3 users with basic lead and deal management |
| Mobile experience | Criticised for missed call notifications and frequent app refresh | Mobile app available on all tiers; UI is more functional than polished |
What to watch for in a Close to Zoho CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
CSV export silently drops all activity history
Close's CSV export intentionally omits calls, emails, SMS, and tasks.
How we handle it
We always request JSON export to capture the full activity stream. If a customer has only used CSV exports, we flag during scoping that their activity history needs to be re-exported from Close before migration begins. Without JSON export, engagement history is unrecoverable after the fact and cannot be backfilled retroactively from Close's API without a full re-export.
Zoho has a 300-field limit per module
Zoho CRM enforces a maximum of 300 fields per module at the org level.
How we handle it
Close customers with extensive Custom Fields on multiple modules may exceed this limit when migrating to Zoho. We audit field counts per module during discovery and flag any module that would exceed 300 fields, recommending a field consolidation strategy (archiving inactive fields, merging related picklists) before migration begins. This constraint applies regardless of Zoho edition.
Custom Activities require strict three-phase sequencing
Close Custom Activities have a dependency chain: the Custom Activity Type must exist, then its type-scoped Custom Fields must exist, then activity instances can be imported.
How we handle it
We run this as a three-phase pipeline with validation gates between each phase. If phase two (Custom Fields) fails, phase three (activity records) cannot start and the error surfaces as a Zoho validation rejection. This is a migration-blocking constraint that requires careful sequencing.
Close Workflows do not migrate to Zoho Blueprint or Workflow Rules
Close Automated Workflows are only available on Growth and Scale tiers and contain rule logic tightly coupled to Close's event model.
How we handle it
Zoho Workflow Rules, Blueprints, and Assignment Rules are different automation constructs. We do not migrate Workflows as automation code. We deliver a written inventory of every active Close Workflow (trigger, conditions, actions, cadence) with a Zoho equivalent recommendation for the customer's admin to rebuild post-migration.
Zoho import rejects records with non-existent picklist values
Zoho CRM's import process validates every picklist field against the destination field's allowed values.
How we handle it
Any row with a picklist value that does not exist in Zoho is rejected. We normalise Close picklist labels against Zoho's allowed values during the transform step and flag any unmapped values for the customer to resolve before import. This is a pre-import data quality step that prevents silent record loss during bulk import.
How the migration runs
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.
What this step covers
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.
What this step covers
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.
What this step covers
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.
What this step covers
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.
What this step covers
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.
What this step covers
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.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and the number of Zoho Pipelines to configure. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Close to Zoho CRM →Why teams move from Close to Zoho CRM
- Teams that need broader business application coverage move from Close to Zoho because Zoho One bundles 50+ apps (CRM, accounting, helpdesk, project management, email marketing, HR) under a single $45/user/month plan. Close is purpose-built for outbound sales calling and does not offer adjacent application coverage, forcing teams to pay for and manage multiple SaaS subscriptions that Zoho consolidates into one platform.
- Close's feature set is intentionally lean to keep the UI clean for sales reps, but G2 and Reddit reviewers cite that advanced reporting, deep customisation, and complex workflow logic are missing compared to Zoho CRM. Teams needing Blueprint process management, multi-territory reporting, or Zia AI-driven insights move to Zoho for capabilities that Close does not offer at any tier.
- Close Solo ($9) and Essentials ($49) lack Automated Workflows — that feature requires Growth at $99 or Scale at $139. Zoho CRM includes Workflow Rules, Assignment Rules, Blueprints, and Deluge scripting from its Professional tier ($23/user/month annual), giving teams process automation at a lower entry point than Close's automation-gated tiers.
- Zoho CRM offers native custom modules (called Custom Modules or Custom Tables) from the Professional tier without a separate enablement fee, while Close's Custom Objects and Custom Activities are only available on Growth and Scale and require careful dependency ordering during migration. Teams with complex data models find Zoho's custom module approach more accessible and less migration-risky.
- Close's mobile app receives consistent criticism for missed call notifications, navigation friction, and the need to reopen the app to refresh call status. Zoho's mobile app, while not as polished as Salesforce's, covers standard CRM functions (lead management, pipeline updates, task creation) across all tiers and is rated more functional for field-sales and mobile-first teams.
Questions, answered
Close to Zoho CRM migration questions
How long does a Close to Zoho CRM migration take?
Most migrations land between three and five weeks for accounts under 10,000 Leads and Contacts with no Custom Activities or Custom Objects. Migrations with Custom Activities, multiple Zoho Pipelines, large engagement histories (over 200,000 activity records), or Custom Objects move to six to ten weeks because of the three-phase Custom Activity sequencing, stage-probability mapping per pipeline, and the validation steps required before each phase begins.
Do Close Workflows migrate to Zoho?
No. Close Automated Workflows are available only on Growth ($99) and Scale ($139) tiers and contain rule logic tightly coupled to Close's event model. Zoho Workflow Rules, Blueprints, Assignment Rules, and Deluge scripting are different automation constructs. We do not migrate Workflows as automation code. We deliver a written inventory of every active Close Workflow with its trigger, conditions, actions, and a Zoho equivalent recommendation (Workflow Rule, Blueprint stage, or Deluge function) for the customer's admin to rebuild post-migration.
Do we lose historical engagement data (calls, emails, SMS, tasks) migrating from Close to Zoho?
No, provided the customer exports from Close in JSON format before migration begins. CSV export silently drops all activity history. We always request JSON and use it to reconstruct activity records as Zoho Notes attached to the corresponding Lead or Contact. The chronological ordering of the timeline is preserved by setting the Note creation date to the original Close activity timestamp. If the customer has only CSV exports, we flag this immediately during scoping and pause migration work until JSON exports are available.
Can Close Custom Activities migrate to Zoho CRM?
Yes, but with a three-phase sequencing requirement. The Custom Activity Type must be created in Zoho first (phase one), then its type-scoped Custom Fields must be created (phase two), then activity instances can be imported (phase three). Skipping phases or importing out of order returns Zoho validation errors. We handle this sequencing automatically but require customer approval of the Zoho module structure before phase one begins. If Zoho's Custom Module approach is not suitable for the customer's use case, we document the closest available structure (Notes, Tasks, or a standard module) for the customer to evaluate.
How do we handle Close Smart Views in Zoho CRM?
Close Smart Views are saved Lead searches with filter criteria. We export the filter configuration as named Saved Filters in Zoho CRM. Since Close exports Smart Views only from the Leads tab (not the Contacts tab), we query Leads directly via the Close API to ensure all contact records are retrieved regardless of how saved views are structured in the UI. The customer should be aware that Zoho's Saved Filters behave slightly differently from Close's Smart Views and may require minor adjustment of filter logic.
What Zoho edition do we need for this migration?
Zoho CRM Standard ($14/user/month annual) covers basic lead and deal migration. Professional ($23/user/month annual) is required for Blueprint process management, inventory modules, and workflow rules if the customer plans to rebuild Close Workflows in Zoho. Enterprise ($40/user/month annual) adds Zia AI features and multi-user portals. Custom Modules require Professional or above. We recommend Professional as the minimum for most Close migrations that include automation rebuild scope.
Does FlitStack AI migrate to Zoho Bigin instead of Zoho CRM?
Zoho Bigin is a separate, pipeline-focused CRM product with lower pricing and less customisation than Zoho CRM (no custom modules or custom tables). If the customer's Close data uses Custom Objects or Custom Activities, Bigin is not a viable destination. If the migration scope is straightforward leads and deals with no custom objects, we can migrate to either Zoho CRM or Zoho Bigin based on the customer's product choice. We confirm the destination product during scoping.
Related migrations
Zoho CRM implementation
Set up Zoho CRM and migrate into it as one engagement.
See the service → MarketSharp to Zoho CRMMapping · history · rollbackBitrix24 to Zoho CRMMapping · history · rollbackDaylite to Zoho CRMMapping · history · rollbackSage CRM to Zoho CRMMapping · history · rollbackBigin by Zoho CRM to Zoho CRMMapping · history · rollbackPBS Systems to Zoho CRMMapping · history · rollback Close to monday CRMMapping · history · rollbackClose to HubSpotMapping · history · rollbackClose to SalesforceMapping · history · rollbackGet a quote
Moving from Close to Zoho CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Zoho CRM setup with you, then send a quote.
Get a quote