CRM migration

Migrate from InTouch CRM to Nutshell

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

InTouch CRM logo

InTouch CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

56%

5 of 9

objects map 1:1 between InTouch CRM and Nutshell.

Complexity

CModerate

Timeline

3-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

InTouch CRM and Nutshell both serve small to mid-size B2B sales teams but differ significantly in export methodology and platform depth. InTouch CRM uses CSV-based export as its primary documented migration path, with no publicly indexed bulk API in third-party integration directories. Nutshell, founded in 2010, provides a REST API (Business tier and above) and includes free white-glove data import assistance for new customers. We sequence the migration by first exporting InTouch data in structured CSV, transforming field types for Nutshell's People, Accounts, and Opportunities objects, then loading in dependency order — Accounts first, then People, then Deals, then Activity history as Tasks and Events. Custom fields from InTouch are pre-created in Nutshell before any records land. InTouch Workflows and automations do not migrate as code; we deliver a written inventory of every automation for the customer's admin to rebuild in Nutshell.

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

InTouch CRM logo

InTouch CRM

What's pushing teams away

  • Limited advanced customization — Capterra UK reviewers cite the lack of flexible reporting, integrations, and dashboard customization as the main reason teams outgrow the platform.
  • Integration ecosystem is narrow compared to mainstream SMB CRMs (HubSpot, Pipedrive, Zoho), pushing teams with custom tech stacks to switch.
  • Reporting and analytics are basic, prompting data-driven teams to move to platforms with richer BI integration.
  • Small public review base (mostly Capterra UK) limits peer-reference signal, making procurement teams hesitant when scaling up.
  • No publicly documented bulk API restricts modern automation workflows, so power users hit the integration ceiling earlier than on platforms with open developer ecosystems.

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

Each row shows how a InTouch 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.

InTouch CRM

Contact

maps to

Nutshell

Person

1:1
Fully supported

InTouch Contact records map directly to Nutshell People. The contact's name fields, email address, phone number, address, and any associated custom fields migrate as typed Nutshell People custom fields. We resolve the InTouch company link to a pre-created Nutshell Account record and set the Person's company association during import. Duplicate detection runs on email address as the primary key.

InTouch CRM

Company

maps to

Nutshell

Account

1:1
Fully supported

InTouch Company records map to Nutshell Account. The company name becomes the Account name, domain data maps to the Account website field, and any industry, employee count, or revenue fields migrate as Nutshell Company custom fields. Account is created before Person import so the company association is satisfied at the moment of Person insert.

InTouch CRM

Deal

maps to

Nutshell

Opportunity

1:1
Fully supported

InTouch Deals map to Nutshell Opportunities. The deal amount, close date, stage label, and owner migrate directly. We remap InTouch pipeline stage labels to Nutshell pipeline stage names that we configure before migration. If InTouch has multiple deal pipelines, each becomes a separate Nutshell pipeline with its own stage set.

InTouch CRM

Pipeline

maps to

Nutshell

Pipeline

lossy
Fully supported

InTouch pipelines and their stage definitions are pre-created in Nutshell before any Deal records migrate. Stage order, probability values (if used in InTouch), and stage names are translated one-to-one. Closed Won and Closed Lost stages map to Nutshell's Won and Lost stage equivalents with appropriate probability settings.

InTouch CRM

Custom Fields (People)

maps to

Nutshell

People Custom Fields

lossy
Fully supported

InTouch custom fields on Contact records are pre-created in Nutshell as People custom fields before migration begins. Field type translation applies: text fields become Nutshell text fields, currency fields become Nutshell currency fields, date fields become Nutshell date fields, and checkbox fields become Nutshell checkbox fields. InTouch long-text fields map to Nutshell long-text fields with the 225-character and paragraph limits respected.

InTouch CRM

Custom Fields (Companies)

maps to

Nutshell

Company Custom Fields

lossy
Fully supported

InTouch custom fields on Company records pre-create in Nutshell as Company custom fields. Industry, employee count, annual revenue, and any other company-level attributes in InTouch map to the corresponding Nutshell field type. Fields that InTouch stores as free-text but represent categorical data are imported as Nutshell text with deduplication recommended post-migration.

