CRM migration
Field-level mapping, validation, and rollback between Verenia and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Verenia
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Verenia and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Verenia CPQ to Nutshell CRM is a CPQ-to-general-CRM migration, not a like-for-like platform swap. Verenia's guided-selling rules, bundle structures, and pricing constraint logic do not have native equivalents in Nutshell's CRM model. We extract Quote documents, Order records, Product catalog items, and Contact associations from whatever export artifacts the customer retained before Verenia's 2025 shutdown, map them into Nutshell's Leads, People, Companies, and Deals using custom fields to carry CPQ metadata, and deliver a written inventory of any configuration rules requiring manual rebuild in Nutshell's settings or a separate CPQ add-on. Nutshell's JSON-RPC API, custom field support, and per-user pricing model shape the migration architecture and timeline.
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 Verenia object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Verenia
Quote
Nutshell
Deal + Custom Fields
lossyVerenia Quotes map to Nutshell Deals with a set of custom fields carrying the CPQ quote metadata: total_amount, discount_percent, quote_date, and quote_number. Line items from Verenia decompose into Deal Product custom field rows or Notes attachments. Quote status (Draft, Sent, Accepted, Lost) maps to Nutshell's Deal status enum. The original Verenia quote PDF attaches to the Deal as a Nutshell File. Quote numbering sequences do not auto-transfer; we generate a cross-reference table mapping old quote IDs to new Deal IDs.
Verenia
Order
Nutshell
Deal + Custom Fields
1:1Verenia Orders map to Nutshell Deals with a distinct Deal status (e.g., Won) to separate them from open quotes. Order-level pricing, configuration metadata, and customer associations migrate as custom fields on the Deal. Closed-won Orders from Verenia carry their original close date preserved in a custom date field. Pending or in-progress orders carry their fulfillment state as a text custom field. Order configuration rules nested within orders require decomposition into individual field values or Notes.
Verenia
Product Configuration
Nutshell
Product + Custom Fields
1:manyVerenia product configurations encode guided-selling rules, bundle structures, and compatibility constraints. Nutshell does not have a guided-selling engine, so we extract configuration metadata as structured custom fields on Nutshell Product records: bundle_components, constraint_rules, pricing_tier, and configuration_options as JSON or text. The customer receives a written inventory of all configuration logic requiring manual rebuild in Nutshell's product settings or a separate CPQ tool.
Verenia
Product
Nutshell
Product (Nutshell Product object)
1:1Verenia Products map to Nutshell Product records with name, SKU, and pricing. Pricing tiers from Verenia's tiered pricing model (discount brackets, volume pricing) migrate as custom fields on the Product. Bundle parent products and their component relationships extract as separate Product records with a custom parent_product_id field linking them. Standard pricing list prices migrate to the Nutshell Product's base price field.
Verenia
Contact
Nutshell
People
1:1Verenia Contact records migrate to Nutshell People with standard field mapping: name, email, phone, company association. Custom contact properties migrate as Nutshell People custom fields. Company association resolves via the Verenia company lookup and maps to the corresponding Nutshell Company record. Standard field mapping applies; no transformation required for clean contact exports.
Verenia
Company/Account
Nutshell
Company
1:1Verenia Company records map directly to Nutshell Company records with name, address, industry, and website preserved. Company-to-Contact relationships are maintained through Nutshell's People-to-Company link. If the customer exported companies without contacts, Companies are loaded first to establish the relationship structure before People imports resolve the Company lookup.
Verenia
User
Nutshell
User
1:1Verenia User records associated with Quotes or Orders map to Nutshell User records by email match. Owner assignment on Verenia records migrates to the corresponding Nutshell User. If a Verenia Owner has no matching Nutshell User, the record holds in a reconciliation queue for the customer's admin to provision the User before final import. Inactive Verenia users map to inactive Nutshell users with the Owner reference preserved as a text field for audit.
Verenia
Attachment
Nutshell
File
1:1Quote PDFs, order confirmations, and configuration screenshots from Verenia's exported archives attach to the corresponding Nutshell Deal, People, or Company record via Nutshell's file model. File naming conventions vary across export artifacts; we normalize file paths and generate a file manifest mapping each attachment to its target Nutshell record ID. Files without a resolvable parent record attach to a dedicated migration artifact Company for retrieval.
| Verenia | Nutshell | Compatibility | |
|---|---|---|---|
| Quote | Deal + Custom Fieldslossy | Fully supported | |
| Order | Deal + Custom Fields1:1 | Fully supported | |
| Product Configuration | Product + Custom Fields1:many | Fully supported | |
| Product | Product (Nutshell Product object)1:1 | Fully supported | |
| Contact | People1:1 | Fully supported | |
| Company/Account | Company1:1 | Fully supported | |
| User | User1:1 | Fully supported | |
| Attachment | File1: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.
Verenia gotchas
Verenia CPQ is officially shut down as of 2025
No active API endpoints for live migration
Product configurations do not map 1:1 to other CPQ systems
Quote and order numbering sequences are not preserved by default
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Export artifact audit and scoping
We begin every Verenia migration by confirming what export artifacts the customer retained before the 2025 shutdown. This includes CSV downloads of Quotes, Orders, Products, Product Configurations, Contacts, and Companies; any integration log exports from NetSuite or other connected systems; and archived file stores containing Quote PDFs or configuration screenshots. We inventory the record counts, field coverage, and file completeness for each artifact and define a written migration scope. If no artifacts exist, we declare scope as manual re-entry and adjust pricing accordingly.
Nutshell tier assessment and custom field design
We assess the customer's target Nutshell plan. If the customer needs API access (for ongoing sync or integration), we recommend Enterprise at $79/user/month. We design the Nutshell custom field schema to carry CPQ metadata: custom fields on Deal for Quote and Order fields, custom fields on Product for pricing tier and configuration metadata, and custom fields on People for any Verenia contact properties. Custom fields deploy into a Nutshell sandbox or trial org for validation before production migration.
Configuration rule inventory
We extract Verenia's guided-selling rules, bundle constraints, and pricing logic from the exported product configuration records and document them in a written Configuration Rule Inventory. This document lists each rule, its trigger conditions, the affected products, and a plain-language recommendation for rebuilding it in Nutshell or a separate CPQ tool. We do not migrate these rules as executable logic; the rebuild is an admin task documented in the handoff package.
Staged migration in dependency order
We load data into Nutshell in dependency order: Companies first (to establish the Account hierarchy), then People (with Company lookup resolved), then Products (with pricing and configuration metadata), then Deals (with Quote and Order fields mapped, Deal ID cross-reference generated), then Files (attached to the corresponding Deal, People, or Company record). Each phase produces a row-count reconciliation report before the next phase begins. Owner assignment resolves via email match against Nutshell Users with unresolved owners held in a reconciliation queue.
Cutover, validation, and handoff
We run a final delta migration of any records modified during the artifact preparation window, then enable Nutshell as the system of record. We deliver the Configuration Rule Inventory, the Quote-Order-to-Deal cross-reference table, the file manifest, and the post-migration validation report showing record counts and any unresolved dependencies. We offer a one-week hypercare window to resolve reconciliation issues. We do not rebuild Verenia's guided-selling rules, workflow automations, or pricing constraint logic in Nutshell; that is documented for the customer's admin to handle as a separate configuration task.
Platform deep dives
Verenia
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Verenia and Nutshell.
Object compatibility
1 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
Verenia: Not applicable.
Data volume sensitivity
Verenia 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 Verenia to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Verenia to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Verenia
Other ways to arrive at Nutshell
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.