CRM migration
Field-level mapping, validation, and rollback between Total Control Pro and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Total Control Pro
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Total Control Pro and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Total Control Pro to Nutshell is a focused data migration, not a full platform replacement. Total Control Pro is a cloud MRP and MES platform built for SME discrete manufacturers; it does not publish a public REST or bulk API, which means all data export requires manual CSV extraction or a vendor-provided database export. Nutshell is a B2B CRM that uses Accounts, People, Leads, Deals, and Activities as its core objects, with no native support for manufacturing data such as Work Orders, Bills of Materials, production schedules, or Manufacturing Intelligence KPIs. We scope the migration to the records that make business sense in a CRM: customer Accounts and People, product records, supplier contacts, and any custom fields your team added during Total Control Pro implementation. Manufacturing data remains in Total Control Pro or moves to a dedicated MES platform. We flag automation and workflow rules for manual rebuild and do not migrate attachments as a standard scope item.
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 Total Control Pro 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.
Total Control Pro
Customer
Nutshell
Account and Person
1:manyTotal Control Pro Customer records (with contact details, account terms, and associated sales order references) split into Nutshell Account (the company or business entity) and Person (the individual contact at that company). The primary contact name from Total Control Pro becomes the first Person record; any secondary contacts from the same customer account become additional Person records linked to the same Account. We use the company name as the Account name and preserve account terms and payment terms in a custom field on the Account record.
Total Control Pro
Product
Nutshell
Product
1:1Total Control Pro Product definitions (part numbers, descriptions, unit of measure, and standard cost) map to Nutshell Product records. Part number maps to Product Code. We create Standard Price Book entries during import so that Products are immediately available on Deals. BOM component relationships do not map to Nutshell because Nutshell Products do not have a BOM structure; we deliver a separate BOM inventory document listing each product's components for manual reference.
Total Control Pro
Supplier
Nutshell
Account
1:1Total Control Pro Supplier records (with part supply links, lead times, and associated purchase item assignments) map to Nutshell Account records tagged with a custom Account Type field of 'Vendor'. We preserve supplier lead times and the associated purchase item links in custom fields on the Account. Nutshell does not have a native vendor object, so the vendor classification uses a custom dropdown field we create during schema setup.
Total Control Pro
Custom Fields
Nutshell
Custom Fields
lossyWe enumerate every user-defined field in Total Control Pro during the discovery call and create equivalent custom fields in Nutshell during schema setup. Nutshell supports text (225 character max), long text, currency, date, checkbox, dropdown (single-select), and multi-select types. We map field types where possible; fields with data types not supported by Nutshell (such as complex manufacturing-specific formats) are flagged and delivered as structured CSV for manual entry or external BI use.
Total Control Pro
Attachments
Nutshell
Not migrated
1:1Total Control Pro stores document attachments (drawings, SOPs, inspection images) in its own file store without a documented export endpoint. We flag these for manual transfer and document the file store structure during discovery so the customer's team can copy attachments to a shared drive or document management system post-migration. We do not migrate attachments as a standard scope item.
Total Control Pro
Work Orders
Nutshell
Not migrated
1:1Total Control Pro Work Orders carry operational status, assigned operations, and timestamps. Nutshell has no Work Order or job record equivalent. Work Orders remain in Total Control Pro or migrate to a dedicated MES platform. We deliver a written Work Order inventory summarizing open, in-progress, and closed work orders as of the migration cutoff date for reference in the destination system.
Total Control Pro
Bills of Materials
Nutshell
Not migrated
1:1Total Control Pro Bills of Materials have multi-level structures with revision numbers. Nutshell Products do not support BOM hierarchies. We deliver a BOM inventory document listing each product's active revision, component part numbers, quantities, and routing as of migration cutoff. The customer recreates BOMs in their MES or ERP if needed.
Total Control Pro
Manufacturing Intelligence KPIs
Nutshell
Not migrated
1:1The Manufacturing Intelligence Module stores calculated KPIs (OEE, cycle time, scrap rates) in a proprietary time-series format not exposed in standard Total Control Pro exports. These metrics are manufacturing-operation-specific and have no CRM equivalent in Nutshell. We deliver a targeted MIM export as a structured CSV alongside the transactional migration for ingestion into the customer's BI or reporting tool.
| Total Control Pro | Nutshell | Compatibility | |
|---|---|---|---|
| Customer | Account and Person1:many | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Supplier | Account1:1 | Fully supported | |
| Custom Fields | Custom Fieldslossy | Mapping required | |
| Attachments | Not migrated1:1 | Not supported | |
| Work Orders | Not migrated1:1 | Fully supported | |
| Bills of Materials | Not migrated1:1 | Mapping required | |
| Manufacturing Intelligence KPIs | Not migrated1:1 | Mapping required |
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.
Total Control Pro gotchas
No documented public API for data export
BOM revision history requires explicit scoping
Manufacturing Intelligence Module KPIs stored as opaque time-series
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
Discovery and vendor cooperation request
We conduct a scoped discovery call with the customer to enumerate Total Control Pro modules in use, record volumes per module (Customers, Products, Suppliers, custom fields), any active Work Orders or production schedules at migration time, and any BOM revision history requiring cleanup. We simultaneously request a vendor cooperation letter from Total Control Pro requesting CSV exports scoped to the enumerated modules. If the vendor does not respond within five business days, we scope the migration to UI-available CSV exports and adjust the timeline accordingly.
Schema design and Nutshell custom field creation
We design the Nutshell destination schema before any data import. This includes creating custom fields on Account, Person, and Lead objects to carry Total Control Pro data that does not map to standard Nutshell fields. We configure the Account Type dropdown to include a 'Vendor' value for supplier records. We set up any lookup relationships between Account and Person that require cross-object validation. Schema is validated in Nutshell's test environment before production migration begins.
CSV export processing and data mapping
We process the CSV exports from Total Control Pro in dependency order. Account records (derived from Customers and Suppliers) are cleaned and deduplicated first. Person records are extracted from Customer contacts and linked to their parent Account. Product records are extracted and prepared with Standard Price Book entries. Custom field data is mapped to the Nutshell custom fields created in schema setup. Any records that fail validation (missing required fields, duplicate Account names) are placed in a reconciliation queue for the customer to resolve before re-import.
Sandbox migration and reconciliation
We run a full migration into Nutshell's test environment using production-like data volume. The customer's team reconciles record counts (Accounts in, People in, Products in), spot-checks 25-50 random records against the source CSV exports, and verifies that Account-Person relationships and custom field values migrated correctly. Any mapping corrections and reconciliation resolutions happen in the test environment before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Customers and Suppliers), People (with AccountId resolved), Products (with Price Book entries created), and custom field values on all records. Each phase emits a row-count reconciliation report before the next phase begins. We freeze Total Control Pro writes during cutover to prevent delta records from being missed.
Cutover, validation, and handoff
We enable Nutshell as the system of record after final reconciliation. We deliver the written BOM inventory, Work Order summary, and MIM KPI export as separate CSV files for the customer's reference. We deliver an automation and workflow inventory document listing any automation rules or integrations in Total Control Pro that require rebuild in Nutshell. We support a one-week post-migration window to resolve any data quality issues identified by the customer's sales team.
Platform deep dives
Total Control Pro
Source
Strengths
Weaknesses
Nutshell
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 Total Control Pro and Nutshell.
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
Total Control Pro: Not publicly documented — typical SaaS limits assumed and confirmed during scoping..
Data volume sensitivity
Total Control Pro 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 Total Control Pro to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Total Control Pro 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 Total Control Pro
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.