CRM migration

Migrate from Simply CRM to Nutshell

Field-level mapping, validation, and rollback between Simply CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Simply CRM logo

Simply CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Simply CRM and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Simply CRM logo

Simply CRM

What's pushing teams away

  • At least one user reported significant discrepancies between on-screen record data and exported CSV data, creating billing disputes with vendors — a data integrity concern during routine export operations.
  • Users coming from more feature-rich CRMs have reported that the platform lacks the depth of customization options available in competitors, causing them to outgrow the tool.
  • Sync issues attributed to server traffic and response delays have been noted as a source of friction, particularly during high-activity periods.
  • Some users have flagged that document and presentation tracking is either unavailable or insufficient for their workflow needs, requiring workarounds.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Simply CRM objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Simply 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

maps to

Nutshell

Company

1:1
Fully supported

Simply 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

maps to

Nutshell

Deal

1:1
Fully supported

Simply 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

maps to

Nutshell

Pipeline

1:1
Fully supported

Simply 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)

maps to

Nutshell

Activity

1:1
Fully supported

Simply 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)

maps to

Nutshell

Custom Field

1:1
Fully supported

Simply 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

maps to

Nutshell

User

1:1
Fully supported

Simply 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

maps to

Nutshell

File

1:1
Fully supported

Simply 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

Simply 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

Simply 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.

Gotchas + challenges

What specifically takes care here

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 logo

Simply CRM gotchas

Medium

SugarCRM Professional edition gates certain modules

High

Export discrepancies between screen records and CSV output

Medium

Custom field schema varies per installation

Medium

Workflow automations do not survive migration

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Nutshell custom field limits vary by plan tier

    Nutshell restricts the number of custom fields you can create based on your plan: Foundation has fewer custom fields than Pro or Enterprise. Simply CRM custom fields on People, Companies, and Deals must be pre-audited against the target Nutshell plan. If your Simply CRM setup uses more custom fields than the target plan allows, we flag the overflow fields before migration and your team decides whether to upgrade the Nutshell plan or archive the least-critical custom fields. This is a planning-stage decision — not a post-migration surprise.

  • Simply CRM contacts without companies create standalone Nutshell People

    Simply CRM allows contacts to exist without an associated company record — some teams use this for individual leads or personal contacts. Nutshell's data model expects People to be associated with a Company for full organizational context. We migrate these standalone contacts as Nutshell People with no Company link. Your team can manually assign them to a Company post-migration if needed. We surface all unlinked Person records in the migration report so nothing is silently orphaned.

  • Pipeline stage probability mapping requires manual review

    Simply CRM stores stage probability as a numeric attribute on deal stages. Nutshell stores probability per stage within each pipeline. Stage names and probability values rarely align between the two systems. We create a value-mapping table during scoping — each Simply CRM stage probability maps to the closest Nutshell stage probability. The table is delivered for your review before migration runs, and your team approves the mapping. We do not auto-map probabilities that are materially different because incorrect forecast data can mislead sales leadership post-migration.

  • Workflow and automation logic cannot migrate to Nutshell

    Simply CRM workflow rules, assignment automations, and notification triggers are configuration objects that do not have a Nutshell equivalent. Nutshell's automation model uses different triggers (stage entry, email sequence enrollment) that require manual reconstruction. We export your Simply CRM workflow definitions as a structured reference document listing each rule's trigger, conditions, and actions. Your Nutshell admin uses this to rebuild equivalent automation. We do not skip this step — the rebuild reference is part of the migration deliverable, not an upsell.

  • Industry pick-list values differ between Simply CRM and Nutshell

    Simply CRM and Nutshell use different industry pick-list taxonomies. A Simply CRM industry value like 'Transportation / Logistics / Warehousing' may not exist in Nutshell's industry list. We map each Simply CRM industry value to the closest Nutshell equivalent and flag unmapped values for manual selection. The mapping table is delivered with the migration plan so your team can review industry assignments before data lands.

Migration approach

Six steps for a successful Simply CRM to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Simply CRM logo

Simply CRM

Source

Strengths

  • Built on SugarCRM Professional with decades of stability behind the data model
  • Per-user monthly pricing from $12 with a 14-day free trial and no credit card required
  • Responsive customer support cited frequently across user reviews
  • Intuitive interface designed to reduce CRM complexity and improve adoption rates
  • Contact management, sales pipeline, and reporting available without additional modules

Weaknesses

  • Limited documented API surface beyond basic REST endpoints — bulk export requires careful planning
  • Data export discrepancies reported by at least one user, raising data integrity questions
  • Fewer native integrations compared to HubSpot, Salesforce, or Zoho
  • Limited advanced customization — teams with complex data models may outgrow the platform
  • Sync reliability concerns under heavy server load have been documented in reviews
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Simply CRM and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Simply CRM: Not publicly documented.

  • Data volume sensitivity

    B

    Simply CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Simply CRM to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Simply CRM to Nutshell data migrations

Answers to the questions buyers ask most during Simply CRM to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Simply CRM to Nutshell migrations complete in 24–72 hours of clock time for under 50,000 records. Larger setups with 500,000+ records, multiple pipelines, or a high count of custom fields extend to 5–7 days. The longest planning step is auditing Simply CRM's custom fields against Nutshell's plan-tier limits and building the stage-to-pipeline mapping table. Migration execution is the faster phase once mapping is approved.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Simply CRM.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day