Migrate from GleanView to Microsoft Dynamics 365 Sales

GatherView Company records map directly to Microsoft Dynamics 365 Account. Address fields, industry, website, and all custom Company fields transfer via CSV column mapping. We use the Company name as the dedupe key during import and resolve any duplicate company names against the destination before insertion. Account is created before Contact import so that the ParentAccountId and primary-contact lookup relationships are satisfied at the moment of Contact insert.

GatherView Contact records map 1:1 to Dynamics 365 Contact. Email address is the dedupe key. Name, phone, job title, lifecycle stage, owner, and custom Contact properties transfer via CSV column mapping. We resolve the parent AccountId by matching the Contact's Company link to an Account record already inserted in the previous phase. Any Contact without a matching Company is held in a reconciliation queue.

GatherView Lead records include source, status, and owner fields. If the Lead has been pre-qualified and already has a Company association in GatherView, it may map to Contact under an Account. Otherwise it maps to Dynamics 365 Lead with status values translated from GatherView's lifecycle stages to Dynamics Lead Status options. Any custom status values with no direct Dynamics equivalent are flagged for the customer's admin to define in the destination before import.

GatherView Deal records map to Dynamics 365 Opportunity. Stage, amount, close date, owner, and all custom Deal fields transfer. GatherView pipeline stages map to Microsoft Dynamics 365 Sales Process stage values. We preserve deal stage history as a custom field opportunity_stage_history__c if the destination org does not have the full audit trail enabled. Custom deal fields map to typed Opportunity fields in Dynamics.

GatherView product catalog entries (SKUs, names, base prices, costs, margins, and attributes) map to Dynamics 365 Product2 records. Standard Price Book entries are created during import using the base price from GatherView. Bundle products and conditional pricing rules require field-level flagging before load: GatherView formula pricing does not export as flat values, so we present options (pre-compute in staging, re-evaluate in Dynamics, or accept manual post-migration correction) before proceeding.

GatherView Quotes map to Dynamics 365 Opportunity records with line items representing quote lines. The Quote header (customer reference, validity dates, terms) maps to Opportunity fields or a custom Quote object if the customer licenses Microsoft Dynamics 365 Sales Premium with native Quote-to-Order. Template attachments (proposal PDFs stored in GleanSpaces) are not included in CSV exports; we provide a file manifest listing each linked attachment URL and associated record for manual re-upload.

GatherView email logs, calls, and notes attached to Contacts or Deals export as Activity rows in CSV. Calls map to Task with TaskSubtype = Call and duration preserved. Meeting-type activities map to Dynamics 365 Event. Multi-select or rich-text activity notes may require HTML-to-plaintext reformatting in the destination. We chunk large activity batches into batches of 5,000 records per import job.

GatherView custom fields on Contacts, Companies, Deals, and Leads require per-field mapping. We read the CSV column headers to extract the GatherView field schema, map each to a typed Dynamics 365 field (text, integer, decimal, picklist, lookup), and present a field-mapping worksheet before migration begins. Lookup fields referencing other GatherView objects require parent-record resolution in the destination before the child record import.

GatherView custom pipeline stages map to Microsoft Dynamics 365 Sales Process stage values. We design a Sales Process in the destination matching the GatherView stage order and names, configure stage probabilities to match the source, and assign it to the relevant Opportunity Record Type. Stages with no clear Dynamics equivalent are flagged during scoping for the customer to define before migration.