CRM migration
Field-level mapping, validation, and rollback between Market Maker and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Market Maker
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Market Maker and Nutshell.
Complexity
CModerate
Timeline
48–72 hours
Overview
Market Maker and Nutshell both organize sales data around contacts, companies, and deals, but they diverge in how they model leads, activities, and custom data. Nutshell consolidates People and Leads as separate record types within a single contact object, whereas Market Maker may use distinct lead and contact objects or a unified model with status flags. Nutshell stores activities (calls, emails, meetings) as timestamped entries linked to records, matching the activity-history model most CRMs use. The migration extracts all Market Maker records via API, maps standard fields (name, email, phone, company) directly to Nutshell's People object, and routes non-standard properties to custom fields. Owner resolution happens by email match against Nutshell user accounts. Custom objects and custom fields require destination-side creation before data lands — we deliver the schema plan upfront. Workflows, email sequences, and automation rules do not migrate; we export definitions as a rebuild reference for your Nutshell admin. The cutover includes a delta-pickup window capturing records modified during the switch so the destination reflects Market Maker's final state.
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 Market Maker 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.
Market Maker
Contact / Person
Nutshell
People
1:1Market Maker contact/person records map directly to Nutshell People. Name fields, email, phone, and address properties transfer as standard People fields. Primary company association maps to the Nutshell People-Companies relationship, and any custom person-level attributes become custom fields on the People object. Owner resolution by email match runs before records land, ensuring each contact is assigned to the correct Nutshell user.
Market Maker
Lead
Nutshell
Leads
1:1Market Maker leads with status indicating unqualified or early-stage prospects map to Nutshell Leads. Source attribution, lead score (if numeric), and any custom lead properties migrate as Nutshell custom fields on the Leads object. Lead status values map value-by-value to Nutshell lead stages.
Market Maker
Company / Account
Nutshell
Companies
1:1Market Maker company or account records map to Nutshell Companies. Company name, domain/website, industry, employee count, and annual revenue transfer as standard fields. Any custom company attributes become custom fields on the Companies object. Parent-child company hierarchies in Market Maker map to Nutshell's parent company reference if your account has that feature enabled, preserving corporate structure in the new CRM.
Market Maker
Deal / Opportunity
Nutshell
Nutshell Pipeline (Leads with Deals context)
1:1Market Maker deal or opportunity records requiring pipeline-stage tracking map to Nutshell's pipeline model. Each Market Maker pipeline stage becomes a Nutshell stage within your pipeline configuration. Deal amount, close date, and probability weight transfer; stage names require value-mapping if they differ from Nutshell defaults.
Market Maker
Activity / Engagement (Call, Email, Meeting)
Nutshell
Activities
1:1Market Maker activities (calls logged, emails sent, meetings scheduled) map to Nutshell Activities. Each activity records the type, date, linked person or company, and the user who logged it. Original timestamps and subject lines are preserved. Follow-up tasks generated from activities map as Nutshell Tasks.
Market Maker
Note / Comment
Nutshell
Notes
1:1Market Maker notes attached to contacts, companies, or deals transfer as Nutshell Notes. The note body, author, and timestamp map directly. Rich-text formatting is preserved where the source API returns it; plain-text fallback applies if HTML structures are not supported.
Market Maker
Attachment / File
Nutshell
Attachments
1:1Market Maker file attachments linked to records are downloaded from the source API and re-uploaded to the corresponding Nutshell record timeline. File size limits apply per Nutshell plan — files exceeding limits are flagged for manual handling. Inline images in notes are extracted and re-hosted as attachments.
Market Maker
Custom Object / Custom Entity
Nutshell
Custom Fields on Nutshell Objects
1:1Market Maker custom objects or entities that have no direct Nutshell equivalent become custom fields on the nearest standard object (People, Companies, or Leads). We deliver a custom-field creation plan specifying field name, type (text, number, date, pick-list), and which Nutshell object receives the field before migration runs.
Market Maker
User / Owner
Nutshell
User Resolution
1:1Market Maker owner IDs on records are resolved by matching the owner's email address to a Nutshell user account. Unmatched owners are flagged before migration — your team either creates Nutshell accounts or designates a fallback owner before the full run. No record lands without a valid Nutshell owner.
Market Maker
Tag / Label
Nutshell
Tags
1:1Market Maker tags or labels applied to contacts, companies, or deals migrate as Nutshell Tags. Tags are transferred as-is with no transformation. If a tag value in Market Maker does not exist in Nutshell, it is created during migration and associated with the relevant records.
Market Maker
Workflow / Automation Rule
Nutshell
No Equivalent
1:1Market Maker workflows, automation rules, and sequence logic do not transfer to Nutshell. Nutshell has its own automation capabilities that must be configured separately. We export your Market Maker workflow definitions as a structured document your Nutshell admin can use as a rebuild reference.
Market Maker
Report / Dashboard
Nutshell
No Equivalent
1:1Market Maker saved reports and dashboards cannot be imported into Nutshell — the underlying data migrates, but the report definitions require recreation. Nutshell's reporting module supports custom reports; we provide a data dictionary of migrated fields to accelerate the rebuild.
| Market Maker | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person | People1:1 | Fully supported | |
| Lead | Leads1:1 | Mapping required | |
| Company / Account | Companies1:1 | Fully supported | |
| Deal / Opportunity | Nutshell Pipeline (Leads with Deals context)1:1 | Fully supported | |
| Activity / Engagement (Call, Email, Meeting) | Activities1:1 | Fully supported | |
| Note / Comment | Notes1:1 | Fully supported | |
| Attachment / File | Attachments1:1 | Not supported | |
| Custom Object / Custom Entity | Custom Fields on Nutshell Objects1:1 | Fully supported | |
| User / Owner | User Resolution1:1 | Fully supported | |
| Tag / Label | Tags1:1 | Mapping required | |
| Workflow / Automation Rule | No Equivalent1:1 | Fully supported | |
| Report / Dashboard | No Equivalent1: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.
Market Maker gotchas
Directory rather than CRM
USDA/state participation varies
No public API
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 Market Maker data and build the mapping specification
FlitStack AI connects to your Market Maker account using scoped read access and extracts a full data inventory: record counts by object, field lists with data types, pick-list values, and custom property definitions. We cross-reference this against Nutshell's standard fields to identify direct mappings, value-mappings, and fields requiring custom field creation. The result is a mapping specification document you review and approve before any data moves. This step typically takes 2–5 business days depending on data complexity.
Create Nutshell custom fields and configure pipeline stages
Before migration runs, your Nutshell admin (or our team acting with your credentials) creates the custom fields identified in the mapping specification. Pipeline stages are configured to match Market Maker's stage names or are explicitly value-mapped. User accounts are provisioned for every active Market Maker owner so owner resolution can complete. This step is a prerequisite — migration cannot proceed until the destination schema matches the mapping specification.
Run a sample migration with field-level validation
FlitStack AI migrates a representative sample of your Market Maker data — typically 100–500 records across People, Companies, Leads, and a sample of Activities. We generate a field-level diff report showing source value versus destination value for every mapped field. You review the diff, approve the mapping, and flag any corrections. Sample migration validates the schema alignment, owner resolution, and value mapping before the full run commits any data.
Execute full migration with delta-pickup window
The full dataset migrates from Market Maker to Nutshell. Records process in dependency order (Companies first, then People, then Leads/Deals, then Activities and Attachments) to maintain referential integrity. A delta-pickup window of 24–48 hours after the primary migration run captures any records created or modified in Market Maker during cutover. FlitStack logs every operation to an audit trail. One-click rollback is available if reconciliation identifies unexpected discrepancies.
Validate migrated data and deliver post-migration handover package
FlitStack AI runs reconciliation checks: record counts by object, spot-checks on field values, owner assignment verification, and attachment file count. You receive a validation report with pass/fail status per object and a list of any records requiring manual review. The handover package includes the workflow export document, the migrated-field inventory for report rebuilding, and the delta-captured records merged into the final dataset. Post-migration support is available for 14 days.
Platform deep dives
Market Maker
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 5 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Market Maker and Nutshell.
Object compatibility
5 of 8 objects need a manual workaround.
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
Market Maker: Not applicable..
Data volume sensitivity
Market Maker 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 Market Maker to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Market Maker 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 Market Maker
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.