CRM migration

Migrate from My Dental Clinic to Microsoft Dynamics 365 Sales

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 logo

My Dental Clinic

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

100%

14 of 14

objects map 1:1 between My Dental Clinic and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

3–7 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

My Dental Clinic logo

My Dental Clinic

What's pushing teams away

  • Customer service scores lag behind category leaders, with users reporting slow response times and difficulty reaching support during urgent issues.
  • Feature set feels limiting as practices grow beyond single-location operations, with fewer advanced reporting and multi-location management tools than competitors.
  • Lower value-for-money ratings compared to platforms offering broader feature bundles at similar price points.
  • Integration ecosystem is narrower than major dental platforms, making connectivity to specialized imaging or lab systems a friction point.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How My Dental Clinic objects map to Microsoft Dynamics 365 Sales

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

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

My 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

maps to

Microsoft Dynamics 365 Sales

Contact (Address Fields)

1:1
Fully supported

Patient 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

maps to

Microsoft Dynamics 365 Sales

SystemUser

1:1
Fully supported

My 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

maps to

Microsoft Dynamics 365 Sales

Appointment (Activity)

1:1
Fully supported

My 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

maps to

Microsoft Dynamics 365 Sales

TreatmentPlan (Custom Table)

1:1
Fully supported

Treatment 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

maps to

Microsoft Dynamics 365 Sales

TreatmentPlanProcedure (Custom Table)

1:1
Fully supported

Individual 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

maps to

Microsoft Dynamics 365 Sales

InsurancePolicy (Custom Table)

1:1
Fully supported

Insurance 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

maps to

Microsoft Dynamics 365 Sales

InsurancePolicy (Custom Columns)

1:1
Fully supported

My 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

maps to

Microsoft Dynamics 365 Sales

Annotation (Note)

1:1
Fully supported

My 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

maps to

Microsoft Dynamics 365 Sales

Annotation or Custom Ledger Table

1:1
Fully supported

Billing 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

maps to

Microsoft Dynamics 365 Sales

Annotation or Custom Prescription Table

1:1
Fully supported

Prescription 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

maps to

Microsoft Dynamics 365 Sales

Custom Field on Contact or Account

1:1
Fully supported

Referral 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

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

For 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

maps to

Microsoft Dynamics 365 Sales

SharePoint Integration via Dynamics

1:1
Fully supported

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

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.

My Dental Clinic logo

My Dental Clinic gotchas

High

Dental ledgers are structurally complex to migrate accurately

Medium

Tooth-numbering systems differ between dental platforms

Medium

Insurance carrier IDs must be re-mapped post-migration

Medium

Custom clinical note templates may not map directly

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • Dental export limitations create partial patient record pulls

    Many My Dental Clinic deployments do not expose a full REST API for patient data export. Reddit threads from the r/Dentistry community document that practice managers resort to manual exports, report writers, or third-party data extraction tools to get complete patient records. FlitStack AI works from whatever export method is available — CSV, SQL dump, or API — and flags any fields that cannot be extracted before the migration schema is finalized. Practices should confirm their export capabilities in the discovery phase to avoid surprises during the cutover window.

  • Custom TreatmentPlan table requires Dataverse provisioning before data loads

    Dynamics 365 Sales does not have a native treatment plan entity. Before any treatment data can migrate, a custom TreatmentPlan Dataverse table must be provisioned in the target environment with the ADA procedure code, tooth number, surface, fee, and status columns. Dynamics 365 Enterprise licenses allow unlimited custom tables; Sales Professional allows up to 15 custom tables. Practices on Sales Professional with multiple custom tables for insurance and prescriptions should verify they have capacity before the migration plan is committed. FlitStack delivers the schema design as part of the pre-migration plan.

  • Appointment records migrate as activities, not live schedule entries

    My Dental Clinic's native appointment calendar does not have a direct equivalent in Dynamics 365 Sales. Appointment history migrates as completed Appointment activity records attached to the Contact, preserving date, provider, operatory, and procedure type. However, Dynamics 365 Sales cannot drive an active scheduling workflow without the Dynamics 365 Field Service module ($95/user/month) or a third-party dental scheduling integration. Practices expecting to run their appointment calendar from Dynamics 365 after migration need to budget for Field Service or a compatible scheduling connector.

  • Insurance policy coverage percentages need value-by-value mapping

    My Dental Clinic stores insurance coverage as per-category percentages (preventive, basic, major, ortho) on the patient insurance record. Dynamics 365 has no native coverage percentage fields. FlitStack AI maps each coverage category to a dedicated custom column on the InsurancePolicy table (CoveragePercentPreventive, CoveragePercentBasic, etc.). If My Dental Clinic uses custom coverage tier names beyond the standard four categories, each one requires a custom column created in Dataverse before migration. The migration plan documents every insurance field in the source and the corresponding Dataverse column before the migration run.

  • HIPAA compliance obligations carry over and must be re-established

    Patient clinical notes, allergy data, and treatment records moved to Dynamics 365 are protected health information under HIPAA. My Dental Clinic's existing Business Associate Agreement with Microsoft for Dynamics 365 must be confirmed or established before patient data is loaded. Dynamics 365's field-level security, audit logging, and data loss prevention features should be configured for the dental data columns. FlitStack AI documents the HIPAA-relevant fields in the migration plan and can configure Dataverse field-level security for allergies and medical conditions as part of the migration engagement.

Migration approach

Six steps for a successful My Dental Clinic to Microsoft Dynamics 365 Sales data migration

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

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

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

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

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

Context on both ends of the pair

My Dental Clinic logo

My Dental Clinic

Source

Strengths

  • Web-based, browser-accessible interface requiring no local server installation or maintenance overhead.
  • Automated patient communication tools including appointment reminders and intake form collection reduce front-desk workload.
  • Specialized dental workflow features including tooth charting and perio charting built into the core product rather than add-ons.

Weaknesses

  • Narrower third-party integration ecosystem compared to major dental platforms, limiting connectivity with specialized imaging and lab vendors.
  • Per-feature pricing model can become unpredictable in cost as practices add modules over time.
  • Customer service responsiveness scores trail category competitors, creating risk for practices that need timely support during transitions.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between My Dental Clinic and Microsoft Dynamics 365 Sales .

B

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

    A

    All 8 core objects map 1:1 between My Dental Clinic and Microsoft Dynamics 365 Sales .

  • 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

    My Dental Clinic: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

Estimate your My Dental Clinic to Microsoft Dynamics 365 Sales 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 My Dental Clinic to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during My Dental Clinic to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most My Dental Clinic to Dynamics 365 migrations complete in 3–7 days of clock time for practices with under 10,000 patient records. Multi-location groups with treatment history, insurance records, and provider-to-user mapping for 10,000–50,000 patients extend to 2–4 weeks. The longest planning step is confirming My Dental Clinic's export capabilities and designing the custom Dataverse TreatmentPlan and InsurancePolicy tables before data moves.

Adjacent paths

Related migrations to explore

Ready when you are

Move from My Dental Clinic.
Land in Microsoft Dynamics 365 Sales , 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