CRM migration

Migrate from Sensei Cloud to Nutshell

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

Sensei Cloud logo

Sensei Cloud

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Sensei Cloud and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Sensei Cloud is dental practice management software built for oral healthcare enterprises, DSOs, and multi-location groups. Its data model centers on patients, appointments, clinical charts, treatment plans, billing ledgers, and insurance claims. Nutshell is a sales CRM for small-to-medium businesses that organizes data around People, Companies, Leads, and Deals. The two platforms share almost no native object equivalents — patient records do not map to CRM contacts, treatment plans have no Deal counterpart, and billing ledgers cannot become Opportunities. We map what can migrate: patient names, phone numbers, email addresses, physical addresses, and basic demographic fields become Nutshell People records. Practice contact information becomes a Nutshell Company record. Appointment history migrates as Activities with original timestamps. All other Sensei Cloud data — clinical notes, radiographs, treatment plans, ledger entries, insurance records, and imaging — has no Nutshell destination and must be retained in Sensei Cloud or handled manually. We use Nutshell's JSON-RPC API with scoped read access on Sensei Cloud, run a test migration against a sample of 50-100 records, and capture any changes made during the delta window before cutover.

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

Sensei Cloud logo

Sensei Cloud

What's pushing teams away

  • Conversion from SoftDent and other legacy systems is messy, generating duplicate charts, inconsistent ledger entries, and billing records that do not reconcile cleanly in the new environment.
  • Cloud performance issues including slowness, login problems, and unreliable data syncing frustrate high-volume practices that depend on constant uptime throughout the clinical day.
  • Surgical workflows for oral surgeons feel adapted rather than native, with gaps in medical billing, cross-coding, and referral management that require persistent workarounds.
  • Radiograph visualization is not natively built into the core software, forcing practices to purchase and integrate the separate Sensei Imaging addon to view digital images within the platform.
  • Billing ledger bugs cause completed and paid accounts to show outstanding balances, making collections tracking unreliable and creating reconciliation headaches for front-office staff.

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 Sensei Cloud objects map to Nutshell

Each row shows how a Sensei 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.

Sensei Cloud

Patient

maps to

Nutshell

Person

1:1
Fully supported

Patient first name, last name, date of birth, and contact details map directly to Nutshell Person fields. Patient ID from Sensei Cloud is stored as Source_System_ID__c for traceability. Clinical notes, medical history, and insurance data have no Nutshell destination and are not migrated.

Sensei Cloud

Guarantor

maps to

Nutshell

Person (separate record)

1:1
Fully supported

Guarantor records (the billing party, which may differ from the patient) migrate as separate Nutshell Person records. The relationship between patient and guarantor is preserved as a custom text field linking the two records, since Nutshell has no native guarantor-equivalent object.

Sensei Cloud

Practice / Location

maps to

Nutshell

Company

1:1
Fully supported

Each Sensei Cloud practice location becomes a separate Nutshell Company record. The location's address, phone number, and primary contact name map directly to Company fields. For multi-location DSOs, this generates multiple Company records, with each one linked to the Person records of patients who were seen at that specific location, enabling territory-based reporting.

Sensei Cloud

Insurance Carrier

maps to

Nutshell

Company (separate record)

1:1
Fully supported

Insurance carrier names and plan types have no native Nutshell Company classification. We create separate Company records tagged with a custom Insurance_Carrier__c flag. If insurance data is required for reporting, a custom pick-list field is added to the Person record.

Sensei Cloud

Appointment

maps to

Nutshell

Activity

1:1
Fully supported

Appointment date, time, provider name, and procedure codes (CDT) are consolidated into a Nutshell Activity record attached to the Person. The original appointment status (completed, no-show, cancelled) maps to Activity type. Operatory and provider notes are stored as activity description text.

Sensei Cloud

Treatment Plan

maps to

Nutshell

Note / Custom Field

1:1
Fully supported

Treatment plans with procedure codes, tooth numbers, and clinical notes cannot map to any Nutshell object. We export treatment plan data as a structured text blob and attach it as a Note to the Person record. The clinical detail cannot be rendered in Nutshell's data model and requires a reference back to Sensei Cloud or a PDF export.

