CRM migration
Field-level mapping, validation, and rollback between Results and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Results
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Results and Nutshell.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Results CRM to Nutshell is a small-team migration with a non-standard source. Results has no publicly documented API or confirmed schema, so every migration begins with a direct verification call to confirm what can be exported, in what format, and with which field labels intact. Nutshell accepts CSV imports via its native import wizard and also receives data through its REST API, which gives us two paths depending on volume and record dependency complexity. We map Results Contacts to Nutshell People, Companies to Organizations, Deals to Deals with pipeline stages remapped, and Activities (calls, meetings, tasks, notes) to Nutshell's activity model. Workflows, automations, and any custom objects in Results do not migrate as code; we deliver a written inventory for your admin to rebuild in Nutshell. Because Results lacks confirmed field-level API documentation, scoping takes longer than a well-documented source, and the timeline starts at three weeks for straightforward record migrations.
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 Results 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.
Results
Contact
Nutshell
Person
1:1Results Contacts map to Nutshell People. The Person's name fields, email, phone, address, and any custom fields transfer directly. The Organization lookup resolves to the mapped Organization record after Company migration completes. We flag any Contacts without an associated Company for the customer's admin to review before final import.
Results
Company
Nutshell
Organization
1:1Results Companies map to Nutshell Organizations. Organization name, domain, address, and industry fields transfer directly. Organization is created before any Person import so that the Organization lookup is satisfied at Person insert time.
Results
Deal
Nutshell
Deal
1:1Results Deals map to Nutshell Deals. The deal value, expected close date, and stage transfer directly. Pipeline assignment maps to a Nutshell Pipeline that we configure before migration. If Results uses multiple Deal stages per pipeline, we create corresponding stage values in Nutshell before migration begins.
Results
Pipeline
Nutshell
Pipeline
lossyResults Deal pipelines map to Nutshell Pipelines. Each Pipeline in Nutshell gets its own stage values. We configure the pipeline stages during the pre-migration setup phase and align the stage labels and probabilities with the customer's existing Results pipeline structure.
Results
Activity (Call, Meeting, Task, Note)
Nutshell
Call, Meeting, Task, Note
1:1Results activity records (calls, meetings, tasks, notes) map to their respective Nutshell activity types. Timestamps preserve the original activity date. Activity association to Person and Organization resolves via the email-based Person lookup and the Organization lookup we created during the Company-to-Organization phase.
Results
Custom Field
Nutshell
Custom Field
lossyResults custom fields on Contact, Company, and Deal map to Nutshell custom fields of equivalent type (text, number, date, picklist, checkbox). We create the destination custom field schema in Nutshell during the pre-migration setup phase before any record data moves. Field-level mapping is confirmed during the scoping call because Results has no confirmed public field documentation.
Results
Attachment
Nutshell
File
1:1Results file attachments associated with Contact, Company, or Deal records migrate to Nutshell Files linked via ContentDocumentLink to the parent Person, Organization, or Deal. File content (PDFs, images, documents) transfers as binary blobs; we verify the attachment export format during the discovery call because Results does not have confirmed public API documentation.
Results
Custom Object
Nutshell
Custom Object
1:1If Results contains custom objects beyond the standard Contact, Company, and Deal, we map each to a Nutshell custom object. Because Results has no confirmed public API, custom objects require direct verification during scoping to confirm exportability, field list, and relationship structure. We create the destination custom object schema before migration begins.
| Results | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Organization1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Activity (Call, Meeting, Task, Note) | Call, Meeting, Task, Note1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Attachment | File1:1 | Fully supported | |
| Custom Object | Custom Object1: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.
Results gotchas
QuickBooks-linked records have dual sources of truth
Suite is not architected to scale beyond ~15 users / 15K contacts
No documented public REST API
Field Service photos and signatures require separate binary extraction
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 export verification
We schedule a discovery call to access the customer's Results account and run a test export. We confirm the record types present (Contacts, Companies, Deals, Pipelines, Activities, Custom Fields, Attachments), the export format (CSV structure, delimiter, date format, encoding), and any known limitations on activity history depth. If Results uses a vendor-assisted export rather than a self-serve download, we coordinate the data dump timeline with the Results team on behalf of the customer.
Schema design and Nutshell pipeline configuration
We design the Nutshell destination schema based on the confirmed Results export. This includes creating Nutshell custom fields to match any custom fields in Results, configuring one or more Nutshell Pipelines with stages aligned to the customer's existing Deal structure, and setting up Organization records as the parent of Person records. The Nutshell setup is done in the customer's live Nutshell account during a pre-migration window with no data loaded yet.
Sample migration and reconciliation
We run a sample migration of up to 100 random records from Results into Nutshell, focusing on Contacts, Companies, and Deals. The customer reviews the sample in Nutshell and confirms field mapping accuracy, pipeline stage mapping, and activity display. Any corrections to the mapping (wrong field, missed custom field, stage label mismatch) are applied before the full migration begins. This step is required because Results has no confirmed public schema; the sample is the only way to validate the mapping.
Owner and user reconciliation
We extract all distinct owner and assigned-user values from the Results export and match them against the Nutshell destination account's user list. Any Results owners without a matching Nutshell user are flagged for the customer's admin to provision before production migration. Owner mapping must be resolved before Deal and Activity import because OwnerId is required on those records.
Production migration in dependency order
We run production migration in record-dependency order: Organizations (from Results Companies), People (with Organization lookup resolved), Deals (with Pipeline and stage resolved), Activities (calls, meetings, tasks, notes via API or CSV depending on volume), Attachments (as Files linked to the parent record), and Custom Objects last if present. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation inventory handoff
We freeze any new writes to Results during cutover, run a final delta migration of records modified during the migration window, then enable Nutshell as the system of record. We deliver the automation inventory document listing any detected automations in Results with a description and recommended Nutshell Workflow Rule configuration. We support a three-day post-cutover validation window where the customer's sales team spot-checks record data. We do not rebuild Results automations as Nutshell Workflow Rules inside the migration scope; that is a separate engagement.
Platform deep dives
Results
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Results and Nutshell.
Object compatibility
2 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
Results: Not publicly documented.
Data volume sensitivity
Results 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 Results to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Results 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 Results
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.
