CRM migration
Field-level mapping, validation, and rollback between mQuest and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
mQuest
Source
Nutshell
Destination
Compatibility
13 of 14
objects map 1:1 between mQuest and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
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.
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 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
Nutshell
Person
1:1mQuest 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)
Nutshell
Lead
1:manymQuest 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
Nutshell
Company
1:1mQuest 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
Nutshell
Deal
1:1mQuest 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
Nutshell
Deal Pipeline Stages
1:1mQuest 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)
Nutshell
Custom Field (on Person)
1:1mQuest 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)
Nutshell
Custom Field (on Company)
1:1mQuest 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)
Nutshell
Custom Field (on Deal)
1:1mQuest 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)
Nutshell
Activity
1:1mQuest 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)
Nutshell
Activity
1:1mQuest 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)
Nutshell
Activity
1:1mQuest 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)
Nutshell
Activity
1:1mQuest 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
Nutshell
Nutshell User
1:1mQuest 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
Nutshell
File
1:1mQuest 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.
| mQuest | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person | Person1:1 | Fully supported | |
| Contact (inactive or unqualified status) | Lead1:many | Fully supported | |
| Company / Account | Company1:1 | Fully supported | |
| Deal / Opportunity | Deal1:1 | Fully supported | |
| Pipeline | Deal Pipeline Stages1:1 | Fully supported | |
| Custom Field (on Contact) | Custom Field (on Person)1:1 | Fully supported | |
| Custom Field (on Company) | Custom Field (on Company)1:1 | Fully supported | |
| Custom Field (on Deal) | Custom Field (on Deal)1:1 | Fully supported | |
| Activity (Call) | Activity1:1 | Fully supported | |
| Activity (Email) | Activity1:1 | Fully supported | |
| Activity (Meeting) | Activity1:1 | Fully supported | |
| Activity (Note) | Activity1:1 | Fully supported | |
| Owner / User | Nutshell User1:1 | Fully supported | |
| Attachment / File | File1: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.
mQuest gotchas
No public API documented for programmatic data extraction
Custom field schemas vary by tenant with no published reference
Invoiced job data may require fiscal-period alignment
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 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.
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.
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.
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.
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
mQuest
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 mQuest 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
mQuest: Not publicly documented..
Data volume sensitivity
mQuest exposes a bulk API — large-volume migrations stream efficiently.
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 mQuest to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your mQuest 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 mQuest
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.