Sensei Cloud

Ledger Entry / Payment

maps to

Nutshell

Note

1:1
Fully supported

Billing ledger entries—including procedure charges, payments, write-offs, and insurance adjustments—have no equivalent object in Nutshell's data model. We generate a summary note attached to each patient record that lists total charges, total payments received, and outstanding balance as of the migration date. The complete ledger history remains accessible in Sensei Cloud for reference.

Sensei Cloud

Clinical Note / Chart

maps to

Nutshell

None

1:1
Fully supported

Clinical notes, periodontal charting, radiograph references, intraoral images, and treatment plans are dental-clinical data types that Nutshell's CRM cannot represent in any form. These records are not migrated during the process. Patients with active clinical relationships or ongoing treatment should remain in Sensei Cloud or be transferred to an alternative clinical dental platform to preserve care continuity.

Sensei Cloud

Provider / Staff User

maps to

Nutshell

User (owner resolution)

1:1
Fully supported

Sensei Cloud providers and staff users are matched to Nutshell users by email address. Unmatched providers are assigned to a fallback Nutshell user (office admin) and flagged for review. Provider role (dentist, hygienist, admin) is stored as a custom text field on the User record.

Sensei Cloud

Document / Attachment

maps to

Nutshell

Note (text only)

1:1
Fully supported

Uploaded documents, consent forms, and referral letters attached to patient records are downloaded and re-hosted if they are small image or PDF files. Large imaging files (DICOM radiographs) cannot be stored in Nutshell and are flagged for manual retrieval from Sensei Cloud.

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.

Sensei Cloud logo

Sensei Cloud gotchas

High

Legacy conversion leaves messy patient and chart duplicates

Medium

Chrome-only browser support affects migration workstation compatibility

Medium

Imaging data requires separate Carestream-format conversion pipeline

Low

Billing ledger errors cannot be corrected post-creation

Low

Provider assignments sometimes stored as text rather than foreign key

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

  • Clinical data has no Nutshell destination — full disclosure required

    Sensei Cloud stores clinical data that Nutshell cannot represent: treatment plans with tooth numbers, periodontal charting, radiograph references, clinical notes, and insurance claim status. None of these map to any Nutshell object. We export treatment plans as text notes attached to Person records, but the clinical context cannot be rendered in Nutshell. Patients with active clinical relationships must remain in Sensei Cloud or an alternative clinical system. Migration planning must identify which patients are clinically active versus administratively managed.

  • Billing ledger and payment history cannot migrate to Nutshell

    Sensei Cloud ledger entries — charges, payments, adjustments, write-offs, and insurance payments — have no Nutshell equivalent. Nutshell has a Deal Amount field but no per-contact ledger, no aging report, and no payment history tracking. We generate a one-time summary note per patient listing the outstanding balance at migration time. Ongoing billing must continue in Sensei Cloud or be handled in dedicated accounting software. Patients with outstanding balances should not be marked as 'closed' in the new CRM without resolving the financial record gap.

  • Multi-location DSO setups require Company-split planning before migration

    DSOs running Sensei Cloud with multiple practice locations hold all patient records under one logical database, but each location may need its own Nutshell Company record for territory reporting. We split by location_id: each location becomes a Company record, and each patient is linked to the Company for their primary location. If patients were seen at multiple locations, we assign the most-recently-visited location as primary and flag for review. Nutshell's per-user pricing also means adding locations adds cost per CRM seat — this should be planned before schema creation.

  • Insurance carrier data requires a custom field setup in Nutshell

    Nutshell has no native Insurance Carrier object or patient insurance field. We store insurance carrier names as separate Company records with an Insurance_Carrier__c flag, and plan type as a custom text field on the Patient's Person record. This is a manual setup in Nutshell before migration — the Company records for carriers must be created and the custom Person field must be configured. If the Nutshell plan does not include custom fields (Foundation plan has restrictions), an upgrade to Pro or Business is required before insurance data can be stored.

  • Guarantor relationships collapse to linked Person records with a text field

    Sensei Cloud supports guarantor records where the billing party differs from the patient. Nutshell has no native guarantor relationship object. We migrate guarantors as separate Person records and store the relationship type (parent, spouse, self, employer, etc.) in a custom text field. The link between patient and guarantor is maintained as a text reference, not a relational constraint. This means a change to the guarantor's name in Nutshell does not propagate to the patient's record — your admin team must keep these synchronized manually.

