Migrate from GleanView to Zoho CRM

GatherView Contact records map directly to Zoho CRM Contact. Standard fields (First Name, Last Name, Email, Phone, Title, Owner) map 1:1. We deduplicate against Zoho using email as the primary key and flag any duplicate email addresses for your admin to resolve before import. Custom Contact fields from GleanView export as custom fields in Zoho, preserving the field type where possible (text, number, date, picklist). Lifecycle stage values are mapped to Zoho Lead Status or a custom picklist depending on your Zoho configuration.

GatherView Company records map to Zoho CRM Account. We use Company Name as the dedupe key and resolve any duplicate names before import. Address, industry, website, and custom company fields map to the equivalent Zoho Account fields. Account is created before any Contact import so that the Account Name lookup on Contact is satisfied at insert time, maintaining referential integrity across the full data model.

GatherView Lead records map to Zoho CRM Lead. Lead source, status, owner, and custom fields transfer directly. GleanView's lead lifecycle stages are mapped to Zoho Lead Status values via a status-mapping worksheet presented during scoping. Any unmapped custom lead statuses are flagged and resolved with the customer before migration begins. Owner resolution uses email matching against Zoho User records.

GatherView Deals map to Zoho CRM Potential (Zoho's Opportunity equivalent). Stage, Amount, Close Date, Owner, and custom deal fields transfer directly. We map each GleanView pipeline stage to a corresponding Zoho Stage or create a custom Stage if the destination Zoho layout does not include an equivalent. Closed-Lost and Closed-Won dates from GleanView are preserved in Zoho Potential custom date fields if the standard Stage transition does not capture them.

Each GleanView pipeline and its stage names are mapped to Zoho CRM Stage values within the relevant Sales Pipeline. We present a stage-mapping worksheet during scoping so the customer can choose whether to use Zoho's default stages (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) or create custom stage names matching their GleanView terminology. Stage order and probability percentages are preserved where Zoho supports custom probabilities per stage.

GleanQuote product catalog items (base price, cost, margin, SKU, unit of measure) map to Zoho CRM Product records. We extract product names, codes, and base prices from the GleanView CSV. Conditional pricing fields and formula-derived prices are flagged individually — these fields do not export as static values from GleanQuote. Customers choose whether to pre-compute formula prices in a staging sheet or correct them post-migration; we document every affected field.

GatherView Quotes map to Zoho CRM Quotes if the customer licenses the Quotes module. Quote headers and line items are extracted from CSV and re-created as Zoho Quote records linked to the correct Potential and Contact. GleanView proposal PDF templates do not export from CSV — we deliver a quote template manifest listing each template's name and associated Products so the customer's Zoho admin can recreate templates in Zoho using the standard template builder or a third-party quoting tool.

GatherView engagement records (calls, emails, meetings, tasks, notes) attached to Contacts, Companies, or Deals map to Zoho CRM Tasks and Events. We use the related record's Zoho ID to set the WhatId (linked entity) and preserve the original GleanView timestamp as the Activity Date in Zoho. Multi-select or rich-text notes may require reformatting depending on Zoho's Notes field character encoding. Activity batches over 10,000 records are chunked to avoid Zoho import throttling.

Custom fields on Contacts, Companies, Deals, and Leads are read from GleanView CSV headers during data assessment. Each custom field is mapped to a Zoho CRM custom field of the matching type (text, number, date, picklist, multi-select, checkbox). Zoho field-level security can restrict visibility by role; we coordinate with the customer's Zoho admin to ensure the migration user has write access to all target custom fields before import begins.

GatherView record tags are mapped to Zoho CRM Tags. Tags stored as multi-value comma-separated fields in CSV are split into individual Zoho Tag records and applied to the corresponding Contact, Account, Lead, or Potential. If Zoho Tags are not available in the customer's current edition, tags are mapped to a custom multi-select picklist field as an alternative.