InTouch CRM

Custom Fields (Deals)

maps to

Nutshell

Opportunity Custom Fields

lossy
Fully supported

InTouch custom fields attached to Deals pre-create in Nutshell as Opportunity custom fields. Deal-level attributes like internal order numbers, product categories, or referral sources migrate as text fields. We flag any InTouch fields that represent monetary amounts and ensure they import as Nutshell currency fields rather than text to preserve numeric filtering and reporting in Nutshell.

InTouch CRM

Activity (calls, emails, meetings, tasks)

maps to

Nutshell

Task and Event

1:1
Fully supported

InTouch activity records linked to Contacts and Companies migrate as Nutshell Tasks and Events. Call activities import as Tasks with the Call disposition and duration preserved in custom fields. Meeting activities import as Nutshell Events with start time, duration, and attendee information. Email and task activity records migrate as Tasks with a note body containing the original message or task description. Original timestamps are preserved as the ActivityDate on the Nutshell record.

InTouch CRM

Owner

maps to

Nutshell

User

1:1
Fully supported

InTouch owners referenced on Contact, Company, and Deal records map to Nutshell User accounts. We match by email address. Any InTouch owner without a corresponding Nutshell User is held in a reconciliation queue for the customer's admin to provision before Person and Opportunity import continues.

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.

InTouch CRM logo

InTouch CRM gotchas

High

CSV-based import is the primary documented data path

Medium

Stage and pipeline label drift across customer instances

Medium

Limited custom-object surface

Low

All-in-one bundling means multiple modules' data must be reconciled

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

  • InTouch has no public bulk API; migration relies on CSV export

    InTouch CRM does not expose a publicly documented bulk API accessible through standard third-party integration directories. CSV export is the primary documented path for extracting Contacts, Companies, Deals, and Activity history. We handle CSV sequencing in ordered batches, split large exports into importable chunks, and validate row counts against Nutshell import totals. Large datasets require careful sequencing to avoid row-limit errors during Nutshell CSV import. Teams should confirm which InTouch data modules are active before export to avoid pulling stale or deprecated field data.

  • InTouch Workflows and automations do not migrate to Nutshell

    InTouch Workflows and automation rules are platform-specific and do not transfer to Nutshell as code. The automation models differ structurally: InTouch uses property-triggered workflow rules, while Nutshell uses automation rules with page-visit triggers, drip enrollment actions, and tag-based segmentation. We deliver a written inventory of every active InTouch automation with its trigger conditions, actions, and recommended Nutshell automation equivalent. The customer's admin rebuilds automations in Nutshell post-migration or engages Nutshell's implementation support.

  • Nutshell API access requires Business tier ($59/user/mo)

    Nutshell's REST API is only available on the Business tier and above at $59/user/month (annual billing). Migrations run through Nutshell's native CSV import on lower tiers, which has record-count limits per import batch. We confirm the destination Nutshell plan during scoping and recommend Business tier if the migration volume exceeds 10,000 records or requires custom object API access. API-level migration enables batch processing, error logging, and parent-record lookup resolution that CSV import alone cannot provide.

  • Custom field types must be pre-created before import to avoid data loss

    InTouch custom fields can hold data in a variety of formats — free text, numeric values, dates, currency amounts, and multi-select options — that do not automatically map to Nutshell field types. We audit InTouch custom fields before migration, pre-create matching Nutshell custom fields with the correct type (text, long-text, currency, date, checkbox), and then run the data import with type-aware transformation. Skipping this step results in text-formatted numbers, incorrectly parsed dates, or truncated values in Nutshell after import.

  • Pipeline stage labels from InTouch must be remapped manually in Nutshell

    InTouch pipeline stage labels are defined per user and can vary between InTouch accounts. Nutshell pipeline stages are created as a named set within each pipeline configuration. We extract the exact InTouch stage labels during discovery, recreate them as Nutshell stage names within the corresponding pipeline, and use the stage label as the mapping key during Deal-to-Opportunity import. Any InTouch stage labels that contain characters unsupported by Nutshell's naming conventions are flagged for manual review before migration.

Migration approach

