CRM migration

Migrate from CompanyHub CRM to Nutshell

Field-level mapping, validation, and rollback between CompanyHub CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

CompanyHub CRM logo

CompanyHub CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between CompanyHub CRM and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

CompanyHub CRM logo

CompanyHub CRM

What's pushing teams away

  • No built-in calling or SMS means sales teams requiring phone workflows must purchase and integrate a separate telephony stack.
  • Custom tables and UTrons automations do not export cleanly—teams with heavy custom data models face significant re-implementation effort when leaving.
  • Reporting provides only surface-level visualizations and lacks weighted deal values, pipeline velocity, or activity-based conversion metrics.
  • Goals and targets tracking is buried in the interface and not surfaced prominently enough for sales managers running weekly reviews.
  • The product is unable to be uninstalled from integrations once connected, creating lock-in friction for teams evaluating a switch.

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 CompanyHub CRM objects map to Nutshell

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

maps to

Nutshell

People

1:1
Fully supported

CompanyHub 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

maps to

Nutshell

Account

1:1
Fully supported

CompanyHub 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

maps to

Nutshell

Deal

1:1
Fully supported

CompanyHub 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

maps to

Nutshell

Pipeline Stages

1:1
Mapping required

CompanyHub 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

maps to

Nutshell

Account or People custom fields (flattened)

many:1
Mapping required

CompanyHub 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

maps to

Nutshell

Task

1:1
Fully supported

CompanyHub 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

maps to

Nutshell

Quote (Nutshell Pro and above)

1:1
Fully supported

CompanyHub 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

maps to

Nutshell

User

1:1
Fully supported

CompanyHub 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

maps to

Nutshell

Activity (timeline entry)

1:1
Fully supported

CompanyHub 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

maps to

Nutshell

Note

1:1
Fully supported

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

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.

CompanyHub CRM logo

CompanyHub CRM gotchas

High

Admin-only export gate blocks non-admin migration scoping

Medium

Custom Table schema is not self-describing in the API

Medium

UTrons workflow logic does not survive migration

Low

API key cap of 5 limits concurrent migration jobs

Low

Email body content may be truncated in activity API responses

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

  • Nutshell plan tier limits custom field count

    Nutshell caps the number of custom fields per plan: Foundation allows 5, Growth allows 15, Pro allows 25, Business allows 50, and Enterprise allows unlimited. CompanyHub Professional and Enterprise accounts often carry 30+ custom fields on Contacts, Companies, and Deals. Before migration we audit the custom field count and confirm the customer's Nutshell plan tier can accommodate the full schema. If the plan tier is too low, we recommend upgrading before migration to avoid data truncation or partial field migration.

  • CompanyHub UTrons automations do not transfer as code

    CompanyHub's UTrons workflow engine encodes automation logic as flowchart nodes with no API export capability. Every Utron (task creation on stage change, duplicate disallowance, scheduled alerts) must be rebuilt in Nutshell's automation engine, which uses rule-based triggers rather than flowchart logic. We document each active Utron during discovery with its trigger, conditions, actions, and recommended Nutshell equivalent, and the customer's admin rebuilds them post-migration. This is a manual step that adds scope outside the data migration itself.

  • Custom Table rows require schema flattening

    CompanyHub Custom Tables have user-defined schemas not fully exposed by the v1 API, requiring manual documentation during discovery. Nutshell has no native custom object support, so Custom Table rows must be flattened into Account or People custom fields or left for manual re-entry. We work with the customer during scoping to prioritize the most critical Custom Table fields for migration and document the rest as out-of-scope for rebuild consideration. This planning step adds one to two weeks to discovery.

  • Email body content may be truncated at export

    CompanyHub's API may return email activity logs with only metadata (timestamp, recipient, open status) and no full message body. We run a pre-migration probe against the customer's API key to determine whether body content is present in responses. If body text is missing, we flag the gap in the migration report and offer to supplement with an IMAP export or email platform backup if available. Customers who rely on full email thread history for compliance or customer service should source a complete email archive before migration begins.

  • API key cap of 5 restricts parallel migration jobs

    CompanyHub allows a maximum of 5 API keys per account. For migrations with large record volumes requiring parallel read streams, we may exhaust the key pool during extraction. We coordinate key allocation with the customer during migration planning, requesting temporary elevation of the limit where possible or scheduling staggered job windows to stay within the 5-key ceiling. This is a planning constraint, not a data integrity risk, but it can extend the extraction phase for very large datasets.

Migration approach

Six steps for a successful CompanyHub CRM to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

CompanyHub CRM logo

CompanyHub CRM

Source

Strengths

  • Per-user pricing capped at $42/month makes it the most affordable option among feature-rich SMB CRMs.
  • Drag-and-drop pipeline and task follow-up reminders keep low-touch sales teams from losing deals.
  • UTrons workflow engine uses a flowchart interface to automate any business logic without code.
  • Field-level and record-level security controls allow granular visibility settings across roles and territories.
  • Custom Tables and Custom Apps extend the data model to verticals beyond standard sales (real estate, education, services).

Weaknesses

  • No native calling, SMS, or voice features—phone-centric sales teams need third-party integrations.
  • API is limited to v1 with no public rate limit documentation and a maximum of 5 API keys per account.
  • Only admin users can export data from the product UI, which complicates migration scoping for non-admin account holders.
  • Custom Table migrations require pre-provisioning the destination schema, adding a planning step not needed for standard objects.
  • Activity logs and email bodies may be truncated in API responses, limiting the fidelity of historical communication data migration.
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. 1 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 CompanyHub CRM and Nutshell.

  • Object compatibility

    B

    1 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

    CompanyHub CRM: Not publicly documented.

  • Data volume sensitivity

    B

    CompanyHub CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your CompanyHub CRM 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 CompanyHub CRM to Nutshell data migrations

Answers to the questions buyers ask most during CompanyHub CRM to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and four weeks for accounts under 5,000 Contacts, 1,000 Deals, and no Custom Tables. Migrations with Custom Tables, multiple pipeline stages, or engagement histories over 50,000 records extend to four to eight weeks because of Custom Table flattening planning and activity timeline chunking. The Nutshell plan validation step (confirming custom field quota) adds one to two weeks to discovery for accounts with more than 25 custom fields.

Adjacent paths

Related migrations to explore

Ready when you are

Move from CompanyHub CRM.
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