CRM migration
Field-level mapping, validation, and rollback between Simply CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Simply CRM
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Simply CRM and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Simply CRM organizes data around contacts, companies, deals, and activities — with a data model derived from SugarCRM Professional. It stores standard fields for People (name, email, phone, title, address), Companies (name, domain, industry, employee count, revenue), and Deals (name, amount, stage, close date, owner). Custom fields and custom objects are supported but follow a flat extension model. Nutshell separates People and Companies into distinct modules: People hold contact information with a role on each Company, and Companies store organizational data. Deals in Nutshell track pipeline stages, values, and probabilities, with activities logged against any related record. Nutshell uses custom fields that can be created per-plan on People, Companies, and Leads, and its API is JSON-RPC over HTTPS with basic auth. FlitStack AI extracts Simply CRM data via its REST API, maps People to Nutshell People, Companies to Nutshell Companies, and Deals to Nutshell Deals. Activities (calls, emails, meetings, notes) migrate as Nutshell Activities with original timestamps and owner links preserved. Custom fields from Simply CRM create corresponding custom fields in Nutshell before data lands. Workflows, automations, and notification rules do not migrate — we export those definitions as a rebuild reference for your Nutshell admin. The migration runs as a sequenced bulk load: Companies first, then People with company links, then Deals, then Activities. A delta-pickup window captures in-flight changes during cutover, and audit logging tracks every operation.
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 Simply CRM 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.
Simply CRM
Contact / Person
Nutshell
Person
1:1Simply CRM contacts map to Nutshell People. The contact's name, email, phone, title, and address fields map directly to Nutshell's Person fields. If the Simply CRM contact has no associated company, a standalone Person record is created in Nutshell with no Company link.
Simply CRM
Company
Nutshell
Company
1:1Simply CRM companies map 1:1 to Nutshell Companies. The company name, website, industry, employee count, and annual revenue map to Nutshell's corresponding Company fields. Industry uses value-mapping because Simply CRM and Nutshell use different industry pick-list taxonomies.
Simply CRM
Deal
Nutshell
Deal
1:1Simply CRM deals map to Nutshell Deals with deal name, amount, stage, and close date preserved. Stage mapping uses value-mapping because Simply CRM stage names and Nutshell pipeline stage names rarely match exactly. Each Simply CRM deal's associated pipeline maps to a Nutshell pipeline.
Simply CRM
Pipeline
Nutshell
Pipeline
1:1Simply CRM's pipeline concept translates to Nutshell Pipelines. Each Simply CRM pipeline becomes a Nutshell Pipeline with its own stage set. Stage names, probabilities, and values are mapped value-by-value during migration planning. Simply CRM's single-pipeline-per-instance model maps to Nutshell's multi-pipeline model directly.
Simply CRM
Activity (Call / Email / Meeting / Note)
Nutshell
Activity
1:1Simply CRM activities — calls, emails, meetings, and tasks — map to Nutshell Activities. Original timestamps, owners, and related-to record links are preserved. In Simply CRM, notes are a separate object; in Nutshell, notes are part of the activity feed on each record. We attach Simply CRM notes to the relevant Person, Company, or Deal record by matching the related-to reference.
Simply CRM
Custom Field (on any module)
Nutshell
Custom Field
1:1Simply CRM custom fields on Contacts, Companies, and Deals require pre-creation in Nutshell before data loads. Nutshell's plan tiers limit custom field counts — we audit the target plan during scoping and surface any custom fields that exceed the plan cap for manual resolution before migration runs.
Simply CRM
User / Owner
Nutshell
User
1:1Simply CRM owner IDs are resolved by email match against Nutshell Users. Unmatched owners are flagged before migration — the team either creates Nutshell user accounts or assigns those records to a fallback owner. No record lands in Nutshell without a valid owner reference.
Simply CRM
Attachment / File
Nutshell
File
1:1Simply CRM file attachments are downloaded and re-uploaded to Nutshell Files. File size limits apply (Nutshell's per-file limit is plan-dependent). We re-attach files to the corresponding Person, Company, or Deal record using the original attachment links.
Simply CRM
Workflow / Automation
Nutshell
Not Migrated
1:1Simply CRM workflows and automation rules do not migrate to Nutshell. Nutshell's automation model (triggers on stage entry, email sequences) uses a different configuration paradigm. We export your Simply CRM workflow definitions as a structured reference document your Nutshell admin can use to rebuild equivalent automation in Nutshell.
Simply CRM
Report / Dashboard
Nutshell
Not Migrated
1:1Simply CRM reports and dashboards do not migrate. The underlying data transfers — deal amounts, stage history, activity timestamps — but reporting configurations must be rebuilt in Nutshell's reporting module. We provide a data dictionary so Nutshell reports reference the migrated field names from day one.
| Simply CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Activity (Call / Email / Meeting / Note) | Activity1:1 | Fully supported | |
| Custom Field (on any module) | Custom Field1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Attachment / File | File1:1 | Fully supported | |
| Workflow / Automation | Not Migrated1:1 | Fully supported | |
| Report / Dashboard | Not Migrated1: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.
Simply CRM gotchas
SugarCRM Professional edition gates certain modules
Export discrepancies between screen records and CSV output
Custom field schema varies per installation
Workflow automations do not survive migration
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 source data and scope field mapping
FlitStack AI connects to Simply CRM via its REST API to audit record counts, custom field inventory, and pipeline configurations. We export the full schema — standard fields, custom fields, and activity types — and compare it against Nutshell's data model. This produces a mapping spreadsheet listing every field, its Nutshell equivalent, and any custom fields that need pre-creation. We also audit Simply CRM's industry pick-list values and stage names against Nutshell's corresponding pick-lists. The audit report is delivered for your review before any data moves.
Resolve owner accounts and pre-create Nutshell custom fields
Simply CRM owner IDs are matched by email against existing Nutshell user accounts. Any owner without a corresponding Nutshell user is flagged — your team either creates the Nutshell user first or assigns those records to a fallback owner. Meanwhile, Nutshell custom fields are pre-created based on the audit findings, respecting plan-tier limits. Fields that exceed the plan cap are surfaced for upgrade or archival decisions before the migration window opens.
Migrate Companies, then People, then Deals, then Activities
FlitStack AI sequences the migration to respect Nutshell's foreign-key relationships: Companies are loaded first, then People with their Company links resolved, then Deals with their People and Company associations, then Activities with their related-to references. This order ensures no orphaned records. Activities are loaded last because they depend on People, Companies, and Deals all existing first. We use Nutshell's bulk API endpoints to maximize throughput while staying within rate limits.
Run a sample migration with field-level diff
A representative slice — typically 100–500 records spanning People, Companies, Deals, and Activities — migrates first. We generate a field-level diff between the Simply CRM source and the Nutshell destination, verifying that field values, pick-list mappings, and relationship links are intact. You review the diff and approve field mapping before the full run commits. Any mapping corrections are applied before the bulk migration starts.
Cut over with delta-pickup and audit logging
The full migration runs against Nutshell. A delta-pickup window — typically 24–48 hours — captures any records created or modified in Simply CRM during the cutover. Audit logging tracks every record created, updated, or skipped. If reconciliation fails — record counts don't match, or key field values are missing — one-click rollback reverts the Nutshell instance to its pre-migration state. After rollback is confirmed, your team can investigate the discrepancy and re-run.
Platform deep dives
Simply CRM
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 Simply CRM 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
Simply CRM: Not publicly documented.
Data volume sensitivity
Simply CRM 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 Simply CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Simply CRM 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 Simply CRM
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.