CRM migration

Migrate from MARS to Nutshell

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

MARS logo

MARS

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

9 of 12

objects map 1:1 between MARS and Nutshell.

Complexity

CModerate

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

MARS logo

MARS

What's pushing teams away

  • Limited public footprint makes peer validation impossible and slows due diligence.
  • No publicly documented developer API restricts integration into modern BI, marketing, and automation tools.
  • Smaller vendor scale translates to thinner partner ecosystem and integration libraries.
  • Mobile, cloud-native UX, and modern admin tooling typically lag market leaders.
  • Pricing and contract terms are sales-led with no transparency for early-stage evaluation.

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

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

maps to

Nutshell

Person

1:1
Fully supported

MARS 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

maps to

Nutshell

Company

1:1
Fully supported

MARS 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

maps to

Nutshell

Deal

1:1
Fully supported

MARS 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

maps to

Nutshell

Pipeline

lossy
Fully supported

MARS 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

maps to

Nutshell

User

1:1
Fully supported

MARS 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

maps to

Nutshell

Activity (call type)

1:1
Fully supported

MARS 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

maps to

Nutshell

Activity (email type)

1:1
Fully supported

MARS 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

maps to

Nutshell

Activity (meeting type)

1:1
Fully supported

MARS 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

maps to

Nutshell

Activity (task type)

1:1
Fully supported

MARS 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

maps to

Nutshell

Activity (note type)

1:1
Fully supported

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

maps to

Nutshell

Custom Field (Person)

lossy
Fully supported

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

maps to

Nutshell

Custom Field (Company)

lossy
Fully supported

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

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.

MARS logo

MARS gotchas

High

Low public information

High

Vendor-implemented deployments vary widely

Medium

No public API documented

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 per-entity custom fields require pre-configuration

    Nutshell custom fields are scoped per entity (Company, Person, Lead) and must be created in the Nutshell Setup before data import. MARS custom fields do not auto-create in Nutshell. We add a pre-migration step to create every MARS custom field in Nutshell with the matching field type, apply field labels, and set any required flags. If a MARS field type (multi-select, formula, rollup) has no direct Nutshell equivalent, we flag it during scoping and recommend a compatible type or a manual workaround. Skipping this step causes import failures on any record with custom field data.

  • MARS export requires coordinated sequencing to satisfy dependencies

    MARS records have foreign-key dependencies: Contacts reference Companies, Deals reference Contacts and Companies, Activities reference Contacts. We export in dependency order (Companies first, then Contacts, then Deals, then Activities) to ensure parent-record IDs are resolved at migration time. If a customer exports MARS data in a single flat file without dependency resolution, duplicate Person records and orphaned Deal links result. We extract and cross-reference the relationship table during scoping to validate the dependency graph before any API insert operations begin.

  • Activity batch sizes must respect Nutshell API rate limits

    Nutshell's REST API enforces rate limits on bulk insert operations. We use exponential backoff with chunking for activity records (calls, emails, meetings, tasks, notes), batching 200-500 records per request depending on payload size. Activity timestamps are preserved by setting the Nutshell activity date to the original MARS timestamp. Without chunking and backoff, API throttling causes timeout errors that silently drop activity batches, leaving gaps in the contact timeline.

  • Nutshell does not support automatic domain-based company dedupe

    MARS uses domain-based deduplication to merge duplicate company records automatically. Nutshell does not have automatic company deduplication; we rely on name-based matching with a manual review step for near-duplicates. During scoping, we run a fuzzy match on MARS company names to identify potential duplicates before insert and resolve them into a single Nutshell Company record with merged custom field values from the MARS source records.

  • Follow-up pipeline automation and workflows do not migrate

    Nutshell's follow-up pipeline automation and auto-assignment rules are Nutshell-specific configurations that do not import from MARS. We deliver a written inventory of any MARS workflow triggers, automation rules, and assignment logic as a separate document for the customer's admin to rebuild in Nutshell. Standard Nutshell follow-up features (available at Business tier and above) are available post-migration but require manual configuration.

Migration approach

Six steps for a successful MARS to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

MARS logo

MARS

Source

Strengths

  • Configurable to domain-specific workflows.
  • Direct vendor relationship for support and customization.
  • On-premise or private-cloud deployment options.
  • Tenant-specific schema flexibility.
  • Responsive support during onboarding (typical of smaller vendors).

Weaknesses

  • Limited public reviewer presence.
  • No publicly documented developer API.
  • Smaller integration ecosystem.
  • Mobile and cloud-native UX lags.
  • Sales-led pricing with limited transparency.
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?

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

C

Overall complexity

Moderate migration

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

  • Object compatibility

    D

    8 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

    MARS: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between two and four weeks for accounts under 15,000 People, 3,000 Deals, and no custom objects with complex type mappings. Migrations with multiple custom fields, multi-stage pipeline structures, large activity histories (over 100,000 engagement records), or MARS field types requiring type conversion move to six to ten weeks because of schema pre-configuration time, batch chunking for activities, and reconciliation scope.

Adjacent paths

Related migrations to explore

Ready when you are

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