CRM migration
Field-level mapping, validation, and rollback between AeronaClinic and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
AeronaClinic
Source
Freshsales
Destination
Compatibility
12 of 12
objects map 1:1 between AeronaClinic and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
AeronaClinic stores patient records, appointments, providers, treatment plans, clinical notes, and billing transactions as a unified practice-management graph. Freshsales (Freshworks CRM) uses a standard sales CRM object model — Leads, Contacts, Accounts, Deals, Tasks, and Events — with Freshsales-specific modules available on Pro and Enterprise plans. The two models diverge significantly: AeronaClinic has no native equivalent to Freshsales Deals or Sales Activities; appointment records do not map to Freshsales Events without a custom-date transformation; treatment-plan line items and procedure codes require a custom module or custom fields on Contacts. We extract AeronaClinic data via its export API and CSV output, normalize patient demographics into Freshsales Contacts, map providers to Freshsales Users, and translate appointment slots into Freshsales Tasks with original start/end timestamps. Workflows, automated reminders, and patient-portal logic cannot migrate — Freshsales has no equivalent to AeronaClinic's appointment-reminder engine. We run a sample migration with field-level diff before the full cutover so your team validates every mapping before data lands in Freshsales.
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 Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
AeronaClinic
Patient
Freshsales
Contact
1:1AeronaClinic Patient maps directly to Freshsales Contact. First name, last name, email, phone, address, date of birth, and gender transfer as standard contact fields. The original AeronaClinic patient ID is preserved in Source_System_ID__c for traceability and delta-run de-duplication. This custom field also enables accurate record linking during incremental syncs after the initial migration, ensuring no duplicate patients are created when the source system continues to receive updates.
AeronaClinic
Patient
Freshsales
Lead
1:1Patients who have not yet booked a treatment appointment (referral-only records, inquiry records) map to Freshsales Lead. Name, email, phone, and referring-provider fields transfer; status defaults to 'New Lead' in Freshsales unless a conversion rule is pre-defined. If your sales process defines specific lead stages for referral sources, we map those to corresponding Freshsales lead status values during migration, preserving the original referral type for reporting.
AeronaClinic
Appointment
Freshsales
Task
1:1AeronaClinic appointments become Freshsales Tasks with Task Type set to 'Appointment'. Original appointment start time, end time, and provider owner map to Freshsales Task Due Date, Subject, and Owner respectively. The appointment status (confirmed, completed, no-show) maps to a custom pick-list field since Freshsales Tasks have no appointment-specific status.
AeronaClinic
Appointment
Freshsales
Event
1:1For appointments with specific time slots and calendar requirements, AeronaClinic appointments map to Freshsales Events (Freshsales Pro and Enterprise). Event Subject, Start Date/Time, End Date/Time, and Assigned User transfer. All-day flag and reminder settings require Freshsales workflow recreation. If your clinic relies on all-day events or recurring reminders, we capture the original flags in custom fields (All_Day_Event__c, Reminder_Flag__c) so your Freshsales admin can configure the appropriate workflow triggers post-migration.
AeronaClinic
Provider
Freshsales
User
1:1AeronaClinic providers (dentists, hygienists, practice managers) resolve by email match to Freshsales Users. Provider role in AeronaClinic (e.g., Principal Dentist) maps to a custom text field on the Freshsales User record. If a provider email has no Freshsales user match, records are assigned to a fallback owner flagged before migration.
AeronaClinic
Treatment Plan
Freshsales
Custom Module (Enterprise) / Custom Fields on Contact
1:1AeronaClinic treatment plans (procedure codes, tooth surfaces, materials, fees) have no Freshsales native equivalent. On Enterprise plans this maps to a Freshsales Custom Module named 'Treatment_Plan__rv'. On Growth/Pro plans, treatment plan fields become custom fields on the Contact record: Treatment_Plan_Status__c, Procedure_Code__c, Estimated_Fee__c.
AeronaClinic
Clinical Note
Freshsales
Note
1:1AeronaClinic clinical notes (per-appointment clinical observations, clinical flags, medical history flags) migrate as Freshsales Notes attached to the Contact record. Notes preserve the original timestamp and provider owner. Long-form clinical notes that exceed Freshsales Notes character limits are split across multiple note records with a sequence prefix.
AeronaClinic
Invoice / Billing Record
Freshsales
Deal Product (on Deal)
1:1AeronaClinic invoice line items (procedure, fee, payment status) map to Freshsales Deal Products linked to a Deal. A Deal named after the patient's active treatment plan is created; invoice totals map to the Deal Amount. Outstanding balance maps to a custom field as Freshsales Deals do not track payment installment schedules natively.
AeronaClinic
Patient Portal / Recall
Freshsales
Freshsales Workflow (manual rebuild)
1:1AeronaClinic patient portal settings and recall/automated reminder logic have no Freshsales equivalent — Freshsales Workflows handle task creation but not patient-facing appointment reminders or recall sequences. We export the recall configuration as a reference document for your Freshsales admin to rebuild using Freshsales Workflows or Freshmarketer (available via Freshsales Suite upgrade).
AeronaClinic
Custom Clinic Fields
Freshsales
Custom Fields on standard objects
1:1Any custom fields configured in AeronaClinic (e.g., referral source, insurance provider, preferred appointment time) migrate as Freshsales custom fields on the relevant object. Field data type is preserved: text to text, pick-list to pick-list, date to date. Freshsales custom fields are created during the pre-migration schema setup phase.
AeronaClinic
Practice Location
Freshsales
Account
1:1AeronaClinic multi-location setups: each clinic location becomes a Freshsales Account record with name, address, and phone. Patients are linked to their primary clinic via AccountId on the Contact record. Provider schedules can be associated with the Account record via custom fields.
AeronaClinic
Document / File Attachment
Freshsales
Freshsales File
1:1Patient documents attached to AeronaClinic records (treatment consent forms, imaging references) are downloaded and re-uploaded as Freshsales Files, linked to the Contact record. File size limits: Freshsales Growth/Pro allow up to 5GB per user; Enterprise allows 100GB per user. We also preserve the original file name and upload timestamp as metadata fields, ensuring your team can verify the source and date of each document after migration.
| AeronaClinic | Freshsales | Compatibility | |
|---|---|---|---|
| Patient | Contact1:1 | Fully supported | |
| Patient | Lead1:1 | Fully supported | |
| Appointment | Task1:1 | Fully supported | |
| Appointment | Event1:1 | Fully supported | |
| Provider | User1:1 | Fully supported | |
| Treatment Plan | Custom Module (Enterprise) / Custom Fields on Contact1:1 | Fully supported | |
| Clinical Note | Note1:1 | Fully supported | |
| Invoice / Billing Record | Deal Product (on Deal)1:1 | Fully supported | |
| Patient Portal / Recall | Freshsales Workflow (manual rebuild)1:1 | Fully supported | |
| Custom Clinic Fields | Custom Fields on standard objects1:1 | Fully supported | |
| Practice Location | Account1:1 | Fully supported | |
| Document / File Attachment | Freshsales File1: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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Discover AeronaClinic schema and define Freshsales target schema
FlitStack AI reads the AeronaClinic export API output and identifies every object, field, and relationship in the source. We generate a schema mapping plan that names the Freshsales objects and fields each AeronaClinic entity maps to — including custom field names, pick-list values, and the decision between Custom Modules (Enterprise) vs. custom fields on Contacts (Growth/Pro). This plan is shared with your team for approval before any data movement begins. We also identify records that lack a destination equivalent and document them as no_equivalent items needing manual handling.
Resolve AeronaClinic providers to Freshsales users by email
FlitStack AI matches AeronaClinic provider records to Freshsales users by email address. Any provider with no corresponding Freshsales user is flagged before migration — your team either creates the Freshsales user first or assigns those providers' records (appointments, notes, treatment plans) to a designated fallback user. No appointment, note, or clinical record lands without a valid Freshsales owner. Provider-to-user resolution is validated in the sample migration phase before the full run.
Migrate contacts and leads first, then accounts and locations
Freshsales requires a valid AccountId on Contact records for most reporting features. We sequence the migration so Account records (clinic locations) are created first, then Contacts are migrated with AccountId populated from the resolved location. For patients without a primary clinic assignment, we create an 'Unassigned' Account record. Appointment records follow Contacts so they can link to the correct Contact and Owner. Treatment plans and invoices are migrated last, after the Contact and Deal records they reference are in place.
Run sample migration with field-level diff before full cutover
FlitStack AI migrates a representative slice — typically 100–500 records covering patients, appointments, providers, treatment plans, and invoices — and generates a field-level diff report. You can verify that patient IDs map to Source_System_ID__c, appointment timestamps are preserved, treatment plan status values translated correctly, and provider ownership resolved. The diff report highlights any field where source and destination values differ, so you confirm mappings before the full migration run commits. If the sample reveals a mapping error, we adjust the plan and re-run the sample.
Execute full migration with delta-pickup and rollback capability
The full migration runs against Freshsales using the validated mapping plan. A delta-pickup window of 24–48 hours captures any records created or modified in AeronaClinic during the cutover — your team keeps working in AeronaClinic throughout this period. FlitStack AI logs every create, update, and link operation to an audit log. If reconciliation reveals a data integrity issue, one-click rollback reverts the Freshsales environment to its pre-migration state. After rollback confirmation, you decide whether to proceed with a corrected mapping or re-run.
Platform deep dives
AeronaClinic
Source
Strengths
Weaknesses
Freshsales
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 AeronaClinic and Freshsales.
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
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 Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your AeronaClinic to Freshsales 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 Freshsales
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.