CRM migration

Migrate from AeronaClinic to Nutshell

Field-level mapping, validation, and rollback between AeronaClinic and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

AeronaClinic logo

AeronaClinic

Source

Nutshell

Destination

Nutshell logo

Compatibility

83%

10 of 12

objects map 1:1 between AeronaClinic and Nutshell.

Complexity

BStandard

Timeline

4–8 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

AeronaClinic logo

AeronaClinic

What's pushing teams away

  • Some practices find the feature set narrower than larger platforms like Dentrix Ascend or CareStack, reporting that advanced clinical workflows or specialist modules require third-party workarounds.
  • The lack of a mobile application means practitioners who want to chart or check schedules from a phone or tablet report friction compared to mobile-first alternatives.
  • Clinics with multiple locations or complex multi-practitioner setups report that reporting and analytics tools, while functional, are less flexible than what spreadsheet-based analysis can deliver.
  • Users occasionally cite the learning curve for staff unfamiliar with cloud-based interfaces, particularly for features like KPI dashboards and automated reporting that replace legacy paper or spreadsheet workflows.

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 AeronaClinic objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

AeronaClinic 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

maps to

Nutshell

Lead

1:many
Fully supported

Inactive 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

maps to

Nutshell

Company

1:1
Fully supported

The 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

maps to

Nutshell

Company

1:many
Fully supported

AeronaClinic 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

maps to

Nutshell

Task

1:1
Fully supported

Each 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

maps to

Nutshell

Note (on Person)

1:1
Fully supported

AeronaClinic 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

maps to

Nutshell

Custom Fields on Person

1:1
Fully supported

Insurance 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

maps to

Nutshell

Custom Fields on Person

1:1
Fully supported

Blood 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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

AeronaClinic 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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Outstanding 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

maps to

Nutshell

User

1:1
Fully supported

AeronaClinic 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

maps to

Nutshell

Note (on Person)

1:1
Fully supported

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

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.

AeronaClinic logo

AeronaClinic gotchas

High

Password-protected API limits export options

Medium

Large historical record volumes in dental practices

Medium

Payment plan instalment schedules require manual sign-off

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

  • Clinical data has no native Nutshell home — custom fields carry the clinical context

    AeronaClinic stores blood type, allergies, medical alerts, treatment plans, and clinical notes. Nutshell has no native clinical object or medical data type — these all become custom fields on the Person record or Notes attached to the Person. The clinical depth that AeronaClinic tracks (per-tooth charting, periodontal classification, treatment plan phases) cannot be replicated field-for-field in Nutshell. We migrate everything we can as structured custom fields and notes, but practices should audit whether critical clinical data is recoverable post-migration in a form that meets their clinical documentation requirements. This is not a limitation of FlitStack — it is a structural constraint of moving from a clinical PM to a sales CRM.

  • Appointment-to-Task mapping flattens Nutshell's activity model

    Nutshell Tasks are a single activity type for notes, calls, and follow-ups. AeronaClinic's structured appointment model (provider, procedure code, chair location, appointment type, recall interval) cannot map field-for-field into a Nutshell Task. We extract the date, provider, procedure type, and status, but recall scheduling, chair assignments, and multi-appointment series in AeronaClinic do not translate to Nutshell's task structure. Recall workflows built in AeronaClinic must be rebuilt using Nutshell's automation rules or a third-party scheduling integration post-migration.

  • Multi-location clinics require manual parent-child company linking in Nutshell

    AeronaClinic's multi-office configuration stores per-location address, hours, and provider rosters under a single practice entity. Nutshell Companies have one address per record with no native parent-child hierarchy for addresses. We create one Nutshell Company per AeronaClinic location and link them using a custom Parent_Clinic__c text field, but the linking and naming conventions must be confirmed by your team before migration runs. Incorrect linking produces duplicate companies for the same practice.

  • Insurance and billing data migrates as reference fields, not integrated billing

    AeronaClinic insurance records, policy numbers, group numbers, and outstanding balances migrate as custom fields on the Nutshell Person record. Nutshell has no native billing, claims, or accounts-receivable module — these fields exist for front-office reference only. Your team cannot process insurance claims, post payments, or generate patient statements from within Nutshell. If your practice relies on AeronaClinic's billing workflow for day-to-day operations, you need a dedicated billing tool alongside Nutshell. We recommend evaluating integrated billing solutions that can sit alongside Nutshell's CRM functionality to maintain your financial workflows.

  • Nutshell's API rate limits affect migration throughput for large datasets

    Nutshell's API enforces per-user rate limits that govern how many records can be created per minute during migration. Large AeronaClinic datasets with 30,000 or more patient records and multi-year appointment histories can extend migration duration significantly because we pace requests to stay within Nutshell's limits and avoid triggering throttling errors. We monitor response codes and automatically back off when throttling is detected, retrying with exponential delay. All record operations are logged to an audit file so you can trace every migrated ID back to its source AeronaClinic record for reconciliation. Large multi-location migrations should plan for the longer end of the typical timeline to account for these API constraints.

Migration approach

Six steps for a successful AeronaClinic to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

AeronaClinic logo

AeronaClinic

Source

Strengths

  • Fully cloud-based with no local server dependency, accessible from any browser on any device.
  • Integrated payment processing via GoCardless and Stripe with automatic reconciliation.
  • Patient Portal enables 24/7 appointment booking, form completion, and treatment plan viewing by patients.
  • Strong customer service reputation with 5.0/5.0 score for support on Capterra.
  • Built-in GDPR consent recording and e-signature features for UK/EU regulatory compliance.

Weaknesses

  • No native mobile application, limiting access for practitioners who prefer tablet or phone workflows.
  • Narrower feature set compared to enterprise dental platforms like Dentrix Ascend or CareStack, potentially requiring third-party integrations for specialist workflows.
  • The API documentation is password-protected and not publicly accessible, complicating third-party migration tooling and data export.
  • Limited published pricing information beyond the £45/month starting rate, with no public tier comparison.
  • Analytics and reporting dashboards are functional but lack the customisation depth that power users and multi-location practices require.
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. 1 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 AeronaClinic and Nutshell.

  • Object compatibility

    B

    1 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

    AeronaClinic: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your AeronaClinic 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 AeronaClinic to Nutshell data migrations

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

Can't find your answer?

Walk through your AeronaClinic to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most AeronaClinic-to-Nutshell migrations complete in 4–8 days for under 10,000 patient records with standard field mapping. Larger datasets with 30,000+ records, multi-office setups, and extensive custom field configurations extend to 3–6 weeks depending on complexity. Nutshell's API rate limits govern throughput for large appointment histories, and we pace requests to avoid throttling. Pre-migration schema creation (custom fields) and the sample migration approval step add 3–5 business days to the overall timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from AeronaClinic.
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