CRM migration
Field-level mapping, validation, and rollback between LeadSmart Channel Cloud and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
LeadSmart Channel Cloud
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between LeadSmart Channel Cloud and Nutshell.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Migrating from LeadSmart Channel Cloud to Nutshell is a structural simplification. LeadSmart Channel Cloud extends Salesforce Lightning with a Partner Collaboration Portal and vertical custom objects for manufacturers and distributors; Nutshell is an SMB-focused CRM with a unified People object (no separate Leads), a flat Deals model, and a simpler configuration surface. The core migration challenge is resolving LeadSmart's standard Salesforce Lead and Contact objects into Nutshell's single People record with a status field, and handling LeadSmart's industry-specific custom fields against Nutshell's CSV-import column constraints. We flag the Genius Feed and Genius GPT AI records as excluded because they store proprietary recommendation logic tied to LeadSmart's engine. Partner Portal external partner records require a separate mapping pathway to Nutshell People records with a role field. Workflows, automations, and Partner Portal sharing rules do not migrate; we deliver a written inventory 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 LeadSmart Channel Cloud 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.
LeadSmart Channel Cloud
Lead
Nutshell
People
1:1LeadSmart Lead records map to Nutshell People. The Lead Status field from Salesforce maps to a custom People status field that we create during migration setup to distinguish converted (Contact) from unconverted (Lead) records. We preserve the original Lead Score if present as a custom People field. Email, phone, company name, address, and owner transfer directly. LeadSmart's Lead object is the first object imported because People is the primary entity in Nutshell.
LeadSmart Channel Cloud
Contact
Nutshell
People
1:1LeadSmart Contact records map to Nutshell People using email as the dedupe key. We apply the same status-field strategy as for Leads, setting the custom People status to Contact for records where the source object type was Contact. If a Lead and Contact share the same email address (common post-conversion in Salesforce), we merge into a single People record and preserve both originating record IDs in custom fields for audit. LeadSmart's industry-specific custom contact fields require individual mapping to Nutshell custom fields or supplemental CSV export.
LeadSmart Channel Cloud
Account
Nutshell
Company
1:1LeadSmart Account records map to Nutshell Company. The Account Name maps to Company name, and website maps to the Company web address field. Account hierarchies (parent-account relationships for manufacturer-distributor-dealer chains) do not have a native equivalent in Nutshell; we store the parent Account ID in a custom field on the child Company record and recommend the customer manually rebuild the hierarchy in Nutshell's Company list or use a naming convention to reflect the relationship. We extract all Account custom fields for mapping or supplemental export.
LeadSmart Channel Cloud
Opportunity
Nutshell
Deal
1:1LeadSmart Opportunity records map to Nutshell Deal. The Opportunity Name becomes Deal name, Amount maps to Deal value, CloseDate maps to expected close date, StageName maps to a Nutshell pipeline stage, and OwnerId resolves to the Nutshell User by email match. We configure the Nutshell pipeline stages to match the LeadSmart opportunity stage names before migration so that Deals land in the correct status. Discount and probability fields migrate as custom Deal fields.
LeadSmart Channel Cloud
Task and Event
Nutshell
Activity
1:1LeadSmart Task and Event records map to Nutshell Activity. Completed tasks migrate with subject, status, priority, and activity date preserved. Events (meetings) migrate with start time, end time, location, and description. Call logs from LeadSmart as Task subtype Call migrate as Nutshell Activities with a call type flag. Each Activity is linked to the parent People or Deal by resolving the WhoId and WhatId from Salesforce to the migrated Nutshell IDs. Large activity histories (over 100,000 records) are chunked and loaded via Nutshell's bulk CSV import with pagination.
LeadSmart Channel Cloud
Partner Portal Records
Nutshell
People (with role field)
lossyLeadSmart Partner Portal records represent external channel partners (reps, brokers, dealers, distributors) with distinct sharing-rule visibility. These have no native Nutshell equivalent. We map them to Nutshell People records and assign a custom role field (e.g., Distributor, Dealer, Broker, Manufacturer Rep) to preserve the partner classification. We do not migrate the Partner Portal's sharing-rule configuration because Nutshell lacks a sharing-model equivalent; the customer documents their visibility requirements for post-migration admin setup.
LeadSmart Channel Cloud
Marketing Campaign
Nutshell
Campaign
1:1LeadSmart Campaign records map to Nutshell Campaign. Campaign name, type, status, and start/end dates migrate directly. Campaign Member records (contacts and leads enrolled in a campaign) migrate as Campaign Member records linked to the corresponding Nutshell People records. LeadSmart's custom marketing automation fields on campaigns require individual field mapping against Nutshell's campaign object columns.
LeadSmart Channel Cloud
Genius Feed Insights
Nutshell
Excluded (documented)
1:1LeadSmart's Genius Feed AI records store proactive customer issue and growth opportunity insights in a proprietary format tied to the platform's recommendation engine. Nutshell has no AI insights feature and no equivalent object schema. We document each Genius Feed record with its associated People and Deal IDs and deliver it as a supplemental export file. The customer can review this data manually or use it as input for rebuilding insights in a separate AI tool. This exclusion is signed off before migration begins.
LeadSmart Channel Cloud
Attachment and Files
Nutshell
Attachment (linked to People, Company, or Deal)
1:1LeadSmart Files and Attachments (stored in Salesforce as ContentDocument with ContentDocumentLink) migrate to Nutshell Attachments. We extract file content, file name, and the parent record type and ID, then link each attachment to the corresponding migrated Nutshell People, Company, or Deal record. Large binary attachments are chunked for transfer. PDF and image attachments preserve content type metadata.
LeadSmart Channel Cloud
User
Nutshell
User
1:1LeadSmart User records map to Nutshell Users by email match. We extract name, email, role, and active status from the Salesforce User object. Any LeadSmart User referenced as an Opportunity or Task owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before the migration continues. Inactive LeadSmart Users migrate as inactive Nutshell Users to preserve historical assignment.
| LeadSmart Channel Cloud | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | People1:1 | Fully supported | |
| Contact | People1:1 | Fully supported | |
| Account | Company1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Task and Event | Activity1:1 | Fully supported | |
| Partner Portal Records | People (with role field)lossy | Mapping required | |
| Marketing Campaign | Campaign1:1 | Fully supported | |
| Genius Feed Insights | Excluded (documented)1:1 | Mapping required | |
| Attachment and Files | Attachment (linked to People, Company, or Deal)1:1 | Fully supported | |
| User | User1: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.
LeadSmart Channel Cloud gotchas
LeadSmart Partner Portal external users use distinct sharing rules
Genius GPT and Genius Feed are proprietary AI objects with no migration path
Custom fields added by LeadSmart may not map to standard CRM equivalents
Annual vs monthly pricing affects migration timing decisions
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 scoping call
We audit the LeadSmart Channel Cloud instance across the full object inventory, custom fields, active pipelines, opportunity stage values, Partner Portal record count, engagement volume, and file attachments. We identify any LeadSmart-specific custom objects beyond standard Salesforce. We document the Genius Feed and Genius GPT record counts for the exclusion sign-off. The discovery output is a written migration scope with object-level mapping, a custom field inventory, and a timeline estimate. We also review the customer's Nutshell environment to confirm the target plan tier and any pre-existing custom fields that may conflict with migrating field names.
Schema design and custom field mapping
We design the destination schema in Nutshell before any data moves. This includes creating the People status custom field (to differentiate Lead vs Contact records from LeadSmart), any custom fields needed for LeadSmart's industry-specific data that cannot fit in Nutshell's standard columns, and mapping LeadSmart's opportunity stage names to Nutshell pipeline stages. We also create the custom role field on People for Partner Portal records. If the custom field count exceeds Nutshell's CSV import column limits, we flag the overflow fields for supplemental export and confirm the approach with the customer before proceeding.
Sandbox migration and reconciliation
We run a test migration into the customer's Nutshell environment using a representative data sample (typically 10-15 percent of total records across each object type). The customer reviews the migrated records for accuracy: People records are spot-checked against the source LeadSmart Contacts and Leads, Deals are verified against Opportunity data, and activity timelines are confirmed. Any mapping corrections, missing fields, or dedupe conflicts surface here and are resolved before production migration begins. The customer signs off on the People status field strategy and the Partner Portal People mapping approach at this stage.
Owner and user reconciliation
We extract every distinct LeadSmart User referenced as an owner on Lead, Contact, Opportunity, or Activity records. We match each by email against the Nutshell User list. Any LeadSmart owner without a matching Nutshell User goes to a reconciliation queue. The customer's Nutshell admin provisions missing Users (active or inactive depending on whether the person is still with the organization) before record import resumes. Migration cannot proceed past this step because Deal and Activity imports require a valid owner reference.
Production migration in dependency order
We run production migration in record-dependency order: Nutshell Users first (manual provisioning validated), then People (Leads and Contacts merged with status field applied), then Companies (from LeadSmart Accounts with hierarchy stored in supplemental field), then Deals (with owner resolved and stage mapped), then Activities (Tasks and Events chunked and loaded), then Campaigns (with Campaign Members linked to People records), then Attachments (linked to the correct People, Company, or Deal). Each phase emits a row-count reconciliation report before the next phase begins. We freeze LeadSmart write access during the final delta phase to capture any records modified during the migration window.
Cutover, validation, and handoff documentation
We run a final delta migration of any records modified during the cutover window, then enable Nutshell as the system of record. We deliver the complete handoff package: a migration summary with total record counts per object, a list of excluded records (Genius Feed and Genius GPT) with associated record IDs, a list of overflow custom fields exported to supplemental CSV, a Partner Portal records summary with role classifications, and a written inventory of any LeadSmart Workflows or automations that require rebuild in Nutshell's workflow builder. We support a five-business-day hypercare window for reconciliation issues. We do not rebuild LeadSmart automations, Partner Portal sharing rules, or Genius AI insights as part of the migration scope.
Platform deep dives
LeadSmart Channel Cloud
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 LeadSmart Channel Cloud 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
LeadSmart Channel Cloud: Standard Salesforce API rate limits apply; not separately documented by LeadSmart.
Data volume sensitivity
LeadSmart Channel Cloud 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 LeadSmart Channel Cloud to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your LeadSmart Channel Cloud 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 LeadSmart Channel Cloud
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.