CRM migration
Field-level mapping, validation, and rollback between Zilliant CPQ and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Zilliant CPQ
Source
monday CRM
Destination
Compatibility
7 of 10
objects map 1:1 between Zilliant CPQ and monday CRM.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Zilliant CPQ to Monday.com CRM is a migration between fundamentally different product paradigms. Zilliant CPQ is a purpose-built manufacturing and B2B distribution tool with AI-powered pricing optimization, guided-selling flows, constraint-based variant configuration, and native ERP integration. Monday.com CRM is a visual board-based work OS that tracks deals, contacts, and pipelines but has no native CPQ engine, no guided-selling rule engine, and no native ERP connector. We migrate the record data—Products, Accounts, Contacts, Quote headers and line-item context, Price List structure, and Sales Agreements—as Monday.com board items and custom fields. We explicitly do not migrate Groovy scripted logic, constraint-based configuration rules, or BDA lookup tables because these have no Monday.com equivalent and would require reimplementation regardless. We deliver a written inventory of every active guided-selling rule, pricing matrix, and Groovy script for the customer's admin to rebuild as Monday.com automations or separate CPQ tooling post-migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Zilliant CPQ object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Zilliant CPQ
Product
monday CRM
Item or Custom Table
1:1Zilliant Products (the base CPQ entity, equivalent to ERP Materials) map to Monday.com Items in a Products board or to a Custom Table with typed columns matching the source product attributes. Variant configuration rules are not migratable; we document them as a rule package and flag for manual reimplementation as Monday.com dropdown or checkbox column options. ERP cross-references stored in the ERP_ID column are preserved as custom text fields in the destination.
Zilliant CPQ
Quote
monday CRM
Item (board-based)
1:1Zilliant Quotes map to Monday.com Items in a Quotes board. Quote header fields (Quote number, status, dates, total price) migrate as standard or custom columns. Line-item pricing from SalesItems migrates as repeating group entries or as a linked Items table. Matrix pricing and agreement overrides are stored as field values; the underlying pricing logic (catalog, matrix, agreement, override) is noted as a structural difference. Monday.com does not generate PDF quotes natively—this is a post-migration manual step or third-party automation.
Zilliant CPQ
Account
monday CRM
Contact or Company (Monday.com CRM Contact type)
1:1Zilliant Accounts migrate to Monday.com CRM Contacts with company association. Large account hierarchies with custom address structures require field-level mapping of billing address, shipping address, and custom BDA fields to Monday.com custom fields. Partner function records attached to accounts are mapped to tags or custom dropdown fields.
Zilliant CPQ
Contact
monday CRM
Contact (Monday.com CRM Contact type)
1:1Zilliant Contacts migrate to Monday.com CRM Contacts with preserved contact-to-account linkages. BDA custom fields from SAP C4C map to Monday.com custom fields; list-type BDA values lose C4C localization and migrate as raw code values. PartnerRoleRecord associations on contacts require additional mapping to Monday.com tags or custom fields.
Zilliant CPQ
Price List
monday CRM
Custom Table or Item board
1:manyZilliant Price Lists (catalog, reference, global list, published, and matrix price types) split into multiple Monday.com Items or a Price Lists Custom Table. Each price type becomes a separate column set or board. Multi-currency price lists require explicit currency mapping to Monday.com currency columns; Monday.com CRM supports multi-currency on paid plans.
Zilliant CPQ
Price Item
monday CRM
Custom Table row
1:1Zilliant Price Items linked to Products and Price Lists migrate to Custom Table rows with the ERP_ID column explicitly queried (even if hidden via UI Profiles) to preserve ERP cross-references. Unit price, currency, effective dates, and price type migrate as typed columns. Tiered pricing structures require one row per tier.
Zilliant CPQ
Sales Agreement
monday CRM
Item (Agreements board) or Custom Table
1:1Zilliant Sales Agreements (customer-specific pricing contracts with effective date ranges, discount tiers, and overrides) migrate to an Agreements board or Custom Table in Monday.com. Agreement headers map to Item columns; tiered discount structures require one row per tier level. Monday.com does not enforce agreement-based pricing automatically—this requires manual application or a custom automation.
Zilliant CPQ
Guided Selling Rules
monday CRM
No direct equivalent (documentation only)
lossyZilliant guided-selling flows and constraint-based configuration rules are configuration artifacts, not data records. They cannot migrate automatically. We export them as structured rule packages documenting the characteristic-based logic, constraint conditions, and recommended guided-selling actions. The customer's admin rebuilds these as Monday.com automations (if simple) or adopts a dedicated CPQ add-on for complex configuration needs.
Zilliant CPQ
Business Data Attributes (BDAs)
monday CRM
Custom fields on Items or Contacts
lossyZilliant BDAs (custom fields mapped from SAP C4C via lookup tables, supporting String, Boolean, and Decimal types) map to Monday.com custom fields on the relevant board item or Contact. List-type BDA fields store only the raw C4C code value—localized display labels are lost and must be re-established from C4C source records post-migration. We flag every BDA field during scoping to ensure the customer knows which label sets require re-entry.
Zilliant CPQ
User
monday CRM
Team Member
1:1Zilliant Users map to Monday.com Team Members by email match. Domain-approval restrictions on Zilliant user accounts do not apply in Monday.com, which uses workspace-based permissions. Role-based UI Profiles in Zilliant (controlling field visibility such as the ERP_ID column) map to Monday.com permission sets per board or per workspace.
| Zilliant CPQ | monday CRM | Compatibility | |
|---|---|---|---|
| Product | Item or Custom Table1:1 | Fully supported | |
| Quote | Item (board-based)1:1 | Fully supported | |
| Account | Contact or Company (Monday.com CRM Contact type)1:1 | Fully supported | |
| Contact | Contact (Monday.com CRM Contact type)1:1 | Fully supported | |
| Price List | Custom Table or Item board1:many | Fully supported | |
| Price Item | Custom Table row1:1 | Fully supported | |
| Sales Agreement | Item (Agreements board) or Custom Table1:1 | Fully supported | |
| Guided Selling Rules | No direct equivalent (documentation only)lossy | Mapping required | |
| Business Data Attributes (BDAs) | Custom fields on Items or Contactslossy | Mapping required | |
| User | Team Member1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Zilliant CPQ gotchas
Groovy scripted logic does not export as data
ERP_ID column may be hidden but still critical
SAP characteristic labels can duplicate after legacy migration
BDA list-type fields lose C4C localization
Attachment downloads could fire multiple times on older builds
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and Zilliant environment audit
We audit the Zilliant CPQ environment across Products (standard and variant configuration), Quotes (headers and line items), Price Lists and Price Items (including hidden ERP_ID columns), Sales Agreements, Accounts, Contacts, and active BDA field definitions. We catalog every active Groovy script and guided-selling rule. We extract record counts by object type and identify BDA fields with list-type data from SAP C4C. The discovery output is a written migration scope, a data-cleaning checklist, and a Groovy-script inventory document.
Monday.com board design and column mapping
We design the Monday.com CRM board structure to receive the Zilliant data. This includes creating Boards (Quotes, Products, Accounts, Contacts, Agreements, Price Lists), defining standard and custom columns typed to match Zilliant field values, configuring multi-currency columns if needed, and setting up Contact types for the CRM. We pre-create custom fields for BDA attributes and ERP cross-references. Schema design happens in the customer's Monday.com workspace before any data import begins.
Data cleaning and deduplication
We run a data-quality pass on Zilliant exports before import. This includes deduplication of duplicate Accounts and Contacts (by name and domain), normalization of address formats, removal of orphaned Price Items with missing Product links, and deduplication of SAP characteristic labels if the source environment predates the relevant Zilliant patch. We flag BDA list-type fields for the customer so that C4C localization re-entry is planned post-migration. The cleaning output is a reconciled export set with a record-count baseline for post-migration verification.
Dependency-ordered import into Monday.com
We run imports in dependency order: Accounts first (as Monday.com Contacts with company association), then Contacts, then Products, then Price Lists and Price Items, then Agreements, then Quotes. ERP_ID values on Price Items are inserted as text columns. Sales Agreement tiers insert as separate rows in an Agreements Custom Table. Each phase emits a row-count reconciliation report. Monday.com's API handles rate limiting with exponential backoff and batch chunking.
Groovy script and guided-selling rule handoff
We deliver a written inventory of every active Groovy script (with full logic text) and every guided-selling rule (with constraint conditions, characteristic mappings, and recommended automation logic). This document is the handoff artifact for the customer's admin team or a Monday.com automation specialist to rebuild Zilliant behaviors as Monday.com automations or as part of a separate CPQ adoption. We do not rebuild these as part of the standard migration scope.
Cutover, validation, and post-migration handoff
We freeze Zilliant writes during cutover, run a final delta import of any records modified during the migration window, then verify Monday.com record counts against the baseline. We walk the customer's team through the imported board structure, the custom field mapping, and the limitations documented in the gotchas. We deliver the Groovy-script and guided-selling rule handoff documents, the automation rebuild recommendation list, and a one-week hypercare window for reconciliation issues. We do not provide ongoing Monday.com admin support, training, or automation rebuild as part of the standard migration scope.
Platform deep dives
Zilliant CPQ
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Zilliant CPQ and monday CRM.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Zilliant CPQ: Not publicly documented.
Data volume sensitivity
Zilliant CPQ doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Zilliant CPQ to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Zilliant CPQ to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Zilliant CPQ
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
