CRM migration

Migrate from MotionOps to Nutshell

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

MotionOps logo

MotionOps

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

12 of 13

objects map 1:1 between MotionOps and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

MotionOps logo

MotionOps

What's pushing teams away

  • Users report limited third-party integrations beyond QuickBooks, requiring manual data re-entry for other tools in their stack.
  • Feature gaps in advanced reporting and analytics on the lower-tier plans push growing contractors toward platforms with deeper business intelligence.
  • Some users note the platform is still maturing — early-stage company (2021 founding, seed-funded) means feature velocity and long-term roadmap carry higher uncertainty than established competitors.

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

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

maps to

Nutshell

Nutshell Person

1:1
Fully supported

MotionOps 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

maps to

Nutshell

Nutshell Company

1:1
Fully supported

MotionOps 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)

maps to

Nutshell

Nutshell Lead

1:many
Fully supported

MotionOps 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

maps to

Nutshell

Nutshell Deal

1:1
Fully supported

MotionOps 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

maps to

Nutshell

Nutshell Pipeline

1:1
Fully supported

MotionOps 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

maps to

Nutshell

Nutshell Note

1:1
Fully supported

MotionOps 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)

maps to

Nutshell

Nutshell Custom Fields

1:1
Fully supported

MotionOps 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

maps to

Nutshell

Nutshell Files

1:1
Fully supported

MotionOps 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

maps to

Nutshell

No Nutshell equivalent

1:1
Fully supported

MotionOps 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

maps to

Nutshell

No Nutshell equivalent

1:1
Fully supported

MotionOps 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

maps to

Nutshell

No Nutshell equivalent

1:1
Fully supported

MotionOps 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

maps to

Nutshell

No Nutshell equivalent

1:1
Fully supported

MotionOps 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

maps to

Nutshell

No Nutshell equivalent

1:1
Fully supported

MotionOps 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.

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.

MotionOps logo

MotionOps gotchas

High

No publicly documented public API or export endpoint

Medium

Custom fields not exportable in bulk via UI

Medium

Paid invoice payment history requires explicit data confirmation

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

  • Job and work-order records have no Nutshell equivalent and require manual re-entry

    MotionOps Jobs and Work Orders are the core operational records in the platform — they contain line items, technician assignments, service addresses, materials used, customer signatures, and change-order history. Nutshell's CRM object model covers People, Companies, Leads, and Deals only; it has no job or work-order entity and no API endpoint that stores job-level data. FlitStack exports these records in a structured format (CSV with all fields and attachments referenced) so your team can re-enter them manually or import them into a dedicated field-service tool. This is not a data-loss risk — it is a data-model limitation that must be planned for before migration day.

  • MotionOps multi-select and person-reference custom fields require pre-creation in Nutshell

    MotionOps supports custom field types that Nutshell does not model natively: multiSelect (multi-option pick-list), person (user reference), and relatedTo (cross-object reference). When these field types appear in your MotionOps schema, Nutshell cannot accept the data format directly via its JSON-RPC API. FlitStack creates the corresponding Nutshell custom fields before migration — multiSelect becomes a Nutshell multi-option field, and person/relatedTo fields store the referenced ID as a text string in a custom text field. Your team should review whether these text-stored references meet your reporting needs or whether the data should be migrated as plain text notes instead.

  • MotionOps Proposals and Change Orders cannot be imported into Nutshell Quotes

    MotionOps Proposal Builder stores line items, e-signature status, multimedia attachments, and version history in a structured format that does not map to Nutshell's Quotes add-on. Nutshell Quotes ($67/month) supports basic product-line pricing and can be sent from within the CRM, but it does not share MotionOps' proposal schema. FlitStack exports MotionOps proposals and change orders as structured records your team can use to rebuild quotes in Nutshell or a dedicated proposal tool. This is a rebuild scenario, not a data-loss scenario.

  • MotionOps employee records, timesheets, and HR documents do not migrate

    MotionOps stores employee data — roles, skills, documents, background checks, payroll status, and digital business cards — in its HR module. Nutshell user accounts contain only CRM login credentials and role-based permissions. Employee HR data cannot map to Nutshell user accounts, and Nutshell has no HR module. FlitStack exports employee records as a structured file separate from the CRM migration so your team can keep those records accessible in MotionOps or move them to a dedicated HR platform. This is disclosed upfront so you do not assume these records are migrating.

  • Nutshell contact limit tiers affect per-user pricing — overages add cost

    Nutshell pricing is tiered by contact count (100 to 900,000+ contacts) with per-user rates that increase at each tier. MotionOps does not have a contact limit in the same sense — storage scales with the subscription tier. If your MotionOps CRM contains more than 2,500 contacts, moving to Nutshell may trigger a pricing tier increase beyond your initial estimate. FlitStack audits the contact count during the discovery phase and flags the Nutshell pricing tier so your team can verify the budget impact before committing to migration.

Migration approach

Six steps for a successful MotionOps to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

MotionOps logo

MotionOps

Source

Strengths

  • Combines CRM, scheduling, invoicing, and time tracking in a single subscription without add-ons.
  • Mobile-first design works well for field technicians with varying levels of technical comfort.
  • Drag-and-drop scheduling with real-time technician availability filtering across skills and service areas.
  • Built-in payment collection including partial payments, credit memos, and stored payment methods.
  • Employee documents, skills tracking, and roles/permissions support back-office HR workflows.

Weaknesses

  • Early-stage company with limited public API documentation and no published developer portal.
  • Third-party integration ecosystem is narrow — QuickBooks Online is the primary accounting integration, others require custom development.
  • Advanced reporting and business intelligence features are tier-gated behind the Scale plan.
  • Multi-location and multi-timezone support is limited to Scale tier, restricting growing multi-market contractors.
  • No publicly documented bulk export or migration tooling in the platform itself.
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?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • 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

    MotionOps: Not publicly documented — no public API surface, so rate limits cannot be confirmed externally..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most MotionOps-to-Nutshell migrations complete in 48–72 hours of clock time for under 50,000 CRM records (People, Companies, Deals). The longest planning step is the sample migration review — verifying custom field mapping and pipeline stage alignment takes 1–2 days before the full run. Larger setups with 500k+ records or extensive custom field definitions extend to 5–7 days. Job and work-order records are exported separately and require manual re-entry post-migration, which runs outside the automated migration timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from MotionOps.
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