Migrate from GleanView to Salesforce Sales Cloud

GleanView uses a single Contact object with lifecycle stage properties (subscriber, lead, marketing qualified, sales qualified, customer). Salesforce requires a split: prospects without a company association map to Salesforce Lead; qualified buyers with an associated company map to Salesforce Contact attached to an Account. We apply the split rule at migration time using GleanView's lifecycle_stage property, preserve the original stage value in a custom field gv_original_lifecycle__c on both Lead and Contact, and set Lead Status from the GleanView lead_status property. Contacts with a GleanView company reference receive an AccountId lookup resolved from the Companies export.

GleanView Company records map to Salesforce Account with direct field mapping: Company Name to Account Name, domain or website to Website, industry to Industry, billing address to BillingAddress. We deduplicate by company name and domain during staging. Account is inserted before Contact import to satisfy the AccountId lookup requirement on Contact records. GleanView's custom company properties migrate to custom Account fields prefixed gv_.

GleanView Lead records (when exported as distinct from Contacts) map to Salesforce Lead with lead status, source, owner, and custom fields preserved. Owner resolution is by email match against Salesforce Users. Any GleanView Lead without a matching Salesforce User is held in a reconciliation queue. Lead score and rating migrate to custom numeric and picklist fields on the Salesforce Lead object.

GleanView Deals map to Salesforce Opportunity with direct field mapping: deal name to Opportunity Name, amount to Amount, close date to CloseDate, stage to StageName. GleanView's pipeline assignment requires pre-creation of Salesforce Record Types (one per GleanView pipeline) and Sales Processes that whitelist the destination stage values. Closed-Lost and Closed-Won custom reasons map to Salesforce Loss Reason and custom Win Reason fields.

GleanView's custom pipeline stages map to Salesforce Opportunity Record Types, each with its own Sales Process defining valid StageName values and probabilities. We create the Record Types and Sales Processes in a Salesforce Sandbox before production migration, matching stage order and probability percentages from GleanView. Stage-specific actions in GleanView have no Salesforce equivalent and are documented as manual configuration items in the handoff worksheet.

GleanQuote product records map to Salesforce Product2. We extract product name, SKU, cost, margin percentage, and product attributes from the CSV. Base prices create PricebookEntry records against the Standard Price Book. Products with conditional options or bundles require field-level decomposition: bundle parent becomes a Product2 with a custom bundle_flag__c checkbox, and bundle components become separate Product2 records with a lookup to the parent bundle product.

GleanQuote Quotes with line items map to Salesforce Quote records (Professional and above) attached to an Opportunity, or to OpportunityLineItems directly if the customer does not use Salesforce native Quote objects. Quote headers (customer reference, quote date, expiration, terms) migrate as Quote fields. Line items require Pricebook2, Product2, Quantity, and UnitPrice to be resolved at migration time. Template attachments (proposal PDFs stored in GleanSpaces) are not included in CSV exports; we provide a file manifest with URLs and associated Quote IDs for manual re-upload.

GleanView Owner references on Contact, Company, Deal, and Quote records map to Salesforce User by email lookup. We extract the distinct owner set from all GleanView exports and reconcile against the destination Salesforce org's User table. Missing Users are queued for admin provisioning before record import proceeds because OwnerId is required on most standard object inserts.

GleanView email logs attached to Contacts or Deals migrate to Salesforce EmailMessage (email content) linked to a Task record (timeline entry) with WhoId pointing to the Contact or Lead and WhatId pointing to the related Opportunity or Account. We use the Salesforce Bulk API for activity batches exceeding 5,000 records to avoid loader timeouts. Rich-text email body migrates as HTML in EmailMessage's HtmlBody field.

GleanView call logs migrate to Salesforce Task with TaskSubtype set to Call. Call disposition, duration, and recording URL (if available) migrate to custom Task fields. ActivityDate is set to the original GleanView timestamp to preserve timeline ordering.

GleanView meeting records map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendees map to EventRelation records linking to the associated Contact, Lead, or User. Virtual meeting links from GleanView meeting descriptions migrate as text in the Event Description field.

GleanView Notes attached to Contacts or Deals migrate to Salesforce Note records linked via ContentDocumentLink to the parent record. Note body migrates as plain text; rich-text formatting is preserved where GleanView's CSV export supports it. Multi-file note attachments (rare in GleanView's export format) are listed in the attachment manifest.

Custom fields on Contacts, Companies, Deals, and Products require per-field mapping against Salesforce's type system. We read the GleanView field schema from CSV headers during scoping, classify each field type (text, number, date, picklist, multi-select), and generate a Salesforce field creation manifest. Multi-select picklists in GleanView map to Salesforce multi-select picklists. Text fields over 255 characters map to Salesforce text area fields. Validation rules and required field constraints in the destination org must be temporarily relaxed or scoped with migration-context bypass logic during import.