CRM migration
Field-level mapping, validation, and rollback between MARS and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
MARS
Source
Nutshell
Destination
Compatibility
9 of 12
objects map 1:1 between MARS and Nutshell.
Complexity
CModerate
Timeline
2-4 weeks
Overview
Moving from MARS to Nutshell is a structural migration that requires careful sequencing of record dependencies. MARS stores Contacts, Companies, Deals, and Activities in a standard CRM object model with pipeline stages and owner assignment. Nutshell uses People (contacts), Companies, Deals, Activities, and per-entity custom fields. We sequence the export by pulling primary objects first, resolving account-company lookups before contact insert, and batch-loading activity history with original timestamps preserved. Custom fields migrate as their Nutshell native type, with any MARS field type lacking a direct Nutshell equivalent flagged for manual resolution during scoping. Nutshell's automation features (follow-up pipelines, auto-assignment rules) do not migrate; we deliver a written inventory of these for the customer's admin to rebuild post-migration.
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 MARS 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.
MARS
Contact
Nutshell
Person
1:1MARS Contacts map directly to Nutshell People. The MARS contact name fields split into first_name and last_name per Nutshell schema. Email address serves as the dedupe key. Any MARS contact with a linked Company maps with the Nutshell Company lookup resolved at migration time. We preserve MARS owner assignment in the Person record for reconciliation.
MARS
Company
Nutshell
Company
1:1MARS Companies map directly to Nutshell Companies. Company name is the primary key. Domain and address fields migrate as text fields. We resolve any Person-to-Company linkage from MARS at migration time and recreate the lookup in Nutshell. Nutshell does not have automatic domain-based dedupe for companies, so we use company name matching with manual review of near-duplicates.
MARS
Deal
Nutshell
Deal
1:1MARS Deals map to Nutshell Deals. The MARS pipeline and stage assignment maps to a Nutshell pipeline with equivalent stage names. We preserve deal value, expected close date, owner assignment, and the linked Company as the Nutshell Company lookup. If MARS tracks deal probability, we store it in a custom numeric field in Nutshell since Nutshell does not have native probability weights on Deals.
MARS
Pipeline
Nutshell
Pipeline
lossyMARS pipeline definitions map to Nutshell pipeline configuration. Each MARS pipeline becomes a Nutshell pipeline with stage labels recreated. Stage order and stage type (open, won, lost) map to Nutshell's stage definition model. We configure pipelines in Nutshell before Deal import begins.
MARS
Owner
Nutshell
User
1:1MARS owners map to Nutshell users by email match. We extract every distinct owner referenced on Contact, Company, and Deal records and match against Nutshell users. Owners without a matching Nutshell user enter a reconciliation queue for the customer's admin to provision before Deal import continues.
MARS
Activity: Call
Nutshell
Activity (call type)
1:1MARS call engagements map to Nutshell Activities of type call. Call duration, disposition, and timestamp migrate to Nutshell Activity fields. The activity links to the Person record by email lookup. We batch calls in groups of 500 and insert via Nutshell's API with rate-limit handling.
MARS
Activity: Email
Nutshell
Activity (email type)
1:1MARS email engagements map to Nutshell Activities of type email. Email subject, body (plain text), and timestamp migrate. Attachments are not supported as native Nutshell activity fields; we store attachment file names in a custom text field and flag attachments for manual retrieval from MARS export files.
MARS
Activity: Meeting
Nutshell
Activity (meeting type)
1:1MARS meeting engagements map to Nutshell Activities of type meeting. Meeting title, date, location, and attendee list migrate. We link attendees to Nutshell Person records by email match. If MARS meeting records include notes, those migrate as the activity description.
MARS
Activity: Task
Nutshell
Activity (task type)
1:1MARS task engagements map to Nutshell Activities of type task. Task title, due date, completion status, and priority migrate. Owner assignment resolves via the User mapping. Completed flag maps to Nutshell completed status. We use original MARS timestamps for activity ordering.
MARS
Activity: Note
Nutshell
Activity (note type)
1:1MARS note engagements map to Nutshell Activities of type note. Note body migrates as the activity description field. We link notes to the Person, Company, or Deal record they were attached to in MARS via lookup resolution at migration time. Rich text formatting is converted to plain text.
MARS
Custom Field (Contact)
Nutshell
Custom Field (Person)
lossyMARS custom fields on Contact map to Nutshell custom fields on Person. We map field types: text to text, number to number, date to date, dropdown to dropdown, checkbox to checkbox. Any MARS field type without a direct Nutshell equivalent (such as multi-select or formula fields) is flagged for scoping and either converted to a compatible type or excluded with a written recommendation.
MARS
Custom Field (Company)
Nutshell
Custom Field (Company)
lossyMARS custom fields on Company map to Nutshell custom fields on Company using the same type-mapped approach. Nutshell supports custom fields on Company, Person, and Lead entities independently, so MARS entity-specific custom fields map to their Nutshell equivalents.
| MARS | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Owner | User1:1 | Fully supported | |
| Activity: Call | Activity (call type)1:1 | Fully supported | |
| Activity: Email | Activity (email type)1:1 | Fully supported | |
| Activity: Meeting | Activity (meeting type)1:1 | Fully supported | |
| Activity: Task | Activity (task type)1:1 | Fully supported | |
| Activity: Note | Activity (note type)1:1 | Fully supported | |
| Custom Field (Contact) | Custom Field (Person)lossy | Fully supported | |
| Custom Field (Company) | Custom Field (Company)lossy | 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.
MARS gotchas
Low public information
Vendor-implemented deployments vary widely
No public API documented
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
Discovery and data audit
We audit the MARS source environment for object counts (Contacts, Companies, Deals, Activities by type), custom field definitions (name, type, entity scope), pipeline structures (stages, owners), and relationship tables (Contact-to-Company, Deal-to-Contact, Activity-to-Contact). We extract a representative data sample (50-100 records per object) to validate field type mapping and identify any MARS field types lacking a Nutshell equivalent. The discovery output is a written migration scope with a field mapping table, a list of MARS automations requiring rebuild, and a Nutshell plan recommendation (Foundation through Enterprise) based on feature requirements.
Nutshell schema pre-configuration
We create all required Nutshell custom fields (per Company, Person, and Lead entity), configure pipelines with stage labels matching the MARS pipeline structure, and set up user accounts for any MARS owners that do not yet have a Nutshell user. We deploy schema changes in the customer's Nutshell environment before any data import. Any MARS field without a direct Nutshell type is flagged with a type-conversion recommendation for customer approval before migration begins.
Dependency-ordered export and cross-reference
We extract MARS data in dependency order: Companies (first, no dependencies), Contacts (with Company lookup resolved), Deals (with Contact and Company lookups resolved), then Activities (with Contact lookup resolved). We build a cross-reference table mapping MARS record IDs to destination Nutshell IDs as each batch inserts successfully. This cross-reference is required for subsequent batches to resolve parent-record lookups correctly. We export all custom field data alongside the standard object export and validate field type consistency against the Nutshell schema pre-configured in step two.
Sandbox validation and reconciliation
We run a full migration into a test environment using production-like data volume. The customer's admin reviews record counts, spot-checks 25-50 random records against the MARS source, and validates that custom fields populated correctly and that activity timelines are complete. Any mapping corrections (field name mismatches, type conversion errors, duplicate resolution decisions) are documented and applied to the production migration plan. Sign-off on the sandbox validation gates the production cutover.
Production migration and delta sync
We run production migration in the validated dependency order. Each phase emits a row-count reconciliation report before the next phase begins. We freeze MARS writes during cutover and run a final delta migration of any records modified during the migration window. Activities migrate via chunked API insert with exponential backoff. Owner reconciliation is verified before Deal import begins because OwnerId is required on Deals.
Cutover, validation, and automation rebuild handoff
We enable Nutshell as the system of record after validating record counts match across all objects and the delta migration confirms no new records were created in MARS during cutover. We deliver the automation inventory document listing every MARS workflow, trigger, and assignment rule with a recommended Nutshell equivalent (manual action, Nutshell follow-up automation, or third-party integration). We support a one-week hypercare window for reconciliation issues raised by the sales team. Nutshell follow-up pipeline configuration is a separate admin task post-migration.
Platform deep dives
MARS
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 8 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across MARS and Nutshell.
Object compatibility
8 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
MARS: Not publicly documented..
Data volume sensitivity
MARS 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 MARS to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your MARS 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 MARS
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.