CRM migration
Field-level mapping, validation, and rollback between Smart CRM Online and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Smart CRM Online
Source
Nutshell
Destination
Compatibility
7 of 11
objects map 1:1 between Smart CRM Online and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Smart CRM Online to Nutshell is a flat-to-relational migration. Smart CRM Online has no documented API and exports Deals with a Company ID reference rather than structured parent-child relationships, so we reconstruct Contact-Deal and Company-Deal linkages by matching identifiers during the transform phase. We import Companies before Contacts to satisfy Nutshell's lookup requirements, then load Deals with explicit account and contact associations. Custom fields require a discovery-phase manual audit because Smart CRM Online does not publish its field schema. Pipeline Stages map to Nutshell's sales processes, and Activity history (calls, emails, meetings, tasks) migrates as Task and Event records linked to the parent Contact or Deal. Nutshell supports custom fields for Companies, People, and Leads from its Foundation tier, and API access is available at the Enterprise tier. We do not migrate any automations, workflows, or sequence cadences; these are documented for the customer's admin to rebuild in Nutshell.
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 Smart CRM Online 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.
Smart CRM Online
Company
Nutshell
Account
1:1Smart CRM Online Company records map directly to Nutshell Account. We import Accounts first in every run to satisfy the lookup requirement for Contacts and Deals. The Company name becomes Account name, and any Company phone, address, or domain fields map to the corresponding Nutshell Account fields. Company ID from Smart CRM Online is preserved as a reference field in a custom Account field for reconciliation purposes.
Smart CRM Online
Contact
Nutshell
Person
1:1Smart CRM Online Contact records map to Nutshell Person. Name, email, phone, title, and company association transfer directly. The Company association is resolved by matching the Smart CRM Online Company ID to the Nutshell Account created in the prior step. Any Contact without a matching Company is flagged and attached to a default placeholder Account pending admin confirmation.
Smart CRM Online
Deal
Nutshell
Lead
1:1Smart CRM Online Deal records map to Nutshell Lead when the deal represents an unqualified prospect, or to Nutshell Lead (in sales pipeline context) when migrating into Nutshell's standard workflow. Deal name, value, stage, owner, and close date transfer directly. The Smart CRM Online dealstage maps to the Nutshell pipeline stage, and we create a Nutshell sales process matching the stage order from the source export.
Smart CRM Online
Deal Stage
Nutshell
Pipeline Stage
lossySmart CRM Online pipeline stages export with the Deal record and are not stored as a separate object. We extract the distinct stage values from the Deal export, map them to Nutshell pipeline stages, and create a Nutshell sales process with matching stage names and order. Stage probabilities are preserved as a percentage field for reporting continuity.
Smart CRM Online
Custom Properties (Contact)
Nutshell
Custom Fields (Person)
lossySmart CRM Online custom contact fields have no published schema, so we identify them during discovery by comparing the CSV column headers against the standard Contact fields (name, email, phone, company). Any non-standard column is flagged as a custom property and presented to the customer for explicit mapping. Nutshell custom Person fields are created before import and mapped per the customer's decisions. Field types (text, date, currency, picklist) are inferred from data values in the export.
Smart CRM Online
Custom Properties (Company)
Nutshell
Custom Fields (Account)
lossySmart CRM Online custom company fields follow the same discovery methodology as contact custom fields. We request a full export during discovery, identify non-standard columns, and present them for explicit mapping to Nutshell Account custom fields. Company-level custom fields are created before Account import begins.
Smart CRM Online
Custom Properties (Deal)
Nutshell
Custom Fields (Lead)
lossySmart CRM Online custom deal fields require discovery-phase identification using the same column-comparison method. Any field not present in the standard Deal schema (name, value, stage, owner, close date) is flagged as custom and mapped to a corresponding Nutshell custom Lead field created before migration.
Smart CRM Online
Activity: Call
Nutshell
Task (Activity type: Call)
1:1Smart CRM Online call activity logs map to Nutshell Task records with the activity type set to Call. Call duration, disposition, and timestamp transfer to the corresponding Task fields. The Who (Person) and What (Deal) associations are reconstructed by matching the Smart CRM Online Contact ID and Deal ID from the activity export against the migrated records.
Smart CRM Online
Activity: Email
Nutshell
Note or Task
1:1Smart CRM Online email activity logs map to Nutshell Notes attached to the related Person record. Email subject, body, and timestamp transfer directly. The Note is linked to the Person by resolving the Contact ID from the activity export to the migrated Nutshell Person. If Nutshell's activity timeline model is preferred, emails can alternatively land as Task records with the email body in the description field.
Smart CRM Online
Activity: Meeting
Nutshell
Event
1:1Smart CRM Online meeting activity logs map to Nutshell Event records. Meeting title, start time, end time, location, and attendees transfer directly. Attendee resolution matches the Smart CRM Online Contact IDs to the migrated Nutshell Person records and links them to the Event.
Smart CRM Online
Activity: Task
Nutshell
Task
1:1Smart CRM Online task activity logs map directly to Nutshell Task records. Task subject, status (open/closed), due date, and assignment transfer directly. Owner resolution matches the Smart CRM Online owner email to the Nutshell User if the destination uses Nutshell's native user management, or the task is assigned to the importing admin if no owner match is found.
| Smart CRM Online | Nutshell | Compatibility | |
|---|---|---|---|
| Company | Account1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Deal | Lead1:1 | Fully supported | |
| Deal Stage | Pipeline Stagelossy | Fully supported | |
| Custom Properties (Contact) | Custom Fields (Person)lossy | Fully supported | |
| Custom Properties (Company) | Custom Fields (Account)lossy | Fully supported | |
| Custom Properties (Deal) | Custom Fields (Lead)lossy | Fully supported | |
| Activity: Call | Task (Activity type: Call)1:1 | Fully supported | |
| Activity: Email | Note or Task1:1 | Fully supported | |
| Activity: Meeting | Event1:1 | Fully supported | |
| Activity: Task | Task1: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.
Smart CRM Online gotchas
No documented API endpoint for programmatic migration
Relational flattening in CSV export breaks object associations
Custom field schema not published, requiring discovery-phase manual audit
No published pricing page creates billing-model ambiguity
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 export verification
We request a full data export from Smart CRM Online covering Contacts, Companies, Deals, Pipeline Stages, and Activity history. We compare column headers against the standard object schema to identify custom fields, count distinct stage values to confirm pipeline count, and assess the activity volume per type (calls, emails, meetings, tasks). We also identify any missing or null fields that require transformation decisions. The discovery output is a written schema map and a custom field inventory requiring explicit mapping from the customer.
Association reconstruction from flat CSV
Smart CRM Online exports Deals with a Company ID reference rather than a structured parent-child relationship to Contacts. We run an association-pass over the CSV before any Nutshell import: we extract the Contact-Deal linkage from any contact association field, match Company IDs to Company records, and build an explicit mapping table of Deal-to-Contact associations. This mapping table is used during Deal import to re-establish the Who and What relationships in Nutshell.
Nutshell schema provisioning
Before any data loads, we create custom fields in Nutshell for every identified Smart CRM Online custom field. We create one Nutshell Account custom field per Company custom field, one Person custom field per Contact custom field, and one Lead custom field per Deal custom field. Field types are set based on data inference from the export (text, currency, date). Standard fields (name, email, phone, stage, value, close date) require no provisioning. If multiple pipelines are present and the customer is not on Nutshell Pro or above, we document the consolidation mapping here.
Staged import in dependency order
We import in record-dependency order: Accounts first (from Smart CRM Online Companies), then Persons (from Contacts with AccountId resolved via Company ID match), then Leads (from Deals with Person and Account resolved via the association reconstruction table), then Activities (Tasks, Events, Notes linked to the migrated Person and Lead records). Each phase emits a row-count reconciliation report comparing source record count to destination record count before the next phase begins.
Activity history linking and timeline validation
After Persons and Leads are confirmed in Nutshell, we run the activity migration. Call logs become Tasks linked to the Person. Emails become Notes attached to the Person. Meetings become Events with attendee resolution. Each activity record is linked via the Nutshell person_id and the Lead reference resolved during the association reconstruction pass. We spot-check 20-30 random activity records in Nutshell against the source CSV to validate linkage accuracy before declaring this phase complete.
Cutover, final delta pass, and automation handoff
We freeze writes in Smart CRM Online and run a final delta export capturing any records modified during the migration window. This delta is processed through the same transform and import pipeline. We deliver the written automation inventory (any Smart CRM Online workflows or sequence cadences if present) to the customer's admin for rebuild in Nutshell. We do not rebuild automations as part of the migration scope. A one-week hypercare window is available for reconciliation issues raised by the sales team.
Platform deep dives
Smart CRM Online
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 Smart CRM Online 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
Smart CRM Online: Not publicly documented.
Data volume sensitivity
Smart CRM Online 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 Smart CRM Online to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Smart CRM Online 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 Smart CRM Online
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.