Six steps for a successful InTouch CRM to Nutshell data migration

  1. Discovery and scoping

    We audit the InTouch CRM account to identify all active modules — Contacts, Companies, Deals, Activities, and any Custom Fields. We count records per module, identify custom field names and data types, and map the pipeline and stage structure used for Deals. We confirm the destination Nutshell plan tier, pre-create any required custom fields in Nutshell, and establish the owner-to-User mapping by extracting distinct owner emails from InTouch. The discovery output is a written migration scope with record counts, field mappings, and a stage remapping table.

  2. InTouch data export

    We extract data from InTouch CRM using the platform's CSV export capability. Exports run in dependency order: Companies first, then Contacts, then Deals, then Activity history. Large datasets are split into batches of 5,000 rows or fewer to stay within Nutshell CSV import limits. We validate each export file for column completeness, row counts, and the presence of required mapping fields (email for People, company name for Accounts, stage label for Opportunities) before the transform phase begins.

  3. Data transformation and field mapping

    We transform each InTouch CSV export into Nutshell-compatible import format. This includes standardizing date formats to YYYY-MM-DD, converting currency values to plain numeric format for Nutshell currency fields, resolving InTouch owner email references to Nutshell User IDs, and remapping InTouch pipeline stage labels to Nutshell stage names using the pre-agreed stage table. Custom field values are mapped to their pre-created Nutshell custom field counterparts with type-aware formatting applied per field.

  4. Sandbox migration and validation

    We run a full test migration into a Nutshell sandbox environment using production-like data volumes before touching live data. The customer reconciles record counts in Nutshell against the InTouch source, spot-checks twenty to thirty records per object for field-level accuracy, and verifies that pipeline stages and custom fields render correctly. Any mapping corrections or missing field additions happen in this phase. Sign-off from the customer's admin is required before production migration begins.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from InTouch Companies) first, then People (with Account association resolved), then Opportunities (with Account, Owner, and pipeline stage resolved), then Activity history as Tasks and Events. Each phase emits a row-count reconciliation report showing records imported, records skipped, and error rows logged. We address any errors before advancing to the next object to avoid cascading lookup failures.

  6. Cutover, validation, and automation handoff

    We freeze InTouch CRM to prevent writes during the final delta migration window, migrate any records modified after the last full export, then enable Nutshell as the system of record. We deliver the written InTouch Workflow and automation inventory with recommended Nutshell equivalents to the customer's admin team. We offer a one-week post-migration hypercare window to resolve any data reconciliation issues reported by the sales team. We do not rebuild InTouch automations as Nutshell automations inside the migration scope; that is a separate engagement or an internal admin task.

Platform deep dives

Context on both ends of the pair

InTouch CRM logo

InTouch CRM

Source

Strengths

  • All-in-one bundling of CRM, email marketing, direct mail, SMS, surveys, contact management, and task tracking in one platform
  • Strong fit for UK small businesses — Capterra UK reviewers consistently highlight ease of use and customer support
  • Flat per-user pricing keeps costs predictable as small teams grow
  • Automation features for email marketing, task tracking, and customer segmentation work out of the box
  • Email-to-CRM workflow described as seamless by users, useful for marketing-led small businesses

Weaknesses

  • Limited advanced customization options for reporting, dashboards, and integrations
  • No publicly indexed bulk API or developer portal
  • Small public review footprint outside Capterra UK
  • Custom objects beyond standard CRM entities are not supported
  • Vendor's UK focus may not suit US/international teams expecting global feature parity
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?

Moderate CRM migration. 1 of 8 objects need a manual workaround.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across InTouch CRM and Nutshell.

  • Object compatibility

    D

    1 of 8 objects need a manual workaround.

  • 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

    InTouch CRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your InTouch CRM to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Straightforward migrations with under 5,000 records, a single pipeline, and a standard field set land in three to four weeks. Migrations with multiple InTouch pipelines, extensive custom field sets, large activity histories, or parallel CRM usage during transition run six to eight weeks. The variation reflects time spent on data audit, custom field pre-creation, and post-import validation. We include data cleaning and staging in the timeline estimate; rebuilding Nutshell pipelines or redesigning deal stages adds separate time outside the migration scope.

Adjacent paths

Related migrations to explore

Ready when you are

Move from InTouch 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