CRM migration
Field-level mapping, validation, and rollback between Market Leader and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Market Leader
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Market Leader and Nutshell.
Complexity
BStandard
Timeline
3–5 days
Overview
Market Leader organizes its CRM around lead products (Lead Stream, Network Boost) and drip campaign enrollment — contacts exist within product-campaign pairs with stage progression tracked per drip sequence. This architecture means every contact record carries implicit context from the product and campaign that generated it, with enrollment status, current stage, and step number tied together. Nutshell uses a traditional Person-Company-Deal model with custom fields available on every object type, providing flexibility for capturing additional data points without restructuring the core data model. The migration carries all Market Leader people, companies, and deal records into Nutshell, with lead product source, drip enrollment status, campaign stage, and step number preserved as custom fields on person and deal records. This approach maintains visibility into each contact's origin and drip campaign history, even though the underlying routing logic differs between platforms. Drip campaign logic — enrollment triggers, sequence steps, and stage transitions — cannot migrate directly because Nutshell's automation engine operates differently; we export the campaign definitions as a rebuild reference for your Nutshell admin to reconstruct equivalent automation sequences. Reports and dashboards are data-backed but must be rebuilt in Nutshell's reporting module, as the field names and schema structures differ between platforms.
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 Leader 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 Leader
Contact / Person
Nutshell
Person
1:1Market Leader people map directly to Nutshell Person records. All standard fields (name, email, phone, address) transfer 1:1. Nutshell stores the person's account as a separate Company record linked via a person-company relationship, so the contact-to-company link requires that the Company mapping resolves first.
Market Leader
Lead (unconverted Market Leader contact)
Nutshell
Lead
1:1Market Leader contacts in a pre-conversion state map to Nutshell Lead records. Lead status in Market Leader maps to a custom pick-list field in Nutshell since Nutshell's built-in Lead Status field uses a different value set. Historical lead scores from Market Leader migrate as a custom number field on the Lead.
Market Leader
Company / Account
Nutshell
Company
1:1Market Leader company records map 1:1 to Nutshell Company records. All standard company fields (name, domain, industry, employee count, annual revenue) transfer directly. Company hierarchies in Market Leader (parent-child relationships) are preserved using Nutshell's parent-company field on the Company object.
Market Leader
Deal / Transaction
Nutshell
Deal
1:1Market Leader deals map to Nutshell Deal records. Deal name, amount, expected close date, and stage transfer directly. The deal owner resolves via email match against Nutshell users. Deals associated with a specific lead product carry that association as a custom field (Lead_Product_Source__c) so teams can still filter deals by their Market Leader product origin.
Market Leader
Lead Product (Network Boost, Lead Stream, etc.)
Nutshell
Custom field on Person and Deal
1:1Market Leader lead products have no direct equivalent in Nutshell's object model. We preserve the product name as a custom field (Lead_Product__c) on both the Person record and the associated Deal record. Teams use this field in Nutshell to segment reports by Market Leader product source without rebuilding the product-routing logic.
Market Leader
Drip Campaign Enrollment
Nutshell
Custom fields on Person
1:1Market Leader tracks drip enrollment status (enrolled, active, completed, paused) and current stage per campaign per person. Nutshell has no drip enrollment object, so we create custom fields: Drip_Campaign__c (campaign name), Drip_Stage__c (current stage), Drip_Step__c (step number), and Drip_Enrolled__c (boolean). These are display-only in Nutshell — the actual drip logic must be rebuilt in Nutshell's email sequences.
Market Leader
Drip Campaign Definition
Nutshell
Not migratable — exported as reference document
1:1Market Leader drip campaign definitions (step sequence, triggers, delays, conditions) have no structural equivalent in Nutshell's automation engine. We export campaign definitions as a structured JSON and PDF reference so your Nutshell admin can rebuild the logic in Nutshell's automation builder. This is not an automated migration step — it is a documentation deliverable.
Market Leader
Custom Contact Properties
Nutshell
Custom fields on Person
1:1Any custom properties configured in Market Leader (beyond standard fields) migrate to Nutshell custom fields on the Person object. Nutshell supports custom fields for Person, Company, Lead, and Deal. Field type is preserved: text fields stay text, pick-lists map to Nutshell pick-lists, date fields map to Nutshell date fields. The Enterprise plan offers unlimited custom fields; lower plans have limits that must be verified before migration.
Market Leader
Task / Activity Log
Nutshell
Activity on Person record
1:1Activity history from Market Leader (calls logged, emails sent, meetings scheduled) migrates as Nutshell activities attached to the Person record. Timestamps and activity owners are preserved. Nutshell's activity feed on the Person record surfaces this history natively, so teams retain the full engagement timeline from Market Leader.
Market Leader
Report / Dashboard
Nutshell
Not migratable — data-backed rebuild
1:1Market Leader report definitions and dashboard layouts cannot migrate to Nutshell because the schema and field names differ. The underlying data — deal amounts, pipeline stages, activity counts — does migrate. We deliver a report-mapping document that identifies each Market Leader report and its equivalent in Nutshell's reporting module so your admin can rebuild them with the correct field references.
| Market Leader | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person | Person1:1 | Fully supported | |
| Lead (unconverted Market Leader contact) | Lead1:1 | Fully supported | |
| Company / Account | Company1:1 | Fully supported | |
| Deal / Transaction | Deal1:1 | Fully supported | |
| Lead Product (Network Boost, Lead Stream, etc.) | Custom field on Person and Deal1:1 | Fully supported | |
| Drip Campaign Enrollment | Custom fields on Person1:1 | Fully supported | |
| Drip Campaign Definition | Not migratable — exported as reference document1:1 | Fully supported | |
| Custom Contact Properties | Custom fields on Person1:1 | Fully supported | |
| Task / Activity Log | Activity on Person record1:1 | Fully supported | |
| Report / Dashboard | Not migratable — data-backed rebuild1: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 Leader gotchas
Contracted lead products are not native CRM objects
No documented public API for automated data extraction
Lead phone numbers frequently absent from exported records
Drip sequence logic cannot be ported as-is to non-Market Leader platforms
Cancellation notification buried in contract requires 60-day advance notice
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 Leader data and design Nutshell target schema
FlitStack AI reviews all Market Leader lists — People, Companies, Deals, and any drip campaign enrollment data — via the data extract. We document the full field inventory, custom property count, and lead product list. We then design the Nutshell target schema: standard field mappings, custom field definitions (Lead_Product__c, Drip_Enrolled__c, Drip_Stage__c, Drip_Campaign__c, Drip_Step__c, Lead_Score__c), and the drip campaign export format. The schema plan is delivered for your Nutshell admin to implement before the migration runs.
Resolve owners by email match against Nutshell users
Market Leader owner records are matched to Nutshell users by email address. Any owner in Market Leader without a corresponding Nutshell user account is flagged before migration begins. Your team either creates the Nutshell user account first or assigns those records to a designated fallback owner. No record lands in Nutshell without a valid owner reference; this prevents orphaned deals and unowned person records at go-live.
Migrate companies first, then people, then deals
Nutshell requires Company records to exist before Person records can link to them via CompanyId. Similarly, deals reference people via the person-company relationship. We sequence the migration so that Company records resolve first (including stub companies for contacts without an explicit Market Leader company record), then Person records resolve with their CompanyId links, then Deals resolve with their linked Person records and custom Lead_Product__c field. This foreign-key ordering ensures referential integrity at the point of data landing.
Run a sample migration with field-level diff
A representative slice of 100–500 records — spanning People, Companies, Deals, and drip-enrolled contacts — migrates into Nutshell first. We generate a field-level diff comparing source values to destination values for every mapped field. You verify drip enrollment mapping (Drip_Enrolled__c, Drip_Stage__c), lead product assignment (Lead_Product__c on Person and Deal), owner resolution, and custom field population. Approval of the sample unlocks the full migration run.
Execute full migration with delta-pickup window
The full data migration runs against Nutshell while your team continues working in Market Leader with scoped read access. A delta-pickup window (typically 24–48 hours) captures any new records or modifications made in Market Leader during the cutover. An audit log records every operation. One-click rollback is available if post-migration reconciliation finds discrepancies. We deliver the drip campaign export (JSON and PDF) as a rebuild reference for your Nutshell admin to recreate the automation logic.
Platform deep dives
Market Leader
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Market Leader and Nutshell.
Object compatibility
1 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
Market Leader: Not publicly documented..
Data volume sensitivity
Market Leader 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 Leader to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Market Leader 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 Leader
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.