CRM migration
Field-level mapping, validation, and rollback between AeronaClinic and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
AeronaClinic
Source
Nutshell
Destination
Compatibility
10 of 12
objects map 1:1 between AeronaClinic and Nutshell.
Complexity
BStandard
Timeline
4–8 days
Overview
AeronaClinic organizes data around patients, treatment plans, appointments, and clinical notes — a model optimized for clinical workflows, not sales pipeline management. Nutshell structures everything around Companies, People, Leads, and Deals — a model built for tracking prospects and closing revenue. These data models share almost no native equivalences beyond basic contact fields. FlitStack AI maps AeronaClinic patients to Nutshell People records, clinic organizations to Nutshell Companies, and appointment data to Nutshell Tasks with custom fields carrying clinical context (procedure type, provider name, location). Insurance information, referral sources, and clinical flags migrate as custom fields on the People record. We preserve original create dates and appointment timestamps so your Nutshell records carry the full history from day one. Workflows, treatment-plan automation, and clinical alerts built in AeronaClinic have no Nutshell equivalent — those must be rebuilt using Nutshell's automation rules and integrations after migration. The migration uses Nutshell's open JSON-RPC API for record creation and custom field population.
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 AeronaClinic 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.
AeronaClinic
Patient
Nutshell
Person
1:1AeronaClinic Patient maps directly to Nutshell Person in a one-to-one relationship. Core fields including first name, last name, email, phone, address, and date of birth carry over as-is without transformation. The original patient ID from AeronaClinic is preserved as a custom field (Source_Patient_ID__c) on the Nutshell Person record, enabling traceability and supporting delta-run de-duplication when comparing records between systems.
AeronaClinic
Patient
Nutshell
Lead
1:manyInactive or prospect-level patients — those with no completed appointments — split to Nutshell Lead instead of Person. Active patients with completed appointments land as People. The split is based on the appointment history count in AeronaClinic; zero completed appointments routes to Lead.
AeronaClinic
Clinic / Practice
Nutshell
Company
1:1The primary clinic or practice entity in AeronaClinic maps to a single Nutshell Company record. Nutshell Company holds the clinic name, primary address, phone, and website. For multi-office setups, each location becomes its own Company record with a shared parent reference via a custom field.
AeronaClinic
Multi-Office Location
Nutshell
Company
1:manyAeronaClinic multi-office deployments generate one Nutshell Company record per physical location rather than grouping all offices under a single record. A custom field (Parent_Clinic__c) on each satellite location's Company record links back to the primary clinic's Company record, preserving the practice's organizational hierarchy in Nutshell. This structure allows each location to maintain its own address, phone, and contact information while remaining associated with the broader practice entity.
AeronaClinic
Appointment
Nutshell
Task
1:1Each AeronaClinic appointment becomes a Nutshell Task. The task subject carries the procedure type and patient name. Appointment date/time maps to the Task due date, and the original provider name maps to the Task assignee. Custom fields capture location, procedure code, and appointment status for clinical reference.
AeronaClinic
Treatment Plan
Nutshell
Note (on Person)
1:1AeronaClinic treatment plans do not have a direct Nutshell equivalent. We extract the plan summary, associated teeth, procedure codes, and estimated cost, then write these as a dated Note attached to the Person record. Treatment plan status is preserved in a custom field (Treatment_Plan_Status__c) on the Person.
AeronaClinic
Insurance Record
Nutshell
Custom Fields on Person
1:1Insurance provider name, policy number, group number, and coverage tier stored in AeronaClinic map to Nutshell custom fields on the Person record: Insurance_Provider__c, Policy_Number__c, Group_Number__c, and Coverage_Tier__c. These fields are created in Nutshell before migration begins using Nutshell's custom field API. The migration process validates that all required custom fields exist in the target Nutshell instance before any data is written, ensuring a smooth transfer of insurance information.
AeronaClinic
Medical History / Allergies
Nutshell
Custom Fields on Person
1:1Blood type, known allergies, and medical alerts stored in AeronaClinic migrate as Nutshell custom fields on the Person record: Blood_Type__c, Allergies__c, and Medical_Alert__c. These are free-text fields designed to accommodate the wide range of clinical notations possible in AeronaClinic, allowing front-office staff to see critical patient health information at a glance without opening clinical documentation.
AeronaClinic
Referral Source
Nutshell
Custom Field on Person
1:1AeronaClinic tracks how patients were referred — whether through a referring practice, advertising source, or word-of-mouth. This referral source value migrates to a custom pick-list field called Referral_Source__c on the Person record, preserving the marketing attribution data for referral tracking and analysis in Nutshell. Practices can use this data to evaluate which referral channels generate the most patient volume and optimize their marketing spend accordingly.
AeronaClinic
Billing / Outstanding Balance
Nutshell
Custom Field on Person
1:1Outstanding balance and last payment date from AeronaClinic migrate as custom fields on the Nutshell Person record: Outstanding_Balance__c (currency format) and Last_Payment_Date__c (date format). Nutshell does not have native accounts-receivable tracking capabilities; these fields preserve financial context for front-office follow-up and help staff prioritize collection efforts during patient outreach. Practices can use this information to identify overdue accounts and track payment patterns over time.
AeronaClinic
Provider / Clinician
Nutshell
User
1:1AeronaClinic provider names and roles (dentist, hygienist, specialist) map to Nutshell Users by email match. If a provider email does not match an existing Nutshell user, the provider name is stored in a custom field (Provider_Name__c) on related Tasks for appointment attribution.
AeronaClinic
Clinical Notes
Nutshell
Note (on Person)
1:1Free-text clinical notes and clinical attachments from AeronaClinic migrate as Nutshell Notes attached to the Person record. Original timestamps and clinician attribution are preserved in the Note metadata. Image attachments are re-hosted in Nutshell Files and linked to the Note.
| AeronaClinic | Nutshell | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Patient | Lead1:many | Fully supported | |
| Clinic / Practice | Company1:1 | Fully supported | |
| Multi-Office Location | Company1:many | Fully supported | |
| Appointment | Task1:1 | Fully supported | |
| Treatment Plan | Note (on Person)1:1 | Fully supported | |
| Insurance Record | Custom Fields on Person1:1 | Fully supported | |
| Medical History / Allergies | Custom Fields on Person1:1 | Fully supported | |
| Referral Source | Custom Field on Person1:1 | Fully supported | |
| Billing / Outstanding Balance | Custom Field on Person1:1 | Fully supported | |
| Provider / Clinician | User1:1 | Fully supported | |
| Clinical Notes | Note (on Person)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.
AeronaClinic gotchas
Password-protected API limits export options
Large historical record volumes in dental practices
Payment plan instalment schedules require manual sign-off
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
Discovery and schema pre-creation in Nutshell
Before any data moves, FlitStack reviews your AeronaClinic export to count patients, appointments, clinic locations, and custom fields. We then create the custom fields in Nutshell (Insurance_Provider__c, Outstanding_Balance__c, Blood_Type__c, and others) using Nutshell's custom field API so the destination schema is ready before validation begins. We deliver a pre-migration checklist confirming which clinical fields will land as custom fields versus Notes so your team can validate the approach.
Resolve provider emails against Nutshell users
AeronaClinic providers (dentists, hygienists, specialists) are mapped to Nutshell Users by email match. If a provider email does not correspond to a Nutshell user account, we flag the record and assign the associated Tasks to your designated fallback owner. Provider roles (e.g., 'Lead Dentist', 'Hygienist') are preserved in a Provider_Role__c custom field on each related Task. This step runs before any record creation to ensure appointment attribution is correct from the first migration batch.
Run a sample migration of 100–500 records
FlitStack migrates a representative slice of your AeronaClinic data — typically 100 patients across multiple locations, their appointments, and a sample of clinical notes — into Nutshell. We generate a field-level diff showing every mapped field's source value and destination value so your team can verify custom field labels, appointment-to-task mapping, and provider attribution. No record is committed permanently until you sign off on the sample. This is the step where multi-location linking and insurance field placement are confirmed.
Full migration with delta-pickup window
Once the sample is approved, FlitStack runs the full migration against Nutshell's JSON-RPC API. We sequence the load in dependency order — Companies first, then People, then Tasks — to satisfy Nutshell's entity relationship requirements. A delta-pickup window of 24–48 hours captures any new patients or appointments created in AeronaClinic during the cutover so your Nutshell instance reflects the final state at go-live. All operations are logged in an audit file for reconciliation.
Validation, rollback plan, and rebuild reference export
FlitStack generates a reconciliation report comparing total record counts and sample field values between AeronaClinic and Nutshell. If reconciliation fails, one-click rollback reverts all Nutshell changes. We also export your AeronaClinic workflow definitions, recall sequences, and appointment reminder rules as a rebuild reference document for your team to reconstruct in Nutshell's automation layer. Integration connections (payment processors, imaging tools, referral tracking systems) are documented for rebuilding post-migration.
Platform deep dives
AeronaClinic
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 AeronaClinic 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
AeronaClinic: Not publicly documented.
Data volume sensitivity
AeronaClinic 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 AeronaClinic to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your AeronaClinic 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 AeronaClinic
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.