Migrate from Gauss Box CRM & Sales to Pipedrive

Gauss Box Organization records (company name, industry, size, D&B data fields if enriched, address) map directly to Pipedrive Organization. The Organization Name is used as the dedupe key during import to prevent duplicate organizations. We create all Organizations before Persons so that the org_id lookup relationship is satisfied at the moment of Person insert. Gauss Box's D&B intelligence fields (creditworthiness, risk data) map to custom fields in Pipedrive if the customer has that add-on active.

Gauss Box Contact records (name, email, phone, address, custom attributes) map to Pipedrive Person. The Person's email is used as the dedupe key. We resolve the Person's organization_id by matching the Gauss Box Contact's linked Organization name to the Pipedrive Organization created in the previous phase. All custom attributes from Gauss Box's attribute-set system are enumerated during discovery and created as custom fields in Pipedrive before import.

Gauss Box Leads carry a work status and assigned team member. We offer two strategies: (1) Land all Leads in Pipedrive's Lead object with a conversion plan to Person-Organization pairs, or (2) Convert leads inline during migration where the work status indicates a qualified contact, mapping directly to a Person-Organization record. The customer chooses the strategy during scoping. We preserve the original Gauss Box Lead ID and work status in custom fields on the migrated record.

Gauss Box Deal records (stage, owner, value, budget, product associations) map to Pipedrive Deal. Pipeline stage names from Gauss Box are configurable per account, so we map them to Pipedrive's pipeline stage schema during migration. The Deal owner maps by email to the Pipedrive User directory. If the customer has multiple Gauss Box pipelines, we configure multiple Pipedrive pipelines (available from Advanced plan upward) or use Deal categories as a single-pipeline workaround.

Gauss Box deal pipelines map to Pipedrive pipelines. Each Gauss Box pipeline becomes a Pipedrive Pipeline with its own stage definitions. Stage probabilities migrate from Gauss Box's stage configuration to Pipedrive's stage probability fields. Pipedrive's Essential plan supports one pipeline; Advanced supports multiple pipelines.

Gauss Box Activities (interactions linked to Deals and Contacts) map to Pipedrive Activities with type resolution. We classify each Gauss Box Activity by its activity_type into one of Pipedrive's typed activities: Call (with CallDurationInSeconds), Meeting (with Start and End time), Task (with due_date), Email (with body and subject), or Note (with content). The parent object link (Deal or Person) migrates as a Pipedrive deal_id or person_id reference. Activity timestamps are preserved as the Pipedrive Activity timestamp.

Gauss Box Product catalog entries (name, category, type, price, sale tax configuration) map to Pipedrive Product. Product name and price migrate directly; category becomes a Pipedrive Product field. We create Products before Deals so that Deal-Product associations can be resolved at migration time. Tiered pricing and volume discount configurations in Gauss Box (if used) are captured as custom fields in Pipedrive since Pipedrive's standard Product object does not include native tiered pricing rules.

Gauss Box Deals store product associations as a linked list. We extract the product reference from each Deal, resolve it to the migrated Pipedrive Product UUID, and create a Deal-Product entry in Pipedrive. This requires Products to be migrated and validated before Deals can be fully closed with their product associations.

Gauss Box Deal, Lead, and Activity records carry owner assignments tied to Gauss Box user accounts. We map owner email addresses to Pipedrive User records by email match. Owners without a matching Pipedrive User go to a reconciliation queue for the customer's admin to provision before Deal and Activity import resumes. Inactive Gauss Box accounts should be deactivated before export to prevent orphaned owner records in the CSV.

Gauss Box's attribute-set system lets each account define custom fields on Contacts, Organizations, Deals, and Products. These are not standardized across accounts — a field called 'Region' on one Gauss Box account may not exist on another. We run a mandatory discovery phase to enumerate every active attribute set, create equivalent custom fields in Pipedrive (with appropriate field types: text, number, date, dropdown, checkbox), and then map the values during import. Fields that exist only in Gauss Box with no Pipedrive equivalent are created as custom fields or flagged for the customer's admin to decide.