Migrate from Zilliant CPQ to HighLevel

Zilliant CPQ Account records map to GoHighLevel Companies. Standard and custom account attributes migrate as Company custom fields. Address structures with multi-location hierarchies map to GoHighLevel location sub-records. Account ownership resolves via email match against GoHighLevel Users during import.

Zilliant CPQ Contact records map directly to GoHighLevel Contacts. PartnerRoleRecord associations and PartnerFunctionRecord attachments on Zilliant Contacts require additional mapping to GoHighLevel custom contact role fields. Custom BDA fields on Contacts migrate as custom fields; note that C4C localized display labels for list-type BDA fields do not transfer—only raw code values carry over.

Zilliant CPQ Products (equivalent to ERP Materials) map to GoHighLevel Products with SKU, name, description, and price fields. Variant configuration rules and characteristic-based BOM structures do not transfer; we catalog them as a structured rule package and flag for manual product reconfiguration in GoHighLevel where variant complexity is handled via product bundles or manual options.

Zilliant Price List hierarchies (catalog, reference, global, published, matrix types) have no GoHighLevel equivalent object. We extract price list values and map them to GoHighLevel Product price fields and, for customer-specific pricing, to custom fields on the Company or Opportunity record. Multi-currency price lists require explicit currency mapping to GoHighLevel's currency settings.

Zilliant Price Items linked to Products and Price Lists carry ERP_ID cross-references that can be hidden via UI Profiles. We explicitly query hidden column data during extraction. Price Item values map to GoHighLevel Product pricing; ERP cross-references preserve in a custom field for downstream fulfillment system reconciliation but have no native use in GoHighLevel.

Zilliant CPQ Quotes map to GoHighLevel Opportunities. Quote headers, Sales Items (line items), and pricing calculations transfer as Opportunity records with line items as Opportunity Product entries. Historical Quote status states require mapping to GoHighLevel pipeline stage values. Guided-selling context attached to Quotes does not transfer automatically.

Zilliant Sales Agreements contain customer-specific pricing contracts with effective date ranges and discount tiers. We migrate the contract header and tier structure as a GoHighLevel custom object. Each agreement tier maps to a custom Agreement Line Item record. GoHighLevel does not enforce agreement-based pricing automatically; the customer's admin applies agreement pricing manually to Opportunities or uses custom field lookups and automations to simulate contract pricing.

Zilliant Guided Selling Rules are structured rule packages driven by characteristic-based product constraints. These are configuration artifacts, not individual records, and have no GoHighLevel equivalent. We export them as a written rule catalog (trigger conditions, constraint logic, recommended action) and the customer's admin rebuilds the steering logic using GoHighLevel Workflows and conditional actions.

Zilliant BDAs are custom fields mapped from SAP C4C via lookup tables supporting String, Boolean, and Decimal types. BDA field definitions and values migrate as GoHighLevel custom fields on the appropriate object. List-type BDA fields carry only the raw code value; C4C localized display labels are lost and require re-establishment from C4C source records post-migration.

Zilliant CPQ Users map to GoHighLevel Users by email match. Domain-approval restrictions on Zilliant Users (email domains requiring approval) have no GoHighLevel equivalent; we flag these for manual review during GoHighLevel user provisioning. Role-based UI Profiles controlling field visibility (e.g., ERP_ID column) do not transfer.