CRM migration

Migrate from Total Control Pro to Nutshell

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 logo

Total Control Pro

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Total Control Pro and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Total Control Pro logo

Total Control Pro

What's pushing teams away

  • No publicly documented REST or bulk API for third-party integration; data movement depends on CSV exports or direct cooperation from the vendor, which limits the integration ceiling for growing operations.
  • Reviewers report bugs during implementation, particularly when requesting newly built or custom features, and describe slow turnaround on feature development requests (Capterra UK).
  • TotalControlPro is a small company (~14 employees per ZoomInfo); support bandwidth is finite, and customers needing guaranteed enterprise SLAs may outgrow the vendor's coverage.
  • Pricing is not transparently published beyond a £15–£25/user/month starting point; full quotes depend on services, integrations, and onboarding, making procurement comparisons harder against listed competitors.
  • Heavily regulated manufacturing (medical device, aerospace primes beyond engine-tier suppliers) often requires formal audit-trail compliance documentation that the platform does not pitch as a core capability.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Total Control Pro objects map to Nutshell

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

maps to

Nutshell

Account and Person

1:many
Fully supported

Total 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

maps to

Nutshell

Product

1:1
Fully supported

Total 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

maps to

Nutshell

Account

1:1
Fully supported

Total 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

maps to

Nutshell

Custom Fields

lossy
Mapping required

We 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

maps to

Nutshell

Not migrated

1:1
Not supported

Total 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

maps to

Nutshell

Not migrated

1:1
Fully supported

Total 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

maps to

Nutshell

Not migrated

1:1
Mapping required

Total 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

maps to

Nutshell

Not migrated

1:1
Mapping required

The 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.

Gotchas + challenges

What specifically takes care here

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 logo

Total Control Pro gotchas

High

No documented public API for data export

Medium

BOM revision history requires explicit scoping

Medium

Manufacturing Intelligence Module KPIs stored as opaque time-series

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Total Control Pro has no documented public API

    Total Control Pro does not publish a public REST or bulk API for third-party data extraction. All data export must be performed through manual CSV exports from the platform UI or through direct database queries requiring credentials obtained directly from the vendor. We request vendor cooperation letters during scoping and, where cooperation is not granted, we fall back to CSV extraction scoped to each module. If the vendor does not provide timely access to exports, migration timelines extend significantly and scoping may need to be reduced to the records available through UI exports only.

  • Manufacturing objects have no CRM equivalent in Nutshell

    Total Control Pro Work Orders, Bills of Materials, production schedules, inventory movements, and Manufacturing Intelligence KPIs are manufacturing-domain records with no equivalent in Nutshell's Account-Person-Lead-Deal-Activity data model. We scope the migration to customer records, product records, supplier contacts, and custom fields. We deliver written inventories of manufacturing data for the customer's admin to manage in a separate MES or ERP system. Attempting to force manufacturing data into CRM objects results in a denormalized schema that breaks Nutshell's reporting and pipeline functionality.

  • Nutshell custom fields require schema setup before data import

    Nutshell custom fields must be created before data import begins because they affect how records are validated during insert. We create all custom fields during the schema setup phase using the Nutshell UI or API, including field type selection (text, long text, currency, date, checkbox, dropdown, multi-select). Custom fields that exist in Total Control Pro but have data types not supported by Nutshell (such as complex manufacturing measurements) are flagged and delivered as structured CSV for manual entry. Importing into non-existent custom fields causes record validation failures.

  • BOM revision history requires explicit scoping and customer confirmation

    Total Control Pro Bills of Materials carry revision numbers and historical variants, but the platform does not automatically mark which BOM revision was active on any given past date unless that metadata was explicitly logged during implementation. We identify the active BOM revision at migration cutoff by querying the most recent approved revision per product and confirm it with the customer's team before mapping to the destination item. BOMs that were never formally approved or lack revision metadata require customer sign-off on the version to migrate.

Migration approach

Six steps for a successful Total Control Pro to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Total Control Pro logo

Total Control Pro

Source

Strengths

  • Real-time shop-floor to management visibility across the production facility
  • BOM and process change management that reviewers describe as saving significant time
  • Integration and automation capabilities praised by manufacturing teams
  • Cloud-based modular deployment with rapid implementation for SME manufacturers
  • Manufacturing Intelligence Module surfaces operational KPIs that standard ERP systems miss

Weaknesses

  • No publicly documented API for third-party integration or migration tooling
  • Small company (14 employees) with limited support bandwidth during peak implementation periods
  • Reviewers report bugs during implementation, especially with custom feature requests
  • No public pricing page — pricing is bespoke per customer deployment
  • Feature turnaround time for new development requests is slow per user feedback
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Total Control Pro and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Total Control Pro: Not publicly documented — typical SaaS limits assumed and confirmed during scoping..

  • Data volume sensitivity

    B

    Total Control Pro doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Total Control Pro to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Total Control Pro to Nutshell data migrations

Answers to the questions buyers ask most during Total Control Pro to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and three weeks for accounts with under 2,000 customer records and under 1,000 product records where vendor CSV exports are available within the scoping window. Migrations exceeding these volumes, involving supplier records, complex custom field sets, or requiring BOM revision cleanup extend to four to six weeks. If Total Control Pro does not provide timely vendor cooperation for database exports, timelines extend further and scope may reduce to UI-available CSV exports only.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Total Control Pro.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day