Migration approach

Six steps for a successful Sensei Cloud to Nutshell data migration

  1. Audit Sensei Cloud data for migration eligibility

    We connect via scoped read access to your Sensei Cloud instance and enumerate all record types, field schemas, and relationship metadata. The audit identifies which patients have basic contact fields (name, email, phone, address) that can migrate versus which records are clinically active and should remain in Sensei Cloud. We flag patients without any contact information, duplicate records, and records with null required fields. The audit output is a migration eligibility report that defines the scope before any data movement begins.

  2. Configure Nutshell schema for dental-to-CRM mapping

    Before data moves, we configure Nutshell custom fields: Source_System_ID__c on Person, Original_Create_Date__c and Last_Modified_Date__c datetime fields, Guarantor_Relationship__c text field, and Insurance_Carrier__c flag on Company records. We create Company records for each Sensei Cloud location and for each insurance carrier. Nutshell users are matched by email to Sensei Cloud providers and staff. If the Foundation plan is in use, we recommend upgrading to Pro or Business to unlock custom field access.

  3. Resolve owner and user relationships by email

    Sensei Cloud providers and staff users are matched to Nutshell users by email address. We run a pre-migration user resolution step: matched users are assigned as record owners, and unmatched providers are assigned to a designated fallback Nutshell user (typically the office administrator) and flagged in the migration report. Every Person, Company, and Activity record lands with a Nutshell owner — no orphan records.

  4. Run test migration on a representative sample

    A sample of 50–100 patient records spanning multiple locations, guarantor relationships, and appointment histories migrates to a Nutshell test environment first. We generate a field-level diff comparing source values to destination fields, verifying name parsing, date formatting, phone number normalization, address splitting, and activity attachment. The test run validates that custom fields are writable, Company links resolve correctly, and insurance carrier Company records are found by name.

  5. Execute full migration with delta-pickup window

    The full migration runs against Nutshell's JSON-RPC API. We sequence the load: Company records (locations and carriers) first, then Person records with foreign-key links to Company, then Activities attached to Person records. A delta-pickup window of 24–48 hours captures any Sensei Cloud records modified during cutover. After delta capture, we run a final reconciliation count against Sensei Cloud's record totals and generate an audit log. One-click rollback is available if the count check fails.

Platform deep dives

Context on both ends of the pair

Sensei Cloud logo

Sensei Cloud

Source

Strengths

  • Cloud-native access means teams schedule, chart, and collect payments from any location or device with a browser login.
  • Carestream imaging integration brings digital radiography, CBCT, and intraoral scans directly into the patient record within the same platform.
  • Centralized multi-location management gives group practices and DSOs a single dashboard for operations and performance across every office.
  • Practice management data including scheduling, treatment planning, billing, and EHR lives in one platform rather than across disconnected legacy systems.

Weaknesses

  • Conversion from legacy Carestream products like SoftDent and Windent consistently generates messy data with duplicate records and reconciliation gaps.
  • Radiograph visualization requires the separate Sensei Imaging addon; the core platform does not display digital images natively.
  • Duplicate charts cannot be merged or deleted within the software, forcing staff to work around or ignore redundant patient records.
  • Ledger entries are difficult to delete or alter after creation, making it hard to correct billing errors post-commitment.
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. 1 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 Sensei Cloud and Nutshell.

  • Object compatibility

    B

    1 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

    Sensei Cloud: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Sensei Cloud 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 Sensei Cloud to Nutshell data migrations

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

Can't find your answer?

Walk through your Sensei Cloud to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Sensei Cloud-to-Nutshell migrations complete in 48–72 hours for under 10,000 patient records. Large DSO datasets with multiple locations and over 50,000 records extend to 5–10 days. The longest step is the pre-migration audit to identify which patients have migratable contact data versus clinical records that must remain in Sensei Cloud. Custom field configuration in Nutshell and user resolution by email also add planning time before the migration run.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Sensei Cloud.
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