CRM migration
Field-level mapping, validation, and rollback between Sensei Cloud and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Sensei Cloud
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Sensei Cloud and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Patient 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
Nutshell
Person (separate record)
1:1Guarantor 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
Nutshell
Company
1:1Each 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
Nutshell
Company (separate record)
1:1Insurance 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
Nutshell
Activity
1:1Appointment 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
Nutshell
Note / Custom Field
1:1Treatment 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
Nutshell
Note
1:1Billing 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
Nutshell
None
1:1Clinical 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
Nutshell
User (owner resolution)
1:1Sensei 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
Nutshell
Note (text only)
1:1Uploaded 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.
| Sensei Cloud | Nutshell | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Guarantor | Person (separate record)1:1 | Fully supported | |
| Practice / Location | Company1:1 | Fully supported | |
| Insurance Carrier | Company (separate record)1:1 | Fully supported | |
| Appointment | Activity1:1 | Fully supported | |
| Treatment Plan | Note / Custom Field1:1 | Fully supported | |
| Ledger Entry / Payment | Note1:1 | Fully supported | |
| Clinical Note / Chart | None1:1 | Fully supported | |
| Provider / Staff User | User (owner resolution)1:1 | Fully supported | |
| Document / Attachment | Note (text only)1: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.
Sensei Cloud gotchas
Legacy conversion leaves messy patient and chart duplicates
Chrome-only browser support affects migration workstation compatibility
Imaging data requires separate Carestream-format conversion pipeline
Billing ledger errors cannot be corrected post-creation
Provider assignments sometimes stored as text rather than foreign key
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 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.
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.
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.
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.
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
Sensei Cloud
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 Sensei Cloud 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
Sensei Cloud: Not publicly documented.
Data volume sensitivity
Sensei Cloud 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 Sensei Cloud to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Sensei 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.