Migrate from AeronaClinic to Microsoft Dynamics 365 Sales

AeronaClinic Patient maps to Dynamics 365 Contact as the primary person record. Patient first name, last name, date of birth, gender, address, phone, and email fields translate directly to Contact.FirstName, Contact.LastName, BirthDate, Gender, Address fields, and Contact.Phone/Email. A Contact's AccountId lookup must resolve to a parent Account created from the Patient's associated clinic or practice entity.

AeronaClinic stores a patient's primary clinic or practice as a related entity. This merges into Dynamics 365 Account — the Account Name becomes the clinic or practice name, with the primary Contact record linked via Account.PrimaryContactId. If the practice operates multiple locations, each location becomes a separate Account with parent-account hierarchy.

AeronaClinic Appointments (with date, time, provider, treatment type, and status) migrate as Dynamics 365 Appointments (ActivityPointer entity). The appointment start time, duration, and status map to ScheduledStart, ScheduledDuration, and StateCode. The associated provider resolves to a Dynamics 365 User by email match. Treatment type stored as a custom field on the Activity.

AeronaClinic Treatment Plans have no direct Dynamics 365 equivalent — the platform lacks a clinical treatment schema. We create a custom Dataverse table (msdyn_treatmentplan) with columns for procedure code, description, estimated cost, and status. Each treatment plan links to the Contact record via a lookup column. Custom table creation must be completed in the destination environment before data loads run.

AeronaClinic clinical notes (provider notes attached to treatment or appointment) migrate to a custom Dataverse table (msdyn_clinicalnote) with columns for note text, created date, provider, and related Contact. Dynamics 365 Notes (annotation) are text-only and lack the schema depth needed for clinical documentation, so a custom table is required. Field-level security may need configuration for HIPAA-adjacent data.

AeronaClinic billing records (invoice number, amount, status, payment method, date) have no native Dynamics 365 equivalent — Opportunities track revenue but not itemized patient billing. We create a custom Dataverse table (msdyn_patientinvoice) linked to Contact and Account. Payment status (paid, pending, overdue) requires a status-option set configured in the Dynamics 365 environment before migration.

AeronaClinic allows multiple Guarantors and Emergency Contacts per Patient — a 1:N relationship model. Dynamics 365 Contact supports a similar model via Contact.ParentContactId for a primary contact and Account.PrimaryContactId for the main patient-contact link. Additional relationship types require a custom Contact Relationship type or a custom junction table to preserve the distinction between Guarantor and Emergency Contact roles.

AeronaClinic providers (dentists, hygienists, admin staff) map to Dynamics 365 SystemUser records by email resolution. The provider's role in AeronaClinic (clinical vs. administrative) does not map directly to Dynamics 365 Security Roles — those must be assigned manually post-migration or based on a role-mapping table provided by the practice administrator.

AeronaClinic procedure codes (e.g., D7140, D2750) used in treatment plans map to Dynamics 365 Product records. Each procedure code becomes a Product with its description, default price from the fee schedule, and unit. Price list associations must be created in Dynamics 365 before opportunity and invoice records can reference them.

AeronaClinic documents (treatment plans, consent forms, insurance cards) attached to patient records migrate to Dynamics 365 SharePoint integration if SharePoint is configured, or to Note (Annotation) records if not. We re-upload files to the associated Contact or Account document location, preserving original filenames and upload timestamps.