Migrate from Glaze CRM to Pipedrive

Discovery and Glaze CRM data export coordination

We audit the customer's Glaze CRM instance by reviewing whatever schema documentation or sample exports they can provide. Simultaneously, we coordinate with the customer's team to request a full data export from Glaze CRM through their vendor support or sales channel. This export typically arrives as a CSV dump or database export. We cannot begin migration work without the data extract. We also confirm Pipedrive account setup (edition, seat count, Lead Management add-on status) and any existing Pipedrive data that should be preserved.

Schema audit and field mapping spreadsheet

Once the Glaze CRM export arrives, we perform a full schema audit: we identify standard fields (name, email, phone, address, stage), infer custom field types from sample values, identify multi-select fields, count unique Users, count unique pipeline stages, and catalog any Tags in use. We produce a field mapping spreadsheet that maps every Glaze CRM field to a Pipedrive field or custom field, with transformation notes. This spreadsheet is reviewed and signed off by the customer's admin before any data moves.

Pipedrive pipeline and field configuration

We configure Pipedrive before importing any records. This includes creating Pipedrive Pipelines that match the Glaze CRM stage names and probabilities, enabling the Lead Management add-on if Glaze Leads are present and the customer chooses to use Pipedrive Leads, and creating all custom fields on Person, Organization, and Deal objects. Field types are set explicitly (text, numeric, multi-option, date) to match the inferred types from the Glaze CRM export. This configuration is done in the customer's live Pipedrive account (not a sandbox, as Pipedrive does not charge for sandbox environments at all tiers).

User provisioning and owner reconciliation

We extract every distinct Glaze CRM User referenced on Contact, Company, Deal, and Engagement records and match by email against the Pipedrive destination account's User table. Any Glaze User without a matching Pipedrive User goes to a reconciliation queue. The customer's Pipedrive admin provisions any missing Users (active or inactive depending on whether the original Glaze user is still active). Migration cannot proceed past this step because OwnerId references are required on Deals and many Activity records.

Production migration in dependency order

We run production migration in record-dependency order: Organizations (from Glaze Companies first), People (with Organization resolved), Deals (with Organization, Owner, and Pipeline stage resolved), Leads (if applicable, with Lead Management enabled), Activity history (calls, emails, meetings, tasks mapped to Pipedrive Activities via API or CSV), and Custom field values. Each phase emits a row-count reconciliation report before the next phase begins. We use Pipedrive's API for bulk activity imports to preserve the full engagement timeline.

Cutover, validation, and automation handoff

We freeze Glaze CRM writes during cutover, run a final delta migration of any records modified during the migration window, then enable Pipedrive as the system of record. We deliver a written inventory of Glaze CRM pipeline configurations and custom field definitions for the customer's admin to rebuild in Pipedrive's visual pipeline editor and custom field settings. We support a five-business-day hypercare window where we resolve any data quality issues surfaced by the customer's team. We do not rebuild Glaze CRM automations or workflow rules as Pipedrive Workflows within migration scope; that is a separate engagement.