Migrate from GleanView to Freshsales

GleanView Contact records carry a lifecycle stage property that we evaluate against the customer's Lead-Contact split rule. Prospects with no closed-won deal history map to Freshsales Lead. Contacts with a GleanView deal history or explicit account association map to Freshsales Contact under a Freshsales Account. The original GleanView lifecycle stage is preserved in a custom field original_lifecycle_stage__c on both Lead and Contact for reporting continuity.

GleanView Company records map directly to Freshsales Account. Company name becomes Account Name; address, industry, and website fields map 1:1. We use Company Name as the dedupe key during import to catch duplicates that accumulated in GleanView over time. Freshsales Account is created before any Contact import so that the account_id lookup is satisfied at Contact insert time.

GleanView Lead records map directly to Freshsales Lead. Lead status values from GleanView are mapped to Freshsales lead status values via a mapping table prepared during scoping. Any custom lead fields from GleanView become Freshsales custom fields of equivalent type. Owner email is matched to a Freshsales User by email lookup, with unmapped owners flagged for admin provisioning.

GleanView Deals map to Freshsales Deals with stage, amount, close date, owner, and associated account preserved. We configure Freshsales Deal Stages to match GleanView's pipeline stages before import so that stage values are valid on arrival. Deal amount fields with formula origins are flagged before import so the customer can choose to pre-compute or correct post-migration.

GleanQuote product catalog entries (base price, cost, margin, attributes) map to Freshsales Products. ProductCode from GleanQuote becomes the Freshsales SKU field. Complex products with conditional options or bundles require field-level mapping; formula-derived price fields are flagged per the pricing field protocol. We create the product records before Deals so that product associations on Deals are valid.

Freshsales has no native CPQ or Quote object equivalent to GleanQuote. We map GleanView Quote headers to Freshsales Deal records using Deal custom fields for quote number, validity date, and terms, and line-item custom fields for Products, quantities, unit prices, and discounts. The customer receives a written quote-template rebuild recommendation specifying which Freshsales HTML template or third-party CPQ integration to adopt post-migration.

GleanView email logs, call records, and notes export as Activities. Each activity type maps to Freshsales Task with TaskSubtype set to Email or Call as appropriate, and activity body preserved as the Task description. Activity timestamp maps to Freshsales Due Date for timeline ordering. Multi-select or rich-text activity notes are reformatted to plain text for Freshsales compatibility.

GleanView pipeline stages are mapped to Freshsales Deal Stages during schema setup. Each GleanView stage name is assigned a matching Freshsales stage (New, Contacted, Qualified, Proposal Sent, Negotiation, Closed Won, Closed Lost). Probability percentages from GleanView are applied to the corresponding Freshsales stage. Stages with no clear Freshsales equivalent are flagged for the customer's admin to configure before the Deal import phase.

GleanView Owner records are resolved by email match against the Freshsales User table. Any GleanView Owner without a matching Freshsales User is held in a reconciliation queue; the customer's admin provisions the missing User account before the production migration phase begins. Active versus inactive status is preserved as a flag on the reconciliation report.