CRM migration
Field-level mapping, validation, and rollback between My Dental Clinic and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
My Dental Clinic
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
14 of 14
objects map 1:1 between My Dental Clinic and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3–7 days
Overview
My Dental Clinic stores patient records, appointments, treatment plans, insurance policies, and clinical notes in a practice-management schema optimized for dental workflows. Dynamics 365 Sales uses the Dataverse data model with Accounts, Contacts, Leads, Opportunities, and custom tables. The migration maps My Dental Clinic patients to Dynamics 365 Contacts (linked to Account records for the practice), appointments to Dataverse Activities, treatment plans to a custom TreatmentPlan table, and insurance information to custom fields on Contact plus a linked InsurancePolicy table. We use My Dental Clinic's export API to extract patient records and treatment histories, transform dental-specific fields (ICD-10 codes, ADA procedure codes, tooth numbers) into custom Dataverse columns, and load via Dynamics 365 Web API with bulk upserts for large patient databases. Workflows, appointment reminder sequences, and insurance claim logic do not migrate — those live in My Dental Clinic's practice-management engine and must be rebuilt in Dynamics 365 Power Automate flows or third-party dental integrations post-migration. FlitStack AI sequences the load so Contact.AccountId resolves before activity links, runs a field-level diff on a sample migration, then executes the full cutover with a 24–48-hour delta pickup 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.
Source platform
My Dental Clinic platform overview
Scorecard, SWOT, gotchas, and pricing for My Dental Clinic.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a My Dental Clinic object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
My Dental Clinic
Patient
Microsoft Dynamics 365 Sales
Contact
1:1My Dental Clinic patient records map to Dynamics 365 Contacts. The Contact's AccountId references the practice Account. Patient date of birth, allergies, and medical conditions migrate as custom fields on the Contact record. Email and phone are standard Contact fields.
My Dental Clinic
Patient Address
Microsoft Dynamics 365 Sales
Contact (Address Fields)
1:1Patient home address maps to the standard Dynamics 365 Contact address fields (address1_line1, address1_city, address1_state, address1_postalcode, address1_country). When My Dental Clinic stores separate billing and physical addresses, each type is assigned to the corresponding Dynamics 365 address field set to maintain data consistency and ensure correspondence reaches the correct location.
My Dental Clinic
Provider / Dentist
Microsoft Dynamics 365 Sales
SystemUser
1:1My Dental Clinic providers are matched to Dynamics 365 SystemUser records by email address matching to ensure accurate appointment and treatment attribution to the correct staff members. Unmatched providers are flagged for administrator review and can either be provisioned as Dynamics users before migration or linked to Contact records for provider visibility without CRM login access.
My Dental Clinic
Appointment
Microsoft Dynamics 365 Sales
Appointment (Activity)
1:1My Dental Clinic appointments map to Dynamics 365 Appointments with Subject, ScheduledStart, ScheduledEnd, Location (operatory), and Description. StatusReason maps to Activity's statecode. Note that Dynamics 365 Sales lacks native scheduling; appointments migrate as historical activity records, not active schedule entries.
My Dental Clinic
Treatment Plan
Microsoft Dynamics 365 Sales
TreatmentPlan (Custom Table)
1:1Treatment plans do not have a native Dynamics 365 equivalent. We create a custom TreatmentPlan Dataverse table with columns for ProcedureCode (ADA code), Description, ToothNumber, Surface, Fee, Status, TreatmentDate, and a lookup to the Contact record. Historical treatment plans load as completed records; active plans load with open status for case acceptance tracking.
My Dental Clinic
Treatment Procedure Line Item
Microsoft Dynamics 365 Sales
TreatmentPlanProcedure (Custom Table)
1:1Individual procedure line items within a treatment plan link to the parent TreatmentPlan record. Each line captures the ADA procedure code, tooth number, surface designation, fee amount, and completion status. This structure enables Dynamics reporting on procedure-level case acceptance rates and allows staff to track which specific treatments within a plan have been completed.
My Dental Clinic
Insurance Policy
Microsoft Dynamics 365 Sales
InsurancePolicy (Custom Table)
1:1Insurance records from My Dental Clinic create InsurancePolicy custom table entries linked to the Contact. Fields include CarrierName, PolicyNumber, GroupNumber, EffectiveDate, ExpirationDate, SubscriberName, RelationshipToSubscriber, and CoveragePercentages for major procedure categories. Primary and secondary policies are distinguished by a PolicyType column.
My Dental Clinic
Insurance Coverage Percentage
Microsoft Dynamics 365 Sales
InsurancePolicy (Custom Columns)
1:1My Dental Clinic stores per-category coverage percentages for preventive, basic, major, and ortho procedures. Each percentage value is mapped to a dedicated custom column on the InsurancePolicy record: CoveragePercentPreventive, CoveragePercentBasic, CoveragePercentMajor, CoveragePercentOrtho. Value-by-value mapping preserves every coverage tier without aggregation or data loss during migration.
My Dental Clinic
Clinical Note
Microsoft Dynamics 365 Sales
Annotation (Note)
1:1My Dental Clinic clinical notes and progress notes migrate as Dynamics 365 Annotations attached to the Contact record. The note subject references the appointment date and provider. Rich-text formatting is preserved where My Dental Clinic supports it. Notes are linked to the originating provider's SystemUser record.
My Dental Clinic
Billing / Ledger Entry
Microsoft Dynamics 365 Sales
Annotation or Custom Ledger Table
1:1Billing ledger entries do not map to native Dynamics 365 Sales objects. We surface them as text summaries in Contact Annotations for reference, or optionally create a custom LedgerEntry table linked to Contact. For practices requiring full billing history, integration with Dynamics 365 Finance or a dental billing module is recommended post-migration.
My Dental Clinic
Prescription
Microsoft Dynamics 365 Sales
Annotation or Custom Prescription Table
1:1Prescription records from My Dental Clinic are preserved as Annotations on the Contact with subject, medication, dosage, frequency, and prescribing provider. The note structure captures all key prescription details for clinical reference. For practices with high prescription volume, a custom Prescription table with structured fields can be created in Dataverse for improved searchability and reporting.
My Dental Clinic
Referral Source
Microsoft Dynamics 365 Sales
Custom Field on Contact or Account
1:1Referral source tracking in My Dental Clinic (doctor referral, patient referral, marketing campaign) migrates to a custom ReferralSource picklist field on Contact. For referral partner tracking, a custom ReferralPartner Account record can be linked to the Contact via a custom lookup relationship.
My Dental Clinic
Practice / Clinic Location
Microsoft Dynamics 365 Sales
Account
1:1For multi-location dental groups, each My Dental Clinic location becomes a Dynamics 365 Account record. The Account Name is the clinic name, with address, phone, and operational notes in standard Account fields. Related Contact records for the location's providers link to this Account via AccountId.
My Dental Clinic
Patient Photo / Document
Microsoft Dynamics 365 Sales
SharePoint Integration via Dynamics
1:1Patient photos and uploaded documents from My Dental Clinic are preserved in SharePoint and linked to Dynamics 365 Contacts via the native SharePoint document management integration. The original file names and upload dates are indexed in the Annotation record for traceability.
| My Dental Clinic | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Patient | Contact1:1 | Fully supported | |
| Patient Address | Contact (Address Fields)1:1 | Fully supported | |
| Provider / Dentist | SystemUser1:1 | Fully supported | |
| Appointment | Appointment (Activity)1:1 | Fully supported | |
| Treatment Plan | TreatmentPlan (Custom Table)1:1 | Fully supported | |
| Treatment Procedure Line Item | TreatmentPlanProcedure (Custom Table)1:1 | Fully supported | |
| Insurance Policy | InsurancePolicy (Custom Table)1:1 | Fully supported | |
| Insurance Coverage Percentage | InsurancePolicy (Custom Columns)1:1 | Fully supported | |
| Clinical Note | Annotation (Note)1:1 | Fully supported | |
| Billing / Ledger Entry | Annotation or Custom Ledger Table1:1 | Fully supported | |
| Prescription | Annotation or Custom Prescription Table1:1 | Fully supported | |
| Referral Source | Custom Field on Contact or Account1:1 | Fully supported | |
| Practice / Clinic Location | Account1:1 | Fully supported | |
| Patient Photo / Document | SharePoint Integration via Dynamics1: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.
My Dental Clinic gotchas
Dental ledgers are structurally complex to migrate accurately
Tooth-numbering systems differ between dental platforms
Insurance carrier IDs must be re-mapped post-migration
Custom clinical note templates may not map directly
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Audit My Dental Clinic export capabilities and design Dataverse schema
FlitStack AI begins every My Dental Clinic migration by mapping the available export method — API endpoint, CSV export, SQL query, or third-party extraction tool. We simultaneously design the Dynamics 365 Dataverse schema: the TreatmentPlan and InsurancePolicy custom tables, custom columns on Contact for allergies and medical conditions, and tooth/surface fields on TreatmentPlanProcedure. The schema design is delivered as a setup checklist before any data moves, so the Dynamics 365 environment is ready when migration runs.
Provision Dynamics 365 users and resolve provider-to-user mapping
Each My Dental Clinic provider record is matched to a Dynamics 365 SystemUser by email address. Providers without a corresponding Dynamics user are flagged — your admin creates the user record or assigns the provider's patient contacts to a fallback owner before migration. No Contact or Appointment record is loaded without a resolved OwnerId. This step also confirms Field Service licensing if active appointment scheduling is planned post-migration.
Migrate Contact records before appointments and treatment plans
Dynamics 365 requires Contact.AccountId to be set before activity records can link to contacts. FlitStack AI sequences the migration so Contact records load first (resolving the AccountId lookup for each practice location), followed by TreatmentPlan and InsurancePolicy custom table records that link to those contacts, then Appointment activity records. This foreign-key ordering prevents orphaned records and ensures treatment plan and insurance lookups resolve correctly in Dynamics.
Run sample migration with field-level diff
A representative sample — typically 100–300 patient records spanning multiple providers, appointments, and treatment plans — migrates first. FlitStack AI generates a field-level diff report showing source values versus destination values for every mapped column. You verify that tooth numbers, ADA codes, coverage percentages, and appointment timestamps transferred correctly. Any mapping gaps are corrected before the full migration run is scheduled.
Execute full migration with delta-pickup window
The full migration runs against Dynamics 365 using the verified field mappings. A delta-pickup window of 24–48 hours captures any patient records, appointments, or treatment plan changes that occurred in My Dental Clinic during the cutover. Audit logs document every record created or updated. One-click rollback is available if reconciliation finds unexpected discrepancies. After rollback window closes, My Dental Clinic remains accessible in read-only mode for 30 days for reference.
Platform deep dives
My Dental Clinic
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between My Dental Clinic and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across My Dental Clinic and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between My Dental Clinic and Microsoft Dynamics 365 Sales .
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
My Dental Clinic: Not publicly documented..
Data volume sensitivity
My Dental Clinic 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 My Dental Clinic to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your My Dental Clinic to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave My Dental Clinic
Other ways to arrive at Microsoft Dynamics 365 Sales
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.