CRM migration
Field-level mapping, validation, and rollback between InTouch CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
InTouch CRM
Source
Nutshell
Destination
Compatibility
5 of 9
objects map 1:1 between InTouch CRM and Nutshell.
Complexity
CModerate
Timeline
3-4 weeks
Overview
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.
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 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
Nutshell
Person
1:1InTouch 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
Nutshell
Account
1:1InTouch 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
Nutshell
Opportunity
1:1InTouch 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
Nutshell
Pipeline
lossyInTouch 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)
Nutshell
People Custom Fields
lossyInTouch 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)
Nutshell
Company Custom Fields
lossyInTouch 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)
Nutshell
Opportunity Custom Fields
lossyInTouch 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)
Nutshell
Task and Event
1:1InTouch 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
Nutshell
User
1:1InTouch 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.
| InTouch CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Custom Fields (People) | People Custom Fieldslossy | Fully supported | |
| Custom Fields (Companies) | Company Custom Fieldslossy | Fully supported | |
| Custom Fields (Deals) | Opportunity Custom Fieldslossy | Fully supported | |
| Activity (calls, emails, meetings, tasks) | Task and Event1:1 | Fully supported | |
| Owner | User1: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.
InTouch CRM gotchas
CSV-based import is the primary documented data path
Stage and pipeline label drift across customer instances
Limited custom-object surface
All-in-one bundling means multiple modules' data must be reconciled
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 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.
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.
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.
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.
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.
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
InTouch CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across InTouch CRM and Nutshell.
Object compatibility
1 of 8 objects need a manual workaround.
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
InTouch CRM: Not publicly documented.
Data volume sensitivity
InTouch 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 InTouch CRM to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave InTouch 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.