Migrate from Zilliant CPQ to Zoho CRM

Zilliant Products map directly to Zoho CRM Products. The Zilliant product hierarchy (parent-product relationships) migrates as Product Category or as a parent-to-child relationship via a custom lookup field on Product. Variant configuration rules (characteristic-based constraint logic) are exported as structured rule packages; Zoho CPQ's Product Rules handle the guided-add and suggestion logic, but the constraint enforcement (which combinations are valid) requires reimplementation in Zoho or a third-party CPQ connector. We flag constraint rule packages in the handoff document.

Zilliant Quote headers map to Zoho CRM Quotes. The Quote status (Draft, Active, Revised, Accepted, Lost) migrates to Zoho Quote Status. Quote validity dates map to Valid Till. The Zilliant Quote owner (sales rep) resolves to a Zoho CRM User by email match. Any Quote PDF attachments migrate as ContentDocument records linked to the Quote.

Zilliant Sales Items (line items with quantity, pricing, and product references) map to Zoho Quote line items. Complex BOM item configurations with nested quantity settings require recursive expansion before import; we flatten multi-level BOM structures into individual Quote line items with a custom field bom_parent__c to preserve the hierarchy. Zoho's CPQ module handles dynamic quantity updates per the base product selection.

Zilliant Price Lists (catalog, reference, global list, published, matrix types) map to Zoho Price Books. The price type hierarchy and sequencing migrate as Price Book names and ordering. Multi-currency Price Lists in Zilliant require explicit currency mapping in Zoho CRM before Price Book import because Zoho stores currency on the Price Book level. We run a currency validation pass before Price Book import.

Zilliant Price Items linked to Products within Price Lists map to Zoho Product pricing records. The ERP_ID column on Price Items may be hidden via UI Profiles in Zilliant; we explicitly query hidden column data during extraction to preserve the ERP cross-reference layer that downstream order-fulfillment systems depend on. The ERP_ID value migrates as a custom field erp_id__c on the Zoho Product record.

Zilliant Sales Agreements store customer-specific pricing contracts with effective date ranges, discount tiers, and pricing overrides. Zoho CRM has no native Sales Agreement equivalent. We migrate agreement structures as extended-validity Quotes (using Quote Valid Till and custom date fields for effective_start__c and effective_end__c) or as a custom Agreement module that we provision in Zoho during schema setup. Tiered pricing tiers in Sales Agreements require translation to Zoho Price Rules with customer-specific conditions. The customer selects the strategy during scoping.

Zilliant Accounts map directly to Zoho CRM Accounts. Large account hierarchies with custom address structures require field-level mapping review because Zilliant's address model supports multi-level shipping addresses (plant, warehouse, dock) that Zoho stores as a flat address with custom fields. We flag address structure mismatches during scoping and recommend a custom address module or a related Addresses module if the customer requires multi-level shipping locations.

Zilliant Contacts map to Zoho CRM Contacts with PartnerRoleRecord associations preserved. Contact-to-Account linkage migrates via AccountId lookup. Custom BDA fields on Contacts require field-level mapping because BDAs store raw list-code values without C4C localized labels. We flag BDA list-type fields during scoping and advise that translated labels must be re-established from C4C source records post-migration.

Zilliant Users migrate to Zoho CRM Users. Domain-approval restrictions in Zilliant (unapproved email domains cannot sign in) map to Zoho's user provisioning restrictions. We resolve Zilliant users by email match against the Zoho destination org. Any user without a matching Zoho User record goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Zilliant attachment metadata migrates to Zoho CRM Attachments or ContentDocument records linked to the parent Quote or Account. A documented Zilliant bug in pre-patch versions caused single clicks on attachment items to trigger multiple downloads; we verify the source environment patch status during scoping to determine whether the attachment metadata is reliable. Customers on older builds with unreliable attachment metadata receive a flagged handoff note recommending a manual attachment audit post-migration.

Zilliant BDA custom fields mapped from SAP C4C (String, Boolean, Decimal types) migrate to Zoho CRM custom fields on the relevant module. List-type BDA fields carry only the raw list code value from C4C; the localized display label is not preserved in Zilliant. We flag every BDA list-type field during scoping and recommend that the customer re-imports translated label sets from C4C after migration as a separate data-cleanup task. BDA fields that reference C4C lookup tables require custom field creation in Zoho before import.