Migrate from Zilliant CPQ to Salesforce Sales Cloud

Zilliant CPQ Products (the base entity, equivalent to ERP Materials) map to Salesforce Product2 records. Variant configuration rules (characteristic-based constraints for assemble-to-order and engineer-to-order workflows) map to Salesforce CPQ Option Constraints, Feature Groups, and Option Tags. We preserve the product hierarchy as Salesforce Product Family and map the ERP_ID column as a custom external ID field prod_erp_id__c for ERP cross-referencing during order fulfillment.

Zilliant CPQ Quotes map to Salesforce Quote (Sales Cloud standard object from Professional tier). Quote headers, line items (SalesItems), pricing calculations, and guided-selling context migrate. Historical Quote status states (Draft, Pending Approval, Approved, Lost, Won) map to Salesforce Quote Status values. We preserve Quote description and any structured pricing context in custom Quote fields. Quote PDFs and attachments migrate as ContentDocument linked to the Quote.

Zilliant CPQ SalesItems (the line-item subject type) map to Salesforce QuoteLineItem. Quantity, UnitPrice, Product2Id (resolved via SKU lookup), and any custom line-level fields migrate. Complex BOM (Bill of Materials) item configurations with nested quantity settings require recursive line expansion during transform. We preserve the BOM hierarchy as nested QuoteLineItem rows with a parent line reference.

Zilliant CPQ Price Lists (catalog, reference, global list, published, and matrix price types) map to Salesforce Pricebook2 records. The price type hierarchy and sequencing are preserved as Pricebook2 description fields and Pricebook isActive flags. Multi-currency Price Lists require explicit currency mapping from Zilliant's currency codes to Salesforce CurrencyIsoCode values during import.

Zilliant CPQ Price Items (linked to Products and Price Lists) map to Salesforce PricebookEntry. The ERP_ID column (id_col_quote_configuration_priceItems_erpId) may be hidden per-role via UI Profiles—we explicitly query hidden column data during extraction to preserve ERP cross-references that downstream order-fulfillment systems depend on. Price Item effective dates map to PricebookEntry UseStandardPrice and StartDate/EndDate fields.

Zilliant CPQ Sales Agreements (customer-specific pricing contracts with effective date ranges, discount tiers, and pricing overrides) map to Salesforce Contract records linked to the corresponding Account. Tiered pricing structures from Zilliant map to Contract Line Items or custom Price Agreement Line Item objects depending on the destination Salesforce CPQ edition. We preserve agreement status, renewal dates, and pricing override flags.

Zilliant CPQ Guided Selling rules (characteristic-based product rules driving guided selling flows and constraint-based configuration) are stored as structured rule packages, not individual records. We export them as a structured rule inventory document listing the rule name, trigger characteristics, constraint logic, and recommended Salesforce CPQ Option Constraint equivalent. The rules are not auto-migrated; they are documented for the customer's admin to rebuild using Salesforce CPQ's constraint model post-migration.

Zilliant CPQ Accounts (subject objects linked to Quotes and Opportunities) map to Salesforce Account. Standard and custom attributes migrate. Large account hierarchies with custom address structures require field-level mapping of address sub-fields (Street, City, State, PostalCode, Country) and Parent Account resolution. We resolve account references before Quote import to satisfy the lookup relationship.

Zilliant CPQ Contacts (subject objects with PartnerRoleRecord associations) map to Salesforce Contact. Contact-to-Account linkages and custom BDA fields migrate. Partner function records attached to contacts require additional mapping to Contact PartnerRole or a custom Contact Role field depending on the destination configuration.

BDAs are custom fields mapped between SAP C4C and Zilliant CPQ via lookup tables supporting String, Boolean, and Decimal types. List-type BDA fields store only the raw code value from C4C—C4C's localized display labels are not preserved in Zilliant CPQ. We flag every BDA field with list-type data during migration scoping, export both the code value and a reference to the C4C label source, and advise customers that translated labels must be re-established from C4C source records post-migration. BDA String and Decimal fields migrate as custom fields on the equivalent Salesforce object.

Zilliant CPQ User management includes domain-approval restrictions (users with unapproved email domains cannot sign in) and Role-based UI Profiles controlling field visibility (e.g., ERP_ID column). We extract user records and map to Salesforce User by email match. UI Profile role mappings that control ERP_ID visibility are documented as Salesforce Field-Level Security or Page Layout assignments for the customer's admin to reapply.

Zilliant CPQ attachment metadata (a known bug in pre-patch versions caused single clicks to trigger multiple downloads equal to the total attachment count) is preserved as ContentDocument metadata during extraction. We document the patch status of the source environment before migration. Attachments and Notes migrate as Salesforce ContentDocument records linked via ContentDocumentLink to the parent Quote, Account, or Contact.