CRM migration
Field-level mapping, validation, and rollback between The Clinic Place and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
The Clinic Place
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between The Clinic Place and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
The Clinic Place stores patient records, appointment schedules, clinical notes, invoices, and custom medical fields across a practice-management schema. Nutshell is a CRM built around People, Companies, Leads, and Deals — it has no native clinical or scheduling model, so the migration maps healthcare records into a sales-adjacent structure. We extract all patient demographics, insurance details, medical-record numbers, appointment dates and statuses, invoice amounts and line items, clinical note bodies, and custom fields via the source API. Each maps to the corresponding Nutshell entity (Person, Company, Deal, Note, or custom field). Owner resolution works by email match against Nutshell users. The one structural gap is appointment scheduling — Nutshell has no calendar entity, so appointment records become Deals with custom datetime fields rather than a native scheduling object. We run a sample migration with a field-level diff before the full cutover, then capture any in-flight changes during the 24–48 hour delta window.
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 The Clinic Place 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.
The Clinic Place
Patient Record
Nutshell
Person
1:1Patient demographics (name, date of birth, contact details, insurance) map directly to Nutshell Person fields. Medical record number and patient status migrate as custom text fields on the Person record for reference. The mapping also includes mapping the patient's primary phone to the Nutshell phone field and any secondary email to a custom field, ensuring all contact points are preserved.
The Clinic Place
Clinic / Facility
Nutshell
Company
1:1Clinic name, address, phone, website, and specialty map to Nutshell Company fields. Accepted insurance plans and facility type migrate as custom text fields. Each patient record links to its primary clinic Company via the Person.关联. If the clinic operates multiple specialties, each specialty can be stored as a separate custom picklist field on the Company record to preserve detailed service offerings.
The Clinic Place
Appointment
Nutshell
Deal
1:1Appointments become Nutshell Deals. Appointment date maps to Deal closeDate, appointment type becomes Deal name, and appointment status (Scheduled, Completed, Cancelled) maps to Deal stage via value mapping. Provider and location become custom fields. The original appointment ID is stored in a custom text field on the Deal for traceability, and any recurrence patterns are documented as a separate custom field to support future scheduling rebuilds.
The Clinic Place
Appointment Status
Nutshell
Deal Stage
1:1The Clinic Place appointment statuses map to Nutshell Deal stages: Scheduled → 'New' or a custom 'Appointment Scheduled' stage; In Progress → a stage of your choosing; Completed → 'Won'; Cancelled → 'Lost'. The stage value map is configured before migration.
The Clinic Place
Invoice / Billing Record
Nutshell
Custom Fields on Person/Deal
1:1Invoice amounts, payer, and status become custom number and text fields on the Person or associated Deal. Nutshell has no native invoice object, so billing data is preserved as structured custom fields rather than a standalone entity. Each invoice line item can be represented as a separate custom text field or as a delimited string stored in a long-text field, depending on your reporting needs.
The Clinic Place
Clinical Note
Nutshell
Note
1:1Clinical encounter notes (note body, date, author) become Nutshell Notes attached to the corresponding Person record. The author resolves to a Nutshell user by email match. Long-form clinical notes may be truncated to fit Nutshell's Note body limits — a custom field on the Person stores the full text if needed.
The Clinic Place
Custom Medical Fields
Nutshell
Custom Fields
1:1The Clinic Place custom fields (e.g., insurance carrier, referral source, treatment plan, allergies, consent flags) map 1:1 to Nutshell custom text or pick-list fields on the corresponding entity type. Nutshell supports custom fields on Person, Company, Lead, and Deal. During the audit, we verify the field type compatibility and create any missing custom fields in Nutshell before the migration run to avoid data loss.
The Clinic Place
Patient–Clinic Association
Nutshell
Person–Company Link
many:1The Clinic Place supports a primary patient-clinic association. We map this as the primary Company link on the Person record. Secondary clinic associations surface as Account Relations in Nutshell, or collapse to the primary if the relationship is 1:N rather than N:N.
The Clinic Place
User / Staff
Nutshell
User
1:1The Clinic Place staff and provider records resolve to Nutshell users by email address. Unmatched staff are flagged before migration — your team either creates their Nutshell account first or assigns records to a fallback owner. We also capture the staff role (e.g., physician, nurse, administrative) as a custom text field on the Nutshell user record to preserve organizational context after the migration.
The Clinic Place
Attachment / File
Nutshell
Files
1:1Patient attachments (lab results, consent forms, imaging references) re-upload to Nutshell Files linked to the corresponding Person record. File size limits apply per Nutshell's storage policy. We preserve original filenames and download URLs for re-hosting. If any file exceeds Nutshell's size cap, we store a link to the original file in a custom URL field and retain the file in a separate cloud storage bucket for retrieval.
The Clinic Place
Lead / Inquiry
Nutshell
Lead
1:1New patient inquiries and lead-type records from The Clinic Place migrate as Nutshell Leads with their original source, status, and owner preserved. Inquiry type and referring doctor map to custom text fields on the Lead. We also map the original lead creation date to a custom datetime field on the Lead to maintain historical context for sales reporting and follow-up timing.
The Clinic Place
System ID / Audit Trail
Nutshell
Custom Text Field
1:1The Clinic Place record IDs are stored in a custom text field (Source_Record_ID__c equivalent) on each Nutshell record for traceability and delta-run de-duplication. Original create dates migrate as custom datetime fields since Nutshell CreatedDate reflects migration time. We also log the last modified timestamp from The Clinic Place as a custom datetime field to preserve the record's last update history in Nutshell.
| The Clinic Place | Nutshell | Compatibility | |
|---|---|---|---|
| Patient Record | Person1:1 | Fully supported | |
| Clinic / Facility | Company1:1 | Fully supported | |
| Appointment | Deal1:1 | Fully supported | |
| Appointment Status | Deal Stage1:1 | Fully supported | |
| Invoice / Billing Record | Custom Fields on Person/Deal1:1 | Fully supported | |
| Clinical Note | Note1:1 | Fully supported | |
| Custom Medical Fields | Custom Fields1:1 | Fully supported | |
| Patient–Clinic Association | Person–Company Linkmany:1 | Fully supported | |
| User / Staff | User1:1 | Fully supported | |
| Attachment / File | Files1:1 | Fully supported | |
| Lead / Inquiry | Lead1:1 | Fully supported | |
| System ID / Audit Trail | Custom Text Field1: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.
The Clinic Place gotchas
No publicly documented API for self-served exports
Custom clinical note formats resist standard mapping
Chart and document file associations are clinic-configured
Pricing opaque without direct vendor contact
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 The Clinic Place data model and extract sample records
We connect to The Clinic Place via API or data export and pull a representative sample (typically 100–200 records per entity type: patients, appointments, invoices, clinical notes, clinics, and leads). We catalog field names, data types, null rates, and relationship cardinality. This gives us the baseline schema map before we write any transformation logic. During this phase we also identify any non‑standard field formats, verify data hygiene, and document any custom fields that will require mapping to Nutshell custom fields.
Design field mapping and value maps against Nutshell schema
Using the audit results, we build the field-level mapping document: direct field pairs, value maps for appointment status to Deal stage, and custom field definitions for MRN, insurance data, clinical note bodies, and provider names. We also identify the email match list for owner resolution and flag any Nutshell custom fields that need to be created before the migration run.
Run sample migration and generate field-level diff
A representative slice of records — spanning patients across different clinics, appointments in multiple statuses, invoices, and clinical notes — migrates into Nutshell first. We produce a field-level diff comparing source values against destination values for every mapped field. You review the diff, confirm the appointment-to-Deal mapping, validate custom field rendering, and approve adjustments before the full run. This step also checks for any data truncation, verifies owner resolution by email, and ensures that relationship cardinalities such as patient‑clinic links are correctly represented.
Execute full migration with owner resolution and relationship integrity
The full dataset migrates with owners resolved by email match, patient-clinic associations mapped to primary Company links, and appointment records created as Deals with custom datetime and provider fields. We handle API rate-limit pacing on the Nutshell side to avoid throttling. Any records that fail validation are isolated to a retry queue and re-processed before the delta window opens. We also log each load batch, track success and failure rates, and provide a summary report after the migration run completes.
Open delta-pickup window and complete cutover
After the initial migration commits, a delta-pickup window (24–48 hours) captures any appointments booked, patient records updated, or invoices issued in The Clinic Place during the cutover period. We reconcile the delta against the initial load and confirm record counts match. You validate a spot-check of migrated Deals and Person records in Nutshell before officially cutting over from The Clinic Place.
Platform deep dives
The Clinic Place
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 The Clinic Place 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
The Clinic Place: Not publicly documented — no published quotas or throttling policy. Limits are negotiated per-customer..
Data volume sensitivity
The Clinic Place 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 The Clinic Place to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your The Clinic Place 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 The Clinic Place
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.