CRM migration
Field-level mapping, validation, and rollback between Road Runner and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Road Runner
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Road Runner and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Road Runner and Nutshell both track contacts, companies, and deals, but the data models diverge significantly on how person records, activity history, and custom fields are stored. Road Runner typically consolidates person-level data in a flat structure; Nutshell splits person records into People and Leads with separate lead-status logic. The migration carries all Road Runner contacts, companies, deals, tasks, and notes into Nutshell via the Nutshell JSON-RPC API, resolving owners by email match before writing records. Custom fields from Road Runner map to Nutshell custom fields on the appropriate entity. Workflows, sequences, and automation logic do not transfer — those must be rebuilt in Nutshell's automation tools. We surface a field-level diff from a test migration before the full run commits, and a 24–48 hour delta-pickup window captures any records modified during cutover so Nutshell reflects Road Runner's final state at go-live.
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 Road Runner 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.
Road Runner
Contact
Nutshell
Person
1:1Road Runner person records with email, phone, and address map directly to Nutshell Person entities. The person's name, contact details, and notes carry over intact. Company associations become the Nutshell Person's 'company' field reference. All standard address sub-fields (street, city, state, postal_code, country) transfer to the corresponding Nutshell Person address structure for complete location data continuity.
Road Runner
Contact (status = Lead)
Nutshell
Lead
1:manyRoad Runner contacts flagged as leads or with no engaged deal map to Nutshell Leads. Nutshell's lead-status field (New, Contacted, Qualified, Dead) receives the Road Runner lead status value via a value-mapping table; unclassified records default to 'New'. The original Road Runner lead creation date is preserved as a custom datetime field for audit trail continuity.
Road Runner
Company
Nutshell
Company (Account)
1:1Road Runner company records map to Nutshell Company entities. The company name, domain, industry, employee count, and revenue fields carry over directly. Parent-child company hierarchies map via Nutshell's parent_company reference when present in Road Runner. Address and phone information transfer to maintain complete organizational contact details in the target system.
Road Runner
Deal
Nutshell
Deal
1:1Road Runner deals map to Nutshell Deals with deal name, amount, stage, and expected close date. Stage names translate via a value-mapping table between Road Runner stage labels and Nutshell's pipeline stage pick-list. Probability percentages are applied to each Nutshell stage based on the destination pipeline configuration to maintain accurate weighted pipeline values.
Road Runner
Pipeline
Nutshell
Pipeline
1:1Road Runner pipelines map to Nutshell Pipelines. If Road Runner uses a single pipeline with named stages, that becomes one Nutshell pipeline. Multi-pipeline Road Runner setups create corresponding Nutshell pipelines — each with its own stage set and board view.
Road Runner
Task
Nutshell
Task
1:1Road Runner tasks map to Nutshell Tasks with subject, due date, status, and assigned user. Completed-at timestamps carry over as Nutshell 'completed_date'. Open tasks preserve their due-date and assignee for immediate actionability. Task priority levels map via value mapping if present in Road Runner to maintain urgency classification in Nutshell.
Road Runner
Activity (Call / Email / Note)
Nutshell
Activity
1:1Road Runner logged calls, emails, and notes migrate as Nutshell Activities. Each activity links to the originating Person, Company, or Deal via Nutshell's 'related' field structure using entity type and ID references. Original timestamps, user attribution, subject, and body content are all preserved for timeline continuity and deal context in the new CRM.
Road Runner
Attachment / File
Nutshell
File (Note attachment)
1:1Road Runner file attachments on contacts, companies, or deals re-upload to Nutshell as file attachments on the corresponding record. File size limits from Nutshell's storage tier apply; oversized files are flagged before the migration runs with a pre-flight report identifying any attachments that exceed Nutshell's 50MB per-file limit.
Road Runner
Custom Field (entity-level)
Nutshell
Custom Field
1:1Road Runner custom fields on contacts, companies, and deals create corresponding Nutshell custom fields on the matching entity type. Field type mapping applies: text maps to text, number to number, date to date, and pick-list to pick-list with options preserved exactly. Required-field constraints are flagged for admin review post-migration to ensure Nutshell required fields have values for all incoming records.
Road Runner
User / Owner
Nutshell
User
1:1Road Runner user and owner records resolve by email match against Nutshell Users. Matched users receive record ownership in Nutshell based on the resolved User ID. Unmatched owners are flagged before migration — teams either invite the user to Nutshell or assign records to a fallback owner designated during the pre-migration planning phase.
Road Runner
Tag
Nutshell
Tag
1:1Road Runner tags on contacts, companies, and deals migrate as Nutshell Tags with exact label preservation. Tags are entity-scoped (a tag applies to a Person, Company, or Deal independently) and preserve all tag values for filtering and segmentation in Nutshell. Multi-value tag fields in Road Runner split into individual tag entries in Nutshell for consistent filtering behavior.
Road Runner
Workflow / Automation
Nutshell
None
1:1Road Runner automation rules, if any, do not have a Nutshell equivalent and cannot be imported directly. FlitStack exports workflow definitions as a structured JSON reference document for rebuilding in Nutshell's automation tools including automation rules, email sequences, and CRM goals. This export documents trigger conditions, actions, and filter logic from Road Runner for manual reconstruction.
| Road Runner | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Contact (status = Lead) | Lead1:many | Fully supported | |
| Company | Company (Account)1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Activity (Call / Email / Note) | Activity1:1 | Fully supported | |
| Attachment / File | File (Note attachment)1:1 | Fully supported | |
| Custom Field (entity-level) | Custom Field1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Workflow / Automation | None1: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.
Road Runner gotchas
No public REST API for FSM record export
v1-to-v2 API rewrite requires complete config migration
Per-installation KV namespace schema varies
Bulk export not supported — we read incrementally
Attachment and media files are external to RoadRunner
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
Establish API access and run data audit on Road Runner
FlitStack connects to Road Runner's API using credentials provided during scoping. We pull a full export of Contacts, Companies, Deals, Tasks, Activities, Attachments, and custom field definitions. A comprehensive data audit report identifies duplicate records, missing required fields, orphaned owner assignments, and records with inactive status values — all issues that require team decisions before the migration plan is finalized and migration day is scheduled.
Design Nutshell target schema: pipelines, stages, custom fields
Based on the Road Runner data audit, FlitStack produces a Nutshell schema design: which Nutshell pipelines and stages will receive the data, which custom fields need creation, and how lead-status value mapping will be configured. Custom fields are created via Nutshell's Custom Fields UI or API before migration begins. The schema plan is reviewed and approved before any data is written.
Resolve owners and prepare for relationship sequencing
Road Runner owner IDs are resolved by email match against Nutshell Users. Records whose owners do not have matching Nutshell accounts are flagged — teams either invite those users to Nutshell or designate a fallback owner before migration day. Relationship sequencing is planned: Companies first, then People linked to those Companies, then Deals linked to those People and Companies, then Activities and Tasks as child records.
Run test migration with field-level diff
A representative sample — typically 200–500 records spanning all entity types and deal pipelines — migrates into a Nutshell staging environment. FlitStack generates a field-level diff report comparing source values against destination values for every mapped field. The diff is reviewed with the team to confirm lead-status routing, custom field population, and owner assignment before the full migration is scheduled.
Execute full migration with delta-pickup and audit log
The full dataset writes to Nutshell in sequenced batches. A delta-pickup window of 24–48 hours runs after the main write completes, capturing any records created or modified in Road Runner during the cutover period. FlitStack maintains a complete audit log of every record created, updated, or skipped. One-click rollback is available if reconciliation numbers do not match within the agreed tolerance threshold.
Platform deep dives
Road Runner
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Road Runner and Nutshell.
Object compatibility
3 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
Road Runner: Not applicable.
Data volume sensitivity
Road Runner 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 Road Runner to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Road Runner 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 Road Runner
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.