Migrate from Zilliant CPQ to Pipedrive

Zilliant Products map to Pipedrive Products. The ERP_ID cross-reference column (id_col_quote_configuration_priceItems_erpId) migrates as a custom Product field erp_id__c to preserve the link to SAP or other ERP materials records. We explicitly query hidden column data during extraction because UI Profiles may suppress ERP_ID visibility system-wide or per-role. Product hierarchies flatten into Pipedrive Product nested groups rather than a multi-level parent BOM model.

Zilliant Price Lists (catalog, reference, global, published, matrix) do not have a direct Pipedrive equivalent. We extract the active catalog price for each Product and write it to a Pipedrive Product custom field list_price__c. Reference prices and matrix prices migrate as additional custom fields (reference_price__c, matrix_price__c). The Price List hierarchy itself is documented as a written artifact for the customer's admin to configure in Pipedrive's Product pricing settings.

Zilliant Quotes map to Pipedrive Deals. The Quote header (quote number, date, status, account reference, total price) becomes Deal fields plus custom fields for pricing breakdown (discount, tax, shipping). Quote status states that do not map to standard Pipedrive stages are added as custom stage values. We preserve the guided-selling context from the Quote by storing rule-set identifiers as text fields for manual review.

Zilliant SalesItems (line items) map to Pipedrive Deal Products using the Product lookup resolved from the Product migration step. Quantity, unit price, and line-total migrate as Deal Product fields. Complex BOM configurations with nested quantity settings are flattened to a single line per component with a custom bom_level__c field for audit. Guided-selling constraint outcomes are noted in a custom field.

Zilliant Sales Agreements with effective date ranges, discount tiers, and pricing overrides have no native Pipedrive equivalent. We model each Agreement as a Pipedrive Deal with a deal_type__c custom field set to 'sales_agreement', start_date__c and end_date__c fields, and tiered pricing captured in a JSON-structured custom field agreement_tiers__c. The customer's admin decides whether to create one Deal per agreement or to attach agreement terms as Deal notes.

Zilliant Accounts map to Pipedrive Organizations. Standard and custom attributes migrate as Organization custom fields. Large account hierarchies with custom address structures require field-level mapping of the address sub-fields (street, city, state, postal_code, country). The ERP_ID on Zilliant Account migrates as org_erp_id__c on the Organization.

Zilliant Contacts map to Pipedrive Persons. We preserve the contact-to-account linkage by resolving the Organization ID at migration time and linking the Person to it. PartnerRoleRecord associations attached to contacts migrate as custom fields (partner_role__c) or as a Person note entry. Custom BDA fields on Contact migrate as Person custom fields.

BDAs mapped from SAP C4C support String, Boolean, and Decimal types. List-type BDA fields store only the raw C4C code value, not the localized display label—this localization loss is a known characteristic of Zilliant's BDA architecture and is documented explicitly. We flag every list-type BDA during scoping and advise the customer that translated labels must be re-established from C4C source records post-migration. Boolean and Decimal BDAs migrate directly as typed Pipedrive custom fields.

Zilliant Guided Selling rules are structured rule packages stored in the CPQ ontology, not individual records. We export them as a written rule package documenting each rule's trigger, conditions, and product configuration outcome. Pipedrive's automation layer (trigger-action rules) does not replicate constraint-based configuration logic, so the rules are handed off as documentation for the customer's admin to rebuild as workflow rules or to address via a CPQ add-on from the Pipedrive Marketplace.

Zilliant Users map to Pipedrive Users by email match. Domain-approval restrictions in Zilliant CPQ (unapproved email domains cannot sign in) have no Pipedrive equivalent; we flag any user records with non-standard domain restrictions for the customer's admin to validate post-migration. Role-based UI Profiles controlling field visibility (e.g., ERP_ID column) are documented as a written access-control artifact.

Quote attachments migrate to Pipedrive Deal files. A resolved bug in pre-patch Zilliant builds caused single-click downloads to trigger multiple downloads equal to the total attachment count. We verify the source environment's patch status during scoping and note any discrepancy between the intended attachment count and what was recorded in the export. Attachments associated with Quote records attach to the corresponding migrated Deal.