Migrate from Zilliant CPQ to Odoo CRM

Zilliant Products map to Odoo Product Templates with variant configurations handled via Product Attributes and Variants. The Zilliant product hierarchy (parent-child relationships) maps to Odoo's internal category structure and optional subcategory fields. Custom product attributes from Zilliant BDAs map to Odoo custom fields on product.template. Multi-variant products with characteristic-based configuration in Zilliant require a pre-migration review of the attribute set because Odoo generates variants as separate records from attribute combinations rather than as nested configuration rows.

Zilliant Quotes map to Odoo Sale Orders. Quote headers migrate as sale.order records; Sales Items migrate as sale.order.line records. Quote status states (Draft, Pending Approval, Approved, Lost) map to Odoo sale.order state values (draft, sent, sale, cancel) with a custom field quote_original_status__c preserving the Zilliant lifecycle stage. Historical signed quotes migrate as sale.order records locked to the original status without triggering Odoo's confirmation workflow.

Zilliant Price Lists (catalog, reference, global list, published, matrix) map to Odoo Pricelists. Catalog price types map to Odoo Public Pricelists; agreement pricing maps to Customer Pricelists linked to res.partner records. Matrix pricing with multiple dimension rules requires decomposition into Odoo Pricelist Rules with computed discount or minimal-price logic. Multi-currency Price Lists in Zilliant map to Odoo Pricelist records with the currency_id set per Pricelist.

Zilliant Price Items link to Products and belong to Price Lists. The ERP_ID cross-reference column (id_col_quote_configuration_priceItems_erpId) is explicitly queried even when UI Profiles hide it from the Zilliant interface. ERP_ID values migrate to a custom field zilliant_erp_id__c on Odoo's product.pricelist.item for downstream order-fulfillment integration. Price Item effective date ranges map to Odoo Pricelist Item date_start and date_end fields.

Zilliant Sales Agreements with customer-specific pricing, effective date ranges, and discount tiers map to Odoo Sale Subscriptions (if the customer licenses the Subscription app) or to Customer Pricelists with manual discount rules. Tiered discount structures in Zilliant Sales Agreements require decomposition into multiple Pricelist Rules in Odoo because Odoo does not natively support quantity-threshold tiering on Customer Pricelists without the Subscription module. We flag the module requirement during scoping.

Zilliant Accounts map to Odoo res.partner records with the company type (customer, company) set per record. Large account hierarchies with custom address structures migrate as partner records with parent_id set to the hierarchy parent and address fields standardized to Odoo's street, street2, city, state_id, zip, country_id format. Partner-specific pricing from Zilliant Sales Agreements links to res.partner via a dedicated Customer Pricelist.

Zilliant Contacts map to Odoo res.partner records with type=contact and a parent_id linking to the company Partner record. PartnerRoleRecord associations on Zilliant Contacts migrate to Odoo res.partner records with the role captured in a custom field contact_role__c. Custom BDA fields on Zilliant Contacts map to custom fields on res.partner with type-mapped values (String to char, Boolean to boolean, Decimal to float).

Zilliant Guided Selling rules (characteristic-based constraints on product configuration) are stored as structured rule packages that we export as JSON documentation with product family groupings, constraint logic, and dependency chains. Odoo has no native guided selling or constraint-based configuration engine. We deliver the rule package as a written specification that the customer's Odoo developer or functional consultant uses to implement configuration logic in Python, Odoo Studio, or a custom addon. Rules do not migrate as executable code.

Business Data Attributes from Zilliant CPQ map to Odoo custom fields. String-type BDAs map to ir.model.fields with ttype=char; Boolean BDAs to ttype=boolean; Decimal BDAs to ttype=float. C4C localized display labels on list-type BDA fields are not preserved in Zilliant CPQ—only the raw list code value transfers. We flag every list-type BDA during scoping and advise customers to re-establish translated labels from C4C source records after migration. The field mapping document specifies the Odoo field name, type, and any required validation.

Zilliant Users map to Odoo res.users records. We resolve users by email match. Domain-approval restrictions in Zilliant (unapproved email domains blocking sign-in) map to Odoo's allowed_company_ids and multi-company access rules. UI Profile field visibility settings in Zilliant do not have a direct Odoo equivalent; we document them as Odoo field-level access rules for the customer's admin to implement in Settings > Users > Access Rights.

Zilliant Quote attachments migrate as Odoo ir.attachment records linked to the sale.order via res_model=sale.order and res_id=the sale.order ID. Notes in the Zilliant Notes section migrate as Odoo mail.message records on the sale.order chatter. A documented Zilliant bug (resolved in a recent patch) caused single-click attachment downloads to trigger multiple downloads on older builds—customers should verify their source environment patch status before migration to determine whether attachment count metadata reflects intentional uploads or the bug artifact.

Zilliant Sales Items map to Odoo sale.order.line records with product_id resolved from the Product Template migration, product_uom_qty from quantity, and price_unit from the Zilliant Price Item calculation. Complex BOM item configurations with nested quantity settings require recursion depth analysis during scoping because Odoo's BOM explosion in the Manufacturing app may not automatically replicate the same nested structure. We flag BOM recursion depth and recommend a manual BOM rebuild verification step before production migration.