CRM migration
Field-level mapping, validation, and rollback between Pearl Dental Software and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Pearl Dental Software
Source
Nutshell
Destination
Compatibility
13 of 13
objects map 1:1 between Pearl Dental Software and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Pearl Dental Software is a UK-focused dental practice management system built for NHS/private mixed practices, independent dentists, and small dental groups. Its data model centres on patients, appointments, treatments, clinical notes, NHS contract data, and charting records — all structured around the clinical workflow of a dental surgery rather than a sales pipeline. Nutshell is a US-origin CRM designed for small-to-mid sales teams; its standard objects are People, Companies, Leads, Deals, and Activities, with custom fields available on People, Companies, and Leads. There is no native dental or clinical object model in Nutshell. FlitStack AI extracts patient demographics, contact details, appointment histories, and clinical notes from Pearl via its export tools or direct database access. We map these into Nutshell People records, create Nutshell custom fields for NHS numbers, treatment codes, clinical flags, and medical-history notes, and preserve original timestamps as custom datetime fields. Appointments become Nutshell Activities or Tasks; deal records can represent treatment-plan milestones or recall cycles as a pipeline. NHS contract and UDA/UOA data from Pearl maps to custom fields on the People record. What does not migrate: Pearl's appointment-booking workflows, recall sequences, NHS contract-target calculators, imaging annotation overlays, and any integrations with radiography systems or payment gateways. These must be rebuilt in Nutshell using its sales-automation features or handled outside the CRM. We export Pearl workflow definitions as a rebuild reference for your team. Our migration runs against Nutshell's JSON-RPC API using scoped read access on Pearl — your dental team keeps working through the cutover, with a delta-pickup window capturing any records modified in Pearl between the snapshot and go-live.
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 Pearl Dental Software 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.
Pearl Dental Software
Patient
Nutshell
Person
1:1Pearl patient records map to Nutshell People. We preserve the original Pearl patient ID as Source_System_ID__c custom field on the Person for delta-run de-duplication. Patient first name, last name, email, and phone map directly. NHS number and GDC number become Nutshell custom fields on the Person record.
Pearl Dental Software
Patient Address
Nutshell
Person Address Fields
1:1Pearl stores one primary address per patient. We map address_line_1 to Nutshell address, city to city, postcode to postal code, and country to country. If Pearl holds a correspondence address separately, we append it to the Person notes field as a custom text block.
Pearl Dental Software
Medical History
Nutshell
Person Custom Fields
1:1Pearl medical history fields (allergies, medications, medical conditions) have no Nutshell standard equivalent. We create Medical_History__c as a long-text custom field on the Person record. For structured medical flags, we create individual checkbox custom fields (e.g., Has_Allergies__c) during schema setup before migration runs.
Pearl Dental Software
NHS Number
Nutshell
Person Custom Field
1:1NHS number is a 10-digit identifier with a check digit, unique to each UK patient. We create NHS_Number__c as a text custom field on the Person record. We validate the NHS number format before insertion and flag any malformed values for review before the full migration commits.
Pearl Dental Software
Treatment Plan
Nutshell
Deal
1:1Pearl treatment plans list proposed and completed procedures with dates and fees. We map each treatment plan to a Nutshell Deal representing the plan, with Deal amount equal to the plan's total fee, and Deal name set to the patient name plus plan date. Completed treatments within a plan can split into separate Deals if the practice tracks each procedure individually.
Pearl Dental Software
Appointment
Nutshell
Activity / Task
1:1Pearl appointments store date, time, practitioner, surgery/room, type (exam, hygiene, emergency), and status. Past appointments map to Nutshell Activities with Type='Appointment' and original timestamps preserved. Future appointments due after go-live can generate Nutshell Tasks for the assigned practitioner. Appointment status (completed, no-show, cancelled) maps to a custom pick-list field on the Activity.
Pearl Dental Software
Practitioner / Staff
Nutshell
Person (Team Member)
1:1Pearl practitioners and staff records map to Nutshell People records flagged as team members. We resolve the Nutshell user account by email match. If a practitioner has no Nutshell login, we assign their records to a fallback Nutshell user and note the original practitioner in a custom Practitioner_Name__c field on the Person.
Pearl Dental Software
Clinical Note
Nutshell
Note / Activity Note
1:1Pearl clinical notes attached to appointments map to Nutshell Notes on the corresponding Person record. We preserve the original note date, practitioner name, and note body. Nutshell Notes are appended in chronological order to the Person record and timestamped with the original Pearl note date.
Pearl Dental Software
Recall / Follow-up
Nutshell
Task / Deal Milestone
1:1Pearl recall records track when a patient is due for their next appointment (e.g., 6-month hygiene recall). We map recalls to Nutshell Tasks with a due date matching the recall date and assigned to the patient's owning practitioner. Practices that manage recalls as pipeline stages can alternatively map recalls to Deal milestones within a dedicated recall pipeline.
Pearl Dental Software
NHS Contract Data
Nutshell
Person / Company Custom Fields
1:1Pearl NHS contract data (UOA/UDA targets, contract value, completion percentage) is practice-level or patient-attributed depending on setup. We map contract-level data to a custom object or Company-level custom fields. Patient-attributed NHS treatment data maps to Person-level custom fields. UDA completion rate and NHS band information require value-mapping setup before migration.
Pearl Dental Software
File / Attachment
Nutshell
File
1:1Pearl patient document attachments (consent forms, referral letters, insurance documents) re-upload to Nutshell Files and attach to the corresponding Person record. We map the original file name and creation date. File size limits from Pearl's 2GB online backup storage allocation apply during extraction.
Pearl Dental Software
Pearl Automations (Recalls, SMS Reminders)
Nutshell
Not Migrated
1:1Pearl's automated recall reminders and SMS appointment reminders are Pearl-native workflows with no Nutshell equivalent. We export Pearl's workflow definitions as a documented rebuild reference. Nutshell's sales email sequences can replicate appointment follow-up logic but require manual rebuild in Nutshell's sequence editor.
Pearl Dental Software
Pearl Imaging Annotations
Nutshell
Not Migrated
1:1Pearl's radiography analysis overlays and AI detection annotations are Pearl AI-specific data that lives in the imaging integration layer, not in the patient record. These cannot be migrated to Nutshell, which has no imaging object model. We note the limitation and recommend the practice retains access to Pearl's imaging archive separately.
| Pearl Dental Software | Nutshell | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Patient Address | Person Address Fields1:1 | Fully supported | |
| Medical History | Person Custom Fields1:1 | Fully supported | |
| NHS Number | Person Custom Field1:1 | Fully supported | |
| Treatment Plan | Deal1:1 | Fully supported | |
| Appointment | Activity / Task1:1 | Fully supported | |
| Practitioner / Staff | Person (Team Member)1:1 | Fully supported | |
| Clinical Note | Note / Activity Note1:1 | Fully supported | |
| Recall / Follow-up | Task / Deal Milestone1:1 | Fully supported | |
| NHS Contract Data | Person / Company Custom Fields1:1 | Fully supported | |
| File / Attachment | File1:1 | Fully supported | |
| Pearl Automations (Recalls, SMS Reminders) | Not Migrated1:1 | Fully supported | |
| Pearl Imaging Annotations | 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.
Pearl Dental Software gotchas
No public API means migration is file-based, not API-based
Charges per surgery, not per user — capacity planning matters
X-ray and image files require separate handling from demographic data
Custom fields and legacy data variants need explicit review
Onboarding is required and charged separately
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
Confirm Pearl data export scope and extract patient, appointment, and clinical note data
FlitStack AI works with Pearl's export tooling to extract all available data: patient demographics, NHS numbers, medical history, appointment records, treatment plans, clinical notes, practitioner lists, and recall data. We review the export for completeness and flag any fields that Pearl's team must extract manually. This step produces a data inventory showing record counts per object and any gaps before mapping begins. We do not modify Pearl during this phase — extraction uses read-only access.
Create Nutshell custom fields for NHS numbers, clinical data, and appointment metadata
Before any data is written to Nutshell, we create the custom fields required for dental data that has no native Nutshell equivalent: NHS_Number__c, GDC_Number__c, Medical_History__c, Has_Allergies__c, Appointment_Status__c, Room__c, UDA_Value__c, Original_Create_Date__c, Source_System_ID__c, and Patient_Status__c. We deliver a custom-field creation checklist mapped to each source field so your Nutshell admin can create them in advance, or our team creates them via the Nutshell API on your behalf.
Map and transform data, validate NHS numbers, and run sample migration with field-level diff
We run a sample migration of 200–500 Pearl records into Nutshell covering patients across active, archived, and recall statuses; appointments of different types; and at least one treatment plan. The sample produces a field-level diff showing exactly what each Pearl field becomes in Nutshell, including any NHS number format corrections, appointment type value mappings, and clinical note placement. You review the diff and approve or request adjustments before the full migration is scheduled.
Execute full migration with delta-pickup window and one-click rollback available
The full migration runs against Nutshell's JSON-RPC API. A delta-pickup window of 24–48 hours captures any Pearl records modified or created between the migration snapshot and your go-live date. Your dental team continues working in Pearl throughout the cutover. All operations are logged in a migration audit log. If reconciliation reveals unexpected gaps, one-click rollback restores Nutshell to its pre-migration state. After rollback, the migration team and your practice manager review the gap and re-scope the extraction before a second run.
Deliver rebuild reference for Pearl workflows and provide post-migration support
We export Pearl's recall configurations, appointment-reminder settings, and any workflow definitions as structured documentation for your team to rebuild in Nutshell or a compatible recall tool. This includes step-by-step rebuild guides for NHS recall intervals, patient follow-up sequences, and appointment SMS reminders. Post-migration, we provide 30 days of support for any data discrepancies discovered after go-live, including re-mapping of any records that landed with formatting issues, mismatched NHS numbers, or owner-resolution failures where a Pearl practitioner had no matching Nutshell user at migration time.
Platform deep dives
Pearl Dental Software
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 Pearl Dental Software 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
Pearl Dental Software: Not publicly documented.
Data volume sensitivity
Pearl Dental Software 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 Pearl Dental Software to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Pearl Dental Software 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 Pearl Dental Software
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.