CRM migration
Field-level mapping, validation, and rollback between MotionOps and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
MotionOps
Source
Nutshell
Destination
Compatibility
12 of 13
objects map 1:1 between MotionOps and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
MotionOps is a field-service operations platform that bundles CRM, scheduling, job costing, invoicing, and HR management into one subscription. Nutshell is a standalone CRM purpose-built for small-to-mid-market sales teams — its data model covers People (contacts), Companies, Leads, and Deals (pipeline opportunities) with optional add-ons for email marketing and SMS. The migration from MotionOps to Nutshell is fundamentally a data-model reduction: everything Nutshell natively supports maps cleanly, but MotionOps field-service records (jobs, work orders, schedules, timesheets, proposals, change orders, employee documents) have no Nutshell equivalent and require either manual re-entry or a post-migration process. We extract MotionOps data via the REST API using workspace-scoped endpoints for contacts, companies, deals, custom fields, and attachments. We load into Nutshell using the JSON-RPC API with Basic authentication. Our migration plan identifies every MotionOps object, maps it to a Nutshell object or flags it as untranslatable, and surfaces the untranslatable records in a structured export your team can use for manual re-entry. We preserve original create and update timestamps as custom fields on each Nutshell record so your sales reporting reflects the full history from day one.
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 MotionOps 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.
MotionOps
MotionOps People
Nutshell
Nutshell Person
1:1MotionOps People (contacts) map directly to Nutshell Persons. Name, email, phone, address, job title, and custom fields transfer 1:1. Nutshell Persons do not have a lifecycle stage equivalent — any stage or tag data from MotionOps becomes a Nutshell custom field or note.
MotionOps
MotionOps Companies
Nutshell
Nutshell Company
1:1MotionOps Companies map to Nutshell Companies with domain, industry, employee count, and annual revenue fields carrying over directly. Address fields (street, city, state, postalcode, country) also transfer 1:1. Parent-company hierarchies in MotionOps transfer to Nutshell using the parent_company_id reference — circular references are flagged before the migration runs to prevent looped hierarchies.
MotionOps
MotionOps People (with lead status)
Nutshell
Nutshell Lead
1:manyMotionOps People records flagged as leads (no associated Deal or unconverted status) route to Nutshell Leads. Leads with an associated active Deal route to Nutshell Persons instead, since Nutshell associates leads with Deals once they are qualified. The routing logic checks for Deal associations before deciding between Lead and Person objects in Nutshell.
MotionOps
MotionOps Deals
Nutshell
Nutshell Deal
1:1MotionOps Deals map to Nutshell Deals. Deal name, amount, expected close date, stage, and owner resolve by email match to Nutshell users. Nutshell Deal stages use a value-mapping table populated from MotionOps pipeline stage names — stages with no matching Nutshell stage are assigned to a default 'New' stage and flagged for review.
MotionOps
MotionOps Pipeline
Nutshell
Nutshell Pipeline
1:1MotionOps pipelines (one per team or service type) map to Nutshell Pipelines. Nutshell allows multiple pipelines per account; each MotionOps pipeline becomes a separate Nutshell pipeline with its own stage sequence. Stage order and probability values transfer via value-mapping per stage name.
MotionOps
MotionOps Notes
Nutshell
Nutshell Note
1:1MotionOps notes on People, Companies, and Deals migrate as Nutshell Notes attached to the corresponding Person or Company record. Rich-text formatting is preserved where the MotionOps API returns HTML; plain-text notes transfer as-is. Note create timestamps map to a custom field for historical continuity.
MotionOps
MotionOps Custom Fields (People, Companies, Deals)
Nutshell
Nutshell Custom Fields
1:1MotionOps custom field definitions (text, number, date, phone, email, currency, dropdown) map directly to Nutshell custom fields. Multi-select pick-lists require a Nutshell multi-option custom field creation before migration. MultiPerson and relatedTo field types have no Nutshell equivalent and are stored as text for reference.
MotionOps
MotionOps Attachments
Nutshell
Nutshell Files
1:1MotionOps file attachments (images, PDFs, documents) on People, Companies, and Deals are downloaded from the MotionOps media API and re-uploaded to Nutshell as Files attached to the corresponding record. File size limits follow Nutshell's upload constraints. Job-level attachments are flagged separately for manual re-upload post-migration.
MotionOps
MotionOps Jobs / Work Orders
Nutshell
No Nutshell equivalent
1:1MotionOps Jobs and Work Orders have no Nutshell object or field counterpart. These records are exported to a structured CSV/JSON file with all job fields, line items, status history, and attached files so your team can re-enter them manually or build a custom job management workflow in Nutshell using Tasks and custom fields.
MotionOps
MotionOps Proposals / Change Orders
Nutshell
No Nutshell equivalent
1:1MotionOps Proposal Builder and Change Order records contain structured line-item data, e-signature status, and multimedia attachments. Nutshell has a Quotes product ($67/month add-on) that covers basic proposal generation, but it does not share the same data schema. We export these records and flag them for rebuild in Nutshell Quotes or a third-party proposal tool.
MotionOps
MotionOps Schedules / Appointments
Nutshell
No Nutshell equivalent
1:1MotionOps appointment records (assigned technician, service address, time window, job status) have no Nutshell equivalent. Nutshell Tasks can be used for simple task scheduling but lack crew assignment, routing, or multi-day job scheduling. These records are exported for manual re-entry or use with a dedicated field-service tool post-migration.
MotionOps
MotionOps Timesheets / Expenses
Nutshell
No Nutshell equivalent
1:1MotionOps employee timesheets and expense records are tied to the HR module and have no Nutshell equivalent. Nutshell does not handle payroll preparation or employee expense tracking. These records are exported separately and must be maintained in a dedicated payroll or HR tool.
MotionOps
MotionOps Employee Records
Nutshell
No Nutshell equivalent
1:1MotionOps employee records include roles, skills, documents, background check status, and digital business cards. Nutshell user accounts store only login credentials and CRM role permissions. Employee HR data does not migrate — it stays in MotionOps or moves to a dedicated HR platform.
| MotionOps | Nutshell | Compatibility | |
|---|---|---|---|
| MotionOps People | Nutshell Person1:1 | Fully supported | |
| MotionOps Companies | Nutshell Company1:1 | Fully supported | |
| MotionOps People (with lead status) | Nutshell Lead1:many | Fully supported | |
| MotionOps Deals | Nutshell Deal1:1 | Fully supported | |
| MotionOps Pipeline | Nutshell Pipeline1:1 | Fully supported | |
| MotionOps Notes | Nutshell Note1:1 | Fully supported | |
| MotionOps Custom Fields (People, Companies, Deals) | Nutshell Custom Fields1:1 | Fully supported | |
| MotionOps Attachments | Nutshell Files1:1 | Fully supported | |
| MotionOps Jobs / Work Orders | No Nutshell equivalent1:1 | Fully supported | |
| MotionOps Proposals / Change Orders | No Nutshell equivalent1:1 | Fully supported | |
| MotionOps Schedules / Appointments | No Nutshell equivalent1:1 | Fully supported | |
| MotionOps Timesheets / Expenses | No Nutshell equivalent1:1 | Fully supported | |
| MotionOps Employee Records | No Nutshell equivalent1: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.
MotionOps gotchas
No publicly documented public API or export endpoint
Custom fields not exportable in bulk via UI
Paid invoice payment history requires explicit data confirmation
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
Audit MotionOps data model and export schema
We connect to the MotionOps REST API using a workspace-scoped API key and enumerate all People, Companies, Deals, custom field definitions, and attachment metadata. We produce a data audit report that lists record counts per object, custom field names and types, and identifies every MotionOps record type that has no Nutshell equivalent (jobs, work orders, proposals, schedules, timesheets, employee records). This report is the foundation of the migration plan and the source of the field-mapping spreadsheet your team reviews before migration runs.
Create Nutshell custom fields and pipelines
Before data loads, we create every Nutshell custom field needed to receive MotionOps data — including multi-option fields for MotionOps multiSelect types and text fields for person/relatedTo references. We also create the Nutshell Pipelines that correspond to each MotionOps pipeline, populate the stage value-mapping table, and set the stage order and probability weights per Nutshell's pipeline configuration. This step runs in parallel with the sample migration so the schema is ready when test records land.
Resolve owners and validate data dependencies
MotionOps owner IDs are resolved to Nutshell users by email match. Any MotionOps owner whose email does not correspond to a Nutshell user account is flagged before the migration runs — your team either creates the Nutshell user first or assigns those records to a fallback owner. We also validate foreign-key dependencies: Companies must exist before People can link to them, and People must exist before Deals can reference a primary contact. Circular or missing parent-company references in MotionOps are flagged for manual resolution before the migration commits.
Run sample migration with field-level diff
A representative slice of 100–500 records (People, Companies, Deals, and a sample of custom fields) migrates first into a Nutshell staging account or sandbox environment. We generate a field-level diff between the MotionOps source values and the Nutshell destination values so your team can verify that pick-list values mapped correctly, multi-option fields populated as expected, timestamps preserved, and owner assignments resolved. Sample migration runs before the full migration is scheduled, and the results determine whether any field-mapping adjustments are needed.
Execute full migration with delta-pickup window
The full migration runs against the live Nutshell account. All People, Companies, Deals, custom fields, notes, and attachments that have a Nutshell equivalent load via the JSON-RPC API. A delta-pickup window (typically 24–48 hours) captures any MotionOps records created or modified during the cutover. MotionOps jobs, work orders, proposals, schedules, timesheets, and employee records are exported to a structured file for manual re-entry. An audit log records every operation, and one-click rollback is available if reconciliation fails.
Platform deep dives
MotionOps
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 MotionOps 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
MotionOps: Not publicly documented — no public API surface, so rate limits cannot be confirmed externally..
Data volume sensitivity
MotionOps 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 MotionOps to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your MotionOps 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 MotionOps
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.