CRM migration
Field-level mapping, validation, and rollback between CompanyHub CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
CompanyHub CRM
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between CompanyHub CRM and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
CompanyHub CRM and Nutshell are both SMB-focused CRMs with per-user pricing, but they differ significantly in data model and automation philosophy. CompanyHub organizes data around Contacts, Companies, Deals, and Custom Tables with UTrons flowchart automations; Nutshell uses a simpler People, Accounts, and Deals structure with a JSON-RPC API and per-plan custom field limits. The migration requires resolving CompanyHub's custom table schemas (which have non-self-describing APIs) against Nutshell's custom field quota, mapping CompanyHub pipeline stages to Nutshell's standard stage labels, and documenting UTrons for rebuild in Nutshell's workflow engine. Activity history migrates as timeline entries; UTrons automations do not transfer as code and require a separate rebuild scope. Nutshell's free onboarding and straightforward interface make it a common destination for teams leaving CompanyHub for simpler tooling, while the lower per-seat cost on Nutshell's Foundation tier appeals to cost-sensitive teams at the lower end of CompanyHub's pricing range.
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 CompanyHub CRM 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.
CompanyHub CRM
Contact
Nutshell
People
1:1CompanyHub Contacts map to Nutshell People records. Standard fields (name, email, phone, address) migrate directly. Custom fields on CompanyHub Contacts map to Nutshell custom fields on People, subject to the destination plan's custom field limit. We validate the field count against the customer's Nutshell plan tier during scoping and flag if the plan upgrade is required before migration begins.
CompanyHub CRM
Company
Nutshell
Account
1:1CompanyHub Companies map to Nutshell Accounts. The Company name becomes the Account name, domain maps to the Website field, and industry/tags migrate as Account-level custom fields. Account is created before any Person import so that the relationship linkage is satisfied at Person insert time.
CompanyHub CRM
Deal
Nutshell
Deal
1:1CompanyHub Deals map to Nutshell Deals. The deal name, amount, expected close date, owner, and associated Company (Account) link migrate directly. We resolve the Company lookup by name match against the Nutshell Account table before Deal import. Custom fields on Deals migrate to Nutshell Deal custom fields, again subject to plan-tier limits.
CompanyHub CRM
Pipeline Stages
Nutshell
Pipeline Stages
1:1CompanyHub pipeline stages (drag-and-drop customizable) map to Nutshell pipeline stage labels. We capture the full stage list during discovery, map each to the equivalent Nutshell stage, and configure the Nutshell pipeline before Deal import. If the customer has stages that do not map cleanly to Nutshell's default labels, we create custom stage names to preserve the original sales process language.
CompanyHub CRM
Custom Tables
Nutshell
Account or People custom fields (flattened)
many:1CompanyHub Custom Tables (Properties, Courses, Payments, etc.) do not have a direct Nutshell equivalent because Nutshell does not support custom objects. During scoping we ask the customer to identify which Custom Table fields are critical to preserve. High-value fields are flattened into Account-level or People-level custom fields; low-priority fields are documented for manual re-entry or a custom database outside the CRM. This decision is made jointly with the customer during discovery.
CompanyHub CRM
Task
Nutshell
Task
1:1CompanyHub Tasks map to Nutshell Tasks. Due date, assigned owner (resolved by email match), linked Contact (resolved to People), and task status migrate directly. Tasks created by UTrons automations in CompanyHub migrate as standard Tasks without the automation logic, which must be rebuilt in Nutshell's automation engine.
CompanyHub CRM
Quote
Nutshell
Quote (Nutshell Pro and above)
1:1CompanyHub Quotes map to Nutshell Quotes on Pro, Business, and Enterprise tiers. Quote templates do not migrate; the customer rebuilds templates in Nutshell's customizable template editor. Line items migrate as Quote Line Items with product name, quantity, unit price, and total.
CompanyHub CRM
User/Owner
Nutshell
User
1:1CompanyHub Users map to Nutshell Users. We match by email address. Owners without a matching Nutshell User go to a reconciliation queue for the customer admin to provision before record import resumes. Inactive CompanyHub users migrate as inactive Nutshell users to preserve the owner attribution on historical records.
CompanyHub CRM
Activity: Email
Nutshell
Activity (timeline entry)
1:1CompanyHub email activity logs migrate as Nutshell Activity entries linked to the corresponding People record. We note that CompanyHub API responses may truncate email body content; we flag any gaps in the migration report and offer to supplement from the customer's email platform export if available.
CompanyHub CRM
Activity: Note
Nutshell
Note
1:1CompanyHub Notes migrate as Nutshell Notes linked to the parent record (People, Account, or Deal). Note body text migrates as rich text. Notes attached to Custom Tables without a Nutshell equivalent are linked to the associated Company or Contact record at the customer's direction.
| CompanyHub CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | People1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline Stages | Pipeline Stages1:1 | Mapping required | |
| Custom Tables | Account or People custom fields (flattened)many:1 | Mapping required | |
| Task | Task1:1 | Fully supported | |
| Quote | Quote (Nutshell Pro and above)1:1 | Fully supported | |
| User/Owner | User1:1 | Fully supported | |
| Activity: Email | Activity (timeline entry)1:1 | Fully supported | |
| Activity: Note | Note1: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.
CompanyHub CRM gotchas
Admin-only export gate blocks non-admin migration scoping
Custom Table schema is not self-describing in the API
UTrons workflow logic does not survive migration
API key cap of 5 limits concurrent migration jobs
Email body content may be truncated in activity API responses
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 scoping
We audit the CompanyHub portal across tier (Starter/Professional/Enterprise), custom field count on Contacts/Companies/Deals, Custom Table list with field definitions, active Utrons, pipeline stage names, engagement volume, and owner list. We pair this with a Nutshell plan review based on the custom field count. The discovery output is a written migration scope document listing every object to migrate, the custom field count against the plan tier, the Custom Table flattening plan, and the Utron inventory requiring rebuild.
Nutshell plan validation and schema pre-provisioning
We validate that the customer's Nutshell plan tier can accommodate the full custom field schema. If the plan tier is insufficient, we recommend upgrading before migration begins to avoid partial field migration. We then provision all custom fields in Nutshell (on People, Accounts, and Deals as appropriate), configure pipeline stages to match CompanyHub's stage names, and set up the Quote object if the customer has Pro or above. Schema is validated by a test import of five records before the full migration proceeds.
Owner and user reconciliation
We extract every distinct CompanyHub Owner referenced on Contacts, Companies, Deals, and Tasks and match by email against the Nutshell destination's User table. Any CompanyHub Owner without a matching Nutshell User goes to a reconciliation queue for the customer admin to provision before record import resumes. Migration cannot proceed past this step because Owner references must be valid at import time.
Sandbox migration and reconciliation
We run a full migration into the customer's live Nutshell environment using a representative data sample (typically the 100 most recently updated records per object). The customer reconciles record counts, spot-checks field mapping for 20-30 records against the CompanyHub source, and validates that pipeline stages, custom field values, and relationship links are intact. Any mapping corrections happen here before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Users (validated), Accounts (from CompanyHub Companies), People (from Contacts with AccountId resolved), Deals (with AccountId and OwnerId resolved), Tasks, Quotes, Activity history. Custom Table fields are flattened into the appropriate parent record custom fields per the flattening plan agreed during discovery. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and Utron rebuild handoff
We freeze CompanyHub writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the Utron inventory document with rebuild specifications for Nutshell's automation engine. We support a one-week hypercare window for reconciliation issues. We do not rebuild Utrons as Nutshell automation rules inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
CompanyHub CRM
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 CompanyHub CRM 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
CompanyHub CRM: Not publicly documented.
Data volume sensitivity
CompanyHub CRM 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 CompanyHub CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your CompanyHub CRM 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 CompanyHub CRM
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.