Migrate from GleanView to Pipedrive

GatherView Company records export via CSV with fields including company name, domain, industry, address, phone, and owner. We map directly to Pipedrive Organization (org_name, address, phone). The Organization is the first record type imported because every Contact requires an org_id lookup. We deduplicate against Pipedrive Organizations using domain as the dedupe key and flag any ambiguous duplicates for customer resolution before insert.

GatherView Contact records map to Pipedrive Person (name, email, phone, job title, owner). We deduplicate against Pipedrive using email as the primary key. Any Contact without an email address is flagged for the customer to assign manually. The org_id on the Person record is resolved by matching the Contact's parent Company domain to the Organization created in the previous step.

GatherView Lead records include source, status, owner, and lifecycle stage. We map Lead status values to Pipedrive Lead Status using a status-mapping worksheet provided during scoping. Any unmapped custom status values from GleanView are preserved in a custom field gv_original_status__c on the Pipedrive Lead for audit. The owner resolves by email match to the Pipedrive User.

GatherView Deals map to Pipedrive Deal with stage, value, currency, expected close date, owner, and linked Contact and Company. We pre-configure Pipedrive Pipelines and Stages before Deal import so that the stage mapping is deterministic. If GleanView uses multi-currency, we map currency codes and note that Pipedrive's multi-currency is available from the Advanced tier. Closed-Won and Closed-Lost reasons from GleanView custom fields migrate to Pipedrive Activity fields or lost_reason custom fields.

GatherView's custom pipeline stages (with stage-specific actions or conditional logic) are mapped to Pipedrive Stage records within a Pipeline. Each GleanView stage becomes a Pipedrive stage with a corresponding probability value. Stage order is preserved. Any stage with no clear Pipedrive equivalent is flagged for the customer to define before Deal import.

GleanQuote product catalog entries (base price, cost, margin, attributes, SKU) export as CSV rows. We map to Pipedrive Products with Standard Price Book entries created during import. Formula-driven pricing fields (conditional pricing, volume discounts, cost-plus-markup rules) are flagged before import because they compute at render time and do not appear as flat values in CSV. The customer chooses among three options: export base cost fields and let Pipedrive recompute, pre-compute pricing in a staging sheet before import, or accept that formula-derived prices will need manual correction post-migration.

GatherView Quotes reference Products, Contacts, and pricing rules. We extract quote headers and line items from CSV exports. Pipedrive does not have a native Quote object at the Essential or Advanced tier; quotes are handled as Deal-linked Products or as Activity Notes with a template attachment. During scoping we confirm whether the customer needs to preserve quote documents as PDFs or just quote line-item data. Template-driven proposals stored in GatherSpaces do not export via CSV and are listed in the file manifest for manual re-upload.

GatherView activity logs (emails, calls, meetings, notes) tied to Contacts or Deals export as CSV rows. We map them to Pipedrive Activities using the activity_type field to set the correct Pipedrive Activity type (call, email, meeting, note). Activity timestamps preserve ordering. Multi-select or rich-text notes may require reformatting. Large activity batches are chunked to avoid row limits in Pipedrive's CSV import tool.

Custom fields on Contacts, Companies, Deals, and Leads require per-field mapping against Pipedrive's 16 supported custom field types. We read the GleanView field schema from the CSV headers, present a field-mapping worksheet before migration begins, and pre-create Pipedrive custom fields in the account so the mapping is resolved before data import. Pipedrive's custom field API names use the field label as a slug; we preserve the original GleanView field name as a pipelabel custom field for reference.

GatherView proposal PDFs, product images, and content library files stored in GatherSpaces do not appear in the standard CSV export. We document every linked file URL in a file manifest listing the URL, the associated GleanView record, and the record type. If Pipedrive supports external file references (for example, Google Drive links stored in a URL custom field), we relink them during migration. Binary files must be re-uploaded manually; we provide a checklist with the file manifest to guide the customer through that process.