Migrate your Zilliant CPQ data

Products are the primary CPQ entity and map directly to Material in ERP terminology. Standard and custom product attributes are available. We migrate product hierarchies and variant configuration rules as structured rule sets. ERP_ID cross-references are preserved to maintain downstream sync integrity.

Quotes represent the core output object in Zilliant CPQ. We migrate Quote headers, line items (SalesItems), pricing calculations, and guided-selling context. We flag historical Quote status states explicitly so closed/won/lost states map correctly to the destination.

Price Lists contain catalog, reference, global list, published, and matrix price types. We preserve the full price type hierarchy and sequencing. Multi-currency price lists require explicit currency mapping during migration.

Price Items are linked to Products and belong to Price Lists. ERP_ID column visibility can be toggled via UI Profiles system-wide or per-role—ERP cross-references may be hidden but are still present. We extract both visible and hidden ERP_ID fields to avoid orphaned pricing rows.

Sales Agreements store customer-specific pricing contracts. They contain effective date ranges, discount tiers, and pricing overrides. We map agreement structures to destination equivalents but tiered and scaled pricing logic may require field-level reconfiguration at the destination.

Product rules defined by characteristics drive guided selling flows and constraint-based configuration. These are stored as structured rules, not individual records. We export them as rule packages; destination systems without constraint-based configuration engines will need manual reimplementation.

BDAs are custom fields mapped between SAP C4C and CPQ via lookup tables supporting String, Boolean, and Decimal types. Localization of list-code values in C4C is not preserved in BDA—only the raw code is stored. We flag all BDA mappings for manual validation post-migration.

Accounts are subject objects in CPQ, linked to Quotes and Opportunities. They support standard and custom attributes. Large account hierarchies with custom address structures require field-level mapping during migration.

Contacts are subject objects with PartnerRoleRecord associations. We preserve contact-to-account linkages and custom BDA fields. Partner function records attached to contacts require additional mapping work.

Sales Items are the line-item subject type in CPQ, containing quantity, pricing, and product references. Complex BOM (Bill of Materials) item configurations with nested quantity settings require recursive extraction to preserve the full product structure.

Attachments and links in the Notes section of Quotes had a known bug where single-click downloads could trigger multiple downloads equal to the number of attachments—this was resolved in a recent patch. We migrate attachment metadata and links, but file binaries require separate file-transfer handling.

Zilliant CPQ supports standard pre-delivered attributes plus custom attributes via the CPQ schema. Custom field mapping between C4C and CPQ uses BDA lookup tables. We export custom field definitions and data but cannot guarantee equivalent custom-field capabilities at the destination.

User management includes domain-approval restrictions—users with unapproved email domains cannot sign in. Role-based UI Profiles control field visibility (e.g., ERP_ID column). We migrate user records and role assignments but domain-allowlist configuration must be replicated manually at the destination.