CRM migration

Migrate from Pearl Dental Software to Nutshell

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 logo

Pearl Dental Software

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

13 of 13

objects map 1:1 between Pearl Dental Software and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Pearl Dental Software logo

Pearl Dental Software

What's pushing teams away

  • Very limited public API documentation — practices with custom integration needs or automated workflows find themselves unable to extend the platform without vendor involvement.
  • Small review sample (2 verified Capterra reviews, limited G2 presence) makes independent due diligence difficult and raises concerns about enterprise-grade support depth.
  • No published pricing for third-party integrations or onboarding fees — the absence of a public price for these components creates ambiguity during procurement.
  • Pearl is designed for independent practices and small groups; multi-practice brands and DSOs are explicitly told to wait for a next-generation product that has no announced release date.
  • Practices requiring advanced analytics or AI-assisted diagnostics built into the PMS layer may need to layer on third-party tools since Pearl's feature set is primarily operational.

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 Pearl Dental Software objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Pearl 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

maps to

Nutshell

Person Address Fields

1:1
Fully supported

Pearl 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

maps to

Nutshell

Person Custom Fields

1:1
Fully supported

Pearl 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

maps to

Nutshell

Person Custom Field

1:1
Fully supported

NHS 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

maps to

Nutshell

Deal

1:1
Fully supported

Pearl 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

maps to

Nutshell

Activity / Task

1:1
Fully supported

Pearl 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

maps to

Nutshell

Person (Team Member)

1:1
Fully supported

Pearl 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

maps to

Nutshell

Note / Activity Note

1:1
Fully supported

Pearl 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

maps to

Nutshell

Task / Deal Milestone

1:1
Fully supported

Pearl 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

maps to

Nutshell

Person / Company Custom Fields

1:1
Fully supported

Pearl 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

maps to

Nutshell

File

1:1
Fully supported

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

maps to

Nutshell

Not Migrated

1:1
Fully supported

Pearl'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

maps to

Nutshell

Not Migrated

1:1
Fully supported

Pearl'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.

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.

Pearl Dental Software logo

Pearl Dental Software gotchas

High

No public API means migration is file-based, not API-based

Medium

Charges per surgery, not per user — capacity planning matters

Medium

X-ray and image files require separate handling from demographic data

Medium

Custom fields and legacy data variants need explicit review

Low

Onboarding is required and charged separately

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

  • Pearl has no documented bulk-export API — data extraction depends on Pearl's own migration tooling

    Pearl Dental Software does not publish a public bulk-export REST or GraphQL API. Data extraction relies on Pearl's own onboarding team's migration tooling or manual exports from within Pearl. This means the source export may not include all fields or historical records unless Pearl's team explicitly supports it during your migration window. We work with Pearl's documented export formats (patient CSV, appointment CSV, treatment-plan exports) and flag any fields that require Pearl team involvement to extract. Practices should confirm with Pearl what data is available for export before scoping the migration. Nutshell's own open API accepts all data we can extract — the bottleneck is always Pearl's side.

  • NHS numbers require validation and must not be treated as a direct text import

    NHS numbers are 10-digit identifiers with a check digit in position 10 that validates the preceding 9 digits. Pearl may store NHS numbers with or without spaces, with leading zeros stripped, or in mixed formats. If an invalid NHS number is imported into Nutshell's NHS_Number__c custom field without validation, it creates a data-integrity problem that surfaces in NHS digital-integration workflows downstream. We validate every NHS number against the Mod 11 algorithm before insertion and surface any failures in a pre-migration validation report so your team can correct source data before the full migration runs.

  • Pearl's clinical note structure has no Nutshell equivalent — long-text fields require schema setup before migration

    Pearl clinical notes are free-text records attached to appointments, often containing tooth-charting notation, periodontal measurements, and treatment descriptions. Nutshell Notes store plain text on a Person record but there is no native clinical note type, no tooth-charting field, and no periodontal data model. We migrate clinical note text as Nutshell Notes attached to the Person. For practices that need structured periodontal data (BPE scores, pocket depths, mobility grades), these must be stored as custom fields on the Person, which Nutshell allows — but those custom fields must be created before migration begins. We deliver a custom-field creation plan as part of the pre-migration schema setup phase.

  • Pearl's recall sequences cannot migrate — dental recall logic must be rebuilt in Nutshell

    Pearl's recall system triggers SMS or email reminders when a patient is due for their next appointment based on the recall interval set per patient (e.g., 6 months for hygiene). This is a Pearl-native workflow triggered by date arithmetic within Pearl's practice management model. Nutshell has no recall trigger — its automation model is based on deal-stage changes and lead entry, not patient appointment cycles. We export Pearl's recall definitions (patient ID, recall interval, last recall date, next due date) as a structured CSV that your team can use to build Nutshell Tasks for each patient at the appropriate interval, or to configure a third-party recall management tool that integrates with Nutshell.

  • Pearl imaging AI annotations live outside the patient record and cannot migrate to Nutshell

    Pearl's radiography analysis features — including Second Opinion AI detections, Imagecheck quality-assurance overlays, and any annotations drawn on radiographs — live in Pearl's imaging integration layer, not in the patient record itself. Nutshell has no imaging object, no annotation model, and no AI detection storage. X-ray image files themselves can be re-uploaded as Nutshell Files attached to the Person record, but the AI analysis overlays and detection data are not portable. Practices relying on Pearl AI for clinical decision support should retain their Pearl subscription for imaging or evaluate a replacement AI platform post-migration.

Migration approach

Six steps for a successful Pearl Dental Software to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Pearl Dental Software logo

Pearl Dental Software

Source

Strengths

  • Charges by surgery count, not user count — unlimited staff can access the system under a single surgery subscription.
  • Includes Patient Portal, PearlPad, touchscreen check-in, and kiosk modes on every paid tier with no feature gating.
  • Subscription model with no annual contract — practices can exit without penalty if the product no longer meets their needs.
  • UK-based support team with direct access, no automated switchboard, and consistent 5-star ratings for customer service responsiveness.
  • 2GB of online backup storage per surgery included for patient documents and X-ray images.

Weaknesses

  • No documented public API — third-party integrations and custom automation require vendor involvement rather than self-service.
  • Small company (8 employees) with limited published security certifications or enterprise SLA documentation.
  • No published pricing for onboarding, third-party integrations, or additional data storage beyond the included 2GB per surgery.
  • Target market is independent practices only; multi-location or DSO practices are not yet supported and must wait for an unannounced product iteration.
  • Limited independent review volume makes it difficult to benchmark long-term reliability against larger competitors.
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 Pearl Dental Software 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

    Pearl Dental Software: Not publicly documented.

  • Data volume sensitivity

    B

    Pearl Dental Software doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Pearl Dental Software 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 Pearl Dental Software to Nutshell data migrations

Answers to the questions buyers ask most during Pearl Dental Software to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Pearl to Nutshell migrations complete within 48–72 hours of clock time for practices with under 25,000 patient records. Practices with 25,000–100,000 records, extensive clinical note histories, or multiple surgery locations extend to 5–10 days. The longest phase is usually extracting the full data set from Pearl's own migration tooling — that timeline depends on Pearl's team availability and data export scope. Nutshell's API writes are fast; the bottleneck is always source-side extraction and custom field creation before data moves.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Pearl Dental Software.
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