CRM migration
Field-level mapping, validation, and rollback between Cetec ERP and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Cetec ERP
Source
Nutshell
Destination
Compatibility
7 of 9
objects map 1:1 between Cetec ERP and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Migrating from Cetec ERP to Nutshell is a CRM-focused extraction: most of Cetec's value lives in manufacturing modules (Work Orders, BOMs, Inspections, NCRs, inventory, and the Chart of Accounts) that have no equivalent object in Nutshell's sales-CRM data model. We extract the CRM-adjacent records—Customers, Contacts, and Sales Quotes—and map them into Nutshell's Companies, People, and Deals. We resolve the owner lookup and validate numeric fields against Cetec's spreadsheet-derived extracts before loading. Manufacturing data that cannot map—BOMs, Work Orders, Quality Records, Documents, Chart of Accounts—does not migrate silently; we deliver a written inventory enumerating every such object by Cetec table name with a description of its structure and recommended disposition so your team can configure Nutshell accordingly or archive to a document store.
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 Cetec ERP 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.
Cetec ERP
Customer
Nutshell
Company
1:1Cetec Customer records map to Nutshell Company records. The customer name, billing address, shipping address, phone, and website transfer directly. We use company name as the dedupe key during import. The internal customer flag (the company entity itself used for intercompany transactions) cannot be edited once linked to an order in Cetec; we map it to a Nutshell Company with a custom field cetec_internal__c = true and flag it in the reconciliation report as requiring admin review before it participates in deal lookups.
Cetec ERP
Contact (on Customer)
Nutshell
Person
1:1Contacts linked to Cetec Customers migrate to Nutshell People records with the parent Company resolved via the Customer-to-Company mapping. We map first name, last name, email address, phone number, job title, and the primary contact flag. Contact roles on Quotes (Buyer, Influencer, Economic Buyer) have no direct Nutshell equivalent; we store them in a custom field contact_role__c and recommend the admin configure Nutshell's Deal Contact Roles from the Pro tier if role attribution matters.
Cetec ERP
PQuote (Sales Quote)
Nutshell
Deal
1:1Cetec Sales Quotes map to Nutshell Deals. The quote number becomes the Deal name with a prefix (e.g., Q-2024-0042). The quote monetary value, status (open, accepted, declined, expired), and expiration date transfer. Quote approval thresholds from Cetec (dollar-value, PPV, LBV limits per user and global) have no Nutshell equivalent; we document them as metadata in the migration handoff so the admin can configure Nutshell Workflow conditions or a separate approval tool if approval routing is required.
Cetec ERP
Quote Line Item
Nutshell
Deal Product
1:manyCetec Quote line items map to Nutshell Deal Products or to a structured notes block on the Deal. If the destination Nutshell instance has the Products feature enabled, we create one Deal Product per line item with part number, description, quantity, unit price, and extended price. If Products are not configured, we append a formatted line-item table to the Deal notes field and flag it for the admin to reconstruct using Nutshell's built-in product library post-migration.
Cetec ERP
User (sales-facing)
Nutshell
User
1:1Cetec Users with CRM-facing roles (sales reps, account managers, quote owners) map to Nutshell Users by email address match. The $25/user/month shop floor role does not transfer to Nutshell because Nutshell does not have a production-access tier; we identify shop-floor-only users during scoping and exclude them from the User migration scope, reducing the Nutshell seat count relative to the Cetec user count.
Cetec ERP
Sales Order (open)
Nutshell
Deal (closed-won)
1:1Open Sales Orders in Cetec can be migrated as Nutshell Deals with status set to Won if the customer wants to preserve the customer relationship and monetary value in the CRM. Historical completed orders map as closed Deals with a custom field cetec_order_id__c carrying the original Cetec order number for cross-reference. We do not migrate order line-item fulfillment detail (which belongs in the ERP layer) but do preserve the order total, customer, and close date.
Cetec ERP
Part Number
Nutshell
Product
lossyCetec Part Numbers can be mapped to Nutshell Products if the customer wants a product catalog in Nutshell for quote line items. We extract part number, description, unit of measure, and standard cost. Pricing rules (vendor pricing, markup schedules) from Cetec's part master do not transfer; the admin rebuilds pricing in Nutshell's product pricing module. BOM structures (multi-level component relationships) have no Nutshell equivalent and are excluded from the standard migration scope.
Cetec ERP
Purchase Order
Nutshell
None (document only)
1:1Purchase Orders in Cetec ERP are vendor-facing supply chain records with no CRM equivalent in Nutshell. We export PO records as a structured CSV (PO number, vendor, line items, receipt status, date) and deliver it as a reference dataset alongside the migration. The customer's admin can store this in a document management tool or link it as a file attachment to the related Nutshell Company if vendor relationship context is needed on the CRM side.
Cetec ERP
Work Order
Nutshell
None (document only)
1:1Work Orders are the manufacturing execution record tying production scheduling, labor tracking, and cost accounting. They have no Nutshell equivalent. We export Work Order headers (WO number, part, status, scheduled dates, assigned labor) as a structured CSV reference dataset. If the customer maintains Nutshell Deals linked to Cetec Work Orders, we map the cetec_work_order__c reference field on the Deal and deliver a lookup table correlating Nutshell Deal IDs to Cetec WO numbers for cross-system reporting.
| Cetec ERP | Nutshell | Compatibility | |
|---|---|---|---|
| Customer | Company1:1 | Fully supported | |
| Contact (on Customer) | Person1:1 | Fully supported | |
| PQuote (Sales Quote) | Deal1:1 | Fully supported | |
| Quote Line Item | Deal Product1:many | Fully supported | |
| User (sales-facing) | User1:1 | Fully supported | |
| Sales Order (open) | Deal (closed-won)1:1 | Fully supported | |
| Part Number | Productlossy | Fully supported | |
| Purchase Order | None (document only)1:1 | Fully supported | |
| Work Order | None (document only)1: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.
Cetec ERP gotchas
Internal customer records lock after order commitment
Manufacturing Contact billing model not applicable but user pricing tiers matter
Spreadsheet-to-transformation migration pattern differs from direct API extraction
Build-and-ship versus build-to-stock dual fulfillment logic
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
Pre-migration audit and scope definition
We run a discovery audit against the Cetec ERP instance: record counts for Customers, Contacts, Quotes, Sales Orders, and open Purchase Orders; identification of custom bonus fields on Customer and Quote objects; identification of internal customer records and records with linked orders that prevent editing; count of distinct Users in CRM-facing roles versus shop-floor-only roles. We deliver a written scope document enumerating what migrates to Nutshell, what exports as reference data, and what has no migration path and receives a disposition recommendation.
Source data extraction and transform
We extract data from Cetec ERP using the same spreadsheet intermediate format that Cetec's own migration team uses. This gives us transformed, validated extract files familiar to Cetec support engineers and enables recurring refreshes before cutover. We apply custom field mapping (Cetec bonus columns to Nutshell custom fields), resolve the internal customer flag, and apply the dual-fulfillment consolidation logic to historical orders. Numeric fields are validated against Cetec account totals before the extract is marked import-ready.
Owner reconciliation and User provisioning
We extract every distinct Cetec User referenced on Customer (sales rep), Quote (owner), and Sales Order (sales rep) records and match by email against the Nutshell destination tenant's User table. Any Cetec User without a matching Nutshell User goes to a reconciliation queue for the admin to provision before record import resumes. We identify shop-floor-only Cetec users and exclude them from the Nutshell seat count to prevent pricing surprises.
Reference data export and disposition packaging
We export all non-migrated Cetec object classes (Purchase Orders, Work Orders, BOMs, Inspections, NCRs, Documents, Chart of Accounts, Quality Codes) as structured CSVs with column headers, row counts, and a data dictionary per table. We package these as a named reference dataset alongside the CRM migration and deliver a written inventory document mapping each Cetec table to a disposition recommendation. This ensures the customer has a complete record of their source data even though it cannot populate Nutshell.
Production migration in dependency order
We run production migration in record-dependency order: Nutshell Users (provisioned manually, validated), Companies (from Cetec Customers), People (from Cetec Contacts with CompanyId resolved), Deals (from Cetec Quotes and Sales Orders), Deal Products (from Quote Line Items), and reference data files (delivered as a named archive). Each phase emits a row-count reconciliation report before the next phase begins. We flag the internal customer records and the consolidated dual-fulfillment Deal lines explicitly in the phase report.
Cutover, validation, and handoff
We freeze Cetec writes during cutover and run a final delta migration of any records modified during the migration window. We deliver the reference data archive and the non-migrated object inventory to the customer. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not configure Nutshell Workflows or rebuild Cetec routing rules as Nutshell automations inside the migration scope; that is a separate engagement.
Platform deep dives
Cetec ERP
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 Cetec ERP 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
Cetec ERP: Not publicly documented in the CSV.
Data volume sensitivity
Cetec ERP exposes a bulk API — large-volume migrations stream efficiently.
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 Cetec ERP to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Cetec ERP 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 Cetec ERP
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.