CRM migration

Migrate from mQuest to Nutshell

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

mQuest logo

mQuest

Source

Nutshell

Destination

Nutshell logo

Compatibility

93%

13 of 14

objects map 1:1 between mQuest and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

mQuest stores data using a standard CRM object model (contacts/people, companies/accounts, deals/opportunities, activities, and custom fields). This data migrates into Nutshell's four primary record types: People, Companies, Leads, and Deals. Nutshell does not support true custom objects — all mQuest custom fields become Nutshell custom fields attached to the appropriate record type. We map mQuest contacts to Nutshell People (or Leads based on status), mQuest companies to Nutshell Companies, and mQuest deals to Nutshell Deals. Activity history including calls, emails, meetings, and notes migrates as Nutshell Activities attached to the parent record. Owner resolution uses email matching against Nutshell users. The migration uses Nutshell's API for all data writes, with a sample migration and field-level diff before the full run, followed by a delta-pickup window capturing in-flight changes during cutover. Workflows, automations, and reporting dashboards do not migrate — those require manual rebuild in Nutshell's automation tools and reporting module.

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

mQuest logo

mQuest

What's pushing teams away

  • Absence of a documented public API makes deep integrations with accounting or ERP systems difficult and forces manual data re-entry.
  • Limited reporting depth beyond standard job summaries means teams that need profitability analytics by technician or region feel constrained.
  • Smaller FSM teams report that the platform's feature set is designed for more complex operations and can feel oversized for simple job scheduling needs.
  • When service portfolios grow to require multi-location or franchise-level management, the platform's structure becomes a limiting factor.
  • Lack of clear pricing transparency on the vendor's site makes budget planning difficult and drives evaluation of alternatives with published tiers.

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

Each row shows how a mQuest 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.

mQuest

Contact / Person

maps to

Nutshell

Person

1:1
Fully supported

mQuest contacts map directly to Nutshell People when the contact has an active customer or prospect relationship. Nutshell People records store name, email, phone, title, address, and association to a Company record. The direct mapping preserves all standard contact fields without transformation.

mQuest

Contact (inactive or unqualified status)

maps to

Nutshell

Lead

1:many
Fully supported

mQuest contacts marked as inactive, unqualified, or archived split to Nutshell Leads. Leads in Nutshell are separate from People and do not automatically convert until manually actioned by a sales rep. This split preserves your pipeline health by keeping unqualified contacts separate.

mQuest

Company / Account

maps to

Nutshell

Company

1:1
Fully supported

mQuest companies map directly to Nutshell Companies. The Company record stores name, domain, industry, employee count, revenue, and parent-company hierarchy if applicable. People associate to Companies via a primary link, maintaining your organizational structure in the destination.

mQuest

Deal / Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

mQuest deals map to Nutshell Deals — the central revenue-tracking object. Each Deal has a name, amount, stage, close date, owner, and optional associated People or Company links. This is your primary revenue visibility object in Nutshell after migration completes.

mQuest

Pipeline

maps to

Nutshell

Deal Pipeline Stages

1:1
Fully supported

mQuest deal pipelines with named stages map to Nutshell Deal stages. Stage order and probability values are configured in Nutshell's pipeline settings. We map each mQuest stage name to the corresponding Nutshell stage label value-by-value during the migration preparation phase.

mQuest

Custom Field (on Contact)

maps to

Nutshell

Custom Field (on Person)

1:1
Fully supported

mQuest custom fields on contacts create equivalent custom fields in Nutshell People. Nutshell custom fields are created by the admin before migration; we provide a field-creation checklist as part of the migration plan to ensure all required fields exist before data transfer begins.

mQuest

Custom Field (on Company)

maps to

Nutshell

Custom Field (on Company)

1:1
Fully supported

mQuest custom fields on companies create equivalent custom fields in Nutshell Companies. Nutshell Company custom fields support text, number, date, and choice types. The appropriate field type is specified in the pre-migration field-creation checklist delivered to your admin.

mQuest

Custom Field (on Deal)

maps to

Nutshell

Custom Field (on Deal)

1:1
Fully supported

mQuest custom fields on deals create custom fields in Nutshell Deals. Deal-level custom fields capture order numbers, product lines, or internal tracking values that have no native Nutshell equivalent. These fields are preserved as custom fields on the Deal record type.

mQuest

Activity (Call)

maps to

Nutshell

Activity

1:1
Fully supported

mQuest call records migrate as Nutshell Activities with type set to Call. Original timestamp, duration, owner, and notes are preserved. The activity links to the parent Person, Company, Lead, or Deal record, maintaining your complete communication history.

mQuest

Activity (Email)

maps to

Nutshell

Activity

1:1
Fully supported

mQuest email activity migrates as Nutshell Activities with type set to Email. Subject line, body text, timestamp, and owner are preserved. Emails link to the associated Person or Lead record, keeping your email history attached to the correct contact record.

mQuest

Activity (Meeting)

maps to

Nutshell

Activity

1:1
Fully supported

mQuest meeting records migrate as Nutshell Activities with type set to Meeting. Start time, end time, location, attendees, and notes transfer. The activity links to the parent record in Nutshell, preserving your full meeting history for reference after migration.

mQuest

Activity (Note)

maps to

Nutshell

Activity

1:1
Fully supported

mQuest notes migrate as Nutshell Activity records with type set to Note. The note body, creation date, and owner transfer. Notes can be associated with People, Companies, Leads, or Deals, maintaining all your reference notes in the new system.

mQuest

Owner / User

maps to

Nutshell

Nutshell User

1:1
Fully supported

mQuest owner records resolve to Nutshell users by email address match. Owners without a matching Nutshell user are flagged before migration. Their records receive a fallback owner assignment based on admin-specified rules to ensure no data is orphaned.

mQuest

Attachment / File

maps to

Nutshell

File

1:1
Fully supported

mQuest file attachments on contacts, companies, or deals download and re-upload to Nutshell's file storage. File names, sizes, and upload dates are preserved. Nutshell's file viewer renders common formats inline for convenient access by your team.

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.

mQuest logo

mQuest gotchas

High

No public API documented for programmatic data extraction

Medium

Custom field schemas vary by tenant with no published reference

Medium

Invoiced job data may require fiscal-period alignment

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

  • Nutshell has no true custom objects — only custom fields on standard types

    Nutshell does not support creating custom objects the way platforms like Salesforce or HubSpot Enterprise do. Any mQuest custom object (a record type that is not a contact, company, or deal) cannot map to an equivalent Nutshell object. Instead, we create Nutshell custom fields on the appropriate standard record type and store the data as structured text, JSON, or delimited values. This preserves the data for reference but requires admin acceptance that the data structure differs from the source.

  • Nutshell API rate limits apply during the migration run

    Nutshell's JSON-RPC API enforces per-account rate limits on write operations. For migrations with more than 10,000 records, we implement request throttling and batch sizing consistent with Nutshell's published limits to avoid 429 errors. If the mQuest dataset includes large activity histories (thousands of call and email logs per contact), the migration run time extends proportionally because each activity is a separate API write. We surface estimated run times based on activity volume before the migration commits.

  • Lead-Person split requires contact-status mapping before migration

    mQuest does not have a separate Lead object — all person records live in one contact table. Nutshell distinguishes between People and Leads. We map contacts with an active, customer, or prospect status to Nutshell People and contacts with an unqualified or archived status to Nutshell Leads. If mQuest uses custom status values, the mapping requires admin review before migration so that the split logic is applied correctly. Misconfigured status mapping causes records to land in the wrong Nutshell record type.

  • Workflows, sequences, and automations do not migrate

    mQuest workflows and automated sequences are platform-specific logic that does not export to external systems. Nutshell's automation capabilities including personal email sequences in Nutshell Pro must be rebuilt manually by the admin after migration completes. We provide an exported list of mQuest workflow definitions as a reference document for your Nutshell admin to use during the manual rebuild process. This reference captures the workflow names, trigger conditions, and action sequences defined in mQuest.

  • Reports and dashboards are not migrated — underlying data does transfer

    mQuest custom reports and dashboards are platform-specific constructs that reference mQuest-specific fields, objects, and calculations that do not exist in Nutshell. These reports cannot migrate between platforms due to fundamental differences in the data model and reporting engine. The underlying data including contacts, companies, deals, and activities does transfer. After migration, Nutshell's built-in reporting covers pipeline metrics, activity summaries, and team performance. Any custom Nutshell reports must be rebuilt by the admin post-migration.

Migration approach

Six steps for a successful mQuest to Nutshell data migration

  1. Audit mQuest data model and custom field inventory

    Before writing any data to Nutshell, we pull the full mQuest object schema including all standard and custom fields on contacts, companies, deals, and activities. We generate a data-quality report flagging missing required fields, duplicate records, and owner email gaps. This audit determines how many Nutshell custom fields need to be created and which mQuest status values require a lead-person split decision from the admin.

  2. Create Nutshell custom fields and configure pipeline stages

    Based on the audit, we deliver a Nutshell setup checklist: which custom fields to create on People, Companies, Leads, and Deals; what field type to use (text, number, date, choice); and which mQuest status values map to Nutshell Lead status. The admin creates these fields in Nutshell before the migration run. We also configure the Nutshell pipeline so stage names align with mQuest deal stages. This step ensures the destination schema is ready before any data lands.

  3. Resolve owners and validate user accounts in Nutshell

    We match mQuest owner records to existing Nutshell users by email address. For owners with no matching Nutshell user, we generate a resolution report listing the unmatched email addresses and record counts. The admin either creates Nutshell user accounts for those emails before migration or assigns a fallback owner. No record migrates without a confirmed Nutshell owner assignment to prevent orphaned data.

  4. Run sample migration with field-level diff

    We migrate a representative slice of data — typically 100–500 records covering a sample of People, Companies, Leads, Deals, and Activities — and generate a field-level diff. The diff shows every source field, its mapped Nutshell field, the transferred value, and any transformation applied. The admin reviews the diff to confirm that contact-to-lead splitting logic, custom field values, and activity associations look correct before the full migration commits.

  5. Execute full migration with delta-pickup cutover

    The full migration runs against Nutshell's API, processing all People, Companies, Leads, Deals, Activities, and attachments. A delta-pickup window of 24–48 hours after the full run captures any records created or modified in mQuest during the cutover period. An audit log records every operation throughout the process. One-click rollback is available if post-migration reconciliation finds discrepancies exceeding the agreed tolerance threshold.

Platform deep dives

Context on both ends of the pair

mQuest logo

mQuest

Source

Strengths

  • Unified job lifecycle from dispatch through completion and customer sign-off in a single FSM interface.
  • Mobile app support for technicians to update job status, add notes, and capture signatures on-site.
  • Customer and site management tied directly to work orders without requiring separate address book imports.
  • Survey-triggered feedback collection after job completion provides immediate service quality signal.
  • Asset tracking linked to service history helps maintenance teams understand equipment failure patterns.

Weaknesses

  • No publicly documented REST API means integrations require manual exports, CSV workarounds, or vendor-assisted data pulls.
  • Reporting and analytics are limited to standard job summaries; custom dashboards require third-party tools.
  • Pricing and tier details are not published on the vendor site, complicating budget planning during evaluation.
  • Feature set is oriented toward complex field service operations and may feel oversized for smaller service teams with simple scheduling needs.
  • Multi-location or franchise-level management capabilities appear limited compared to enterprise FSM platforms.
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 mQuest 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

    mQuest: Not publicly documented..

  • Data volume sensitivity

    A

    mQuest exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most mQuest-to-Nutshell migrations complete within 24–72 hours for datasets under 25,000 records. Larger datasets with 200,000+ records or complex custom field configurations extend to 5–10 days. The longest step is typically the custom field setup in Nutshell and owner-resolution review before the migration run — the migration execution itself is throttled to respect Nutshell API rate limits, which keeps the data safe but adds time for high-volume activity histories.

Adjacent paths

Related migrations to explore

Ready when you are

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