← Back to Blog
Business·10 min read·Mar 25, 2026

The Migration Tax: What Your Dental Software Vendor Doesn't Want You to Know

Your patient data belongs to you. That is not a controversial statement. But when you try to leave your current dental software vendor, you will discover that accessing your own data comes with a price tag that makes no technical sense.

The dental software industry has perfected a retention strategy disguised as a service fee. Vendors call it “data extraction” or “migration assistance.” The industry calls it the migration tax.

How Much Does It Cost to Switch Dental Software?

Switching dental software typically costs $3,000 to $10,000 per location in extraction fees alone. When you factor in lost productivity during 6-to-12-week migration timelines, staff retraining, and data validation labor, the total cost of switching reaches $15,000 to $25,000 per location for most practices.

The extraction fee is the most visible part of the migration tax. Vendors charge it as a flat per-location fee to export your patient records, treatment histories, insurance data, and clinical images into a format another system can read.

But the extraction fee is only the beginning. The real cost includes weeks of dual-system operation, staff overtime to validate migrated records, and the inevitable productivity dip as your team learns new workflows while seeing a full schedule of patients.

How Long Does It Take to Migrate Dental Software?

Traditional dental software migrations take 6 to 12 weeks per location, including data export, format conversion, validation, and staff retraining. Modern cloud-native platforms like NexV complete the same migration in a single weekend using automated import tools that read proprietary formats directly, eliminating the multi-week export request process entirely.

Why Do Vendors Use Proprietary Data Formats?

Dental software vendors store your data in proprietary database schemas and file formats. Your patient charts, clinical notes, treatment plans, and imaging metadata are encoded in structures that only the vendor's software can read natively.

This is not a technical necessity. Open data standards exist. HL7 FHIR, ADA CDT coding, and standard SQL databases are available to any vendor that chooses to use them. Proprietary formats exist because they create a switching cost.

When your data lives in a format that only one vendor can read, that vendor controls your ability to leave. The extraction fee is not compensation for the labor of converting data. It is a toll charged at the only exit from a walled garden.

Some vendors take this further by storing clinical images in proprietary containers. Your X-rays, intraoral photos, and CBCT scans are wrapped in a format that requires the vendor's proprietary viewer. Even if you export the images, you may lose metadata, annotations, and the association between images and patient records.

Can I Keep Using My Current System During Migration?

Yes. A properly executed migration runs in parallel with your existing system. Your current dental software remains fully operational throughout the export and conversion process. NexV works from a copy of your database, not your live production system, so there is zero disruption to daily patient care during the transition period.

The Real Timeline of a Traditional Migration

Vendor sales teams will tell you migration takes “a few weeks.” The reality for most practices is 6 to 12 weeks per location, and that timeline assumes everything goes according to plan.

Here is what actually happens during a traditional dental software migration:

  • Weeks 1-2: Data export request.You submit a formal request to your current vendor. Some vendors require 30 days' notice. Others process export requests “in the order received” with no guaranteed timeline.
  • Weeks 3-4: Data conversion. The exported data arrives in a proprietary or semi-structured format. The receiving vendor must build or run conversion tools to map fields from the old system to the new one. Patient IDs, provider IDs, procedure codes, and insurance plan structures rarely map one-to-one.
  • Weeks 5-8: Validation. Your team manually spot-checks migrated records against the original system. Discrepancies in treatment histories, account balances, and insurance assignments must be resolved before go-live. This is where most migrations stall.
  • Weeks 8-12: Parallel operation. Best practice dictates running both systems simultaneously for 2 to 4 weeks after go-live. During this period, your team enters data in both systems, doubles their administrative workload, and incurs license fees for both platforms.

For a DSO migrating 10 locations sequentially, this process can consume an entire calendar year. The cumulative cost in license overlap, staff overtime, and productivity loss dwarfs the initial extraction fee.

The Migration Tax Is a Retention Strategy

Every element of the traditional migration process serves the same purpose: making switching painful enough that practices stay. The proprietary data format ensures you cannot leave without the vendor's cooperation. The extraction fee punishes you financially for leaving. The extended timeline ensures months of disruption that make the whole exercise feel like it was not worth the trouble.

This is not cynicism. It is a documented business model. Enterprise software vendors across every industry use switching costs as a competitive moat. The dental software market is no different, except that the practices paying the migration tax are often small businesses that can least afford it.

The clearest evidence that the migration tax is artificial is this: the marginal cost of exporting a database is essentially zero. Your data already exists in a structured format. Converting it to a standard export format is a script that runs in minutes, not a professional service that requires thousands of dollars. The migration tax is just one component of a larger cost structure that per-seat pricing models amplify even further.

What Data Can Be Migrated from Dental Software?

A complete dental software migration transfers patient demographics, clinical histories, treatment plans, insurance records, billing ledgers, appointment histories, clinical images, and document attachments. Procedure codes are mapped between systems, and imaging files retain their patient associations, metadata, and annotations throughout the process.

How NexV Eliminates the Migration Tax

NexV imports data from D4W, EXACT, Oasis, Dentrix, Eaglesoft, and Open Dental at no charge. There is no extraction fee, no conversion surcharge, and no professional services invoice for getting your own data into the system.

The technical approach is different from traditional migrations. NexV's import tools read proprietary formats directly. Instead of requiring the old vendor to export data in a specific format, NexV's conversion engine parses the source database structures and maps them automatically to the NexV data model.

This eliminates the multi-week export request process. There is no waiting for your old vendor to queue your export. The migration team works directly with a copy of your existing database, which means the timeline compresses from months to days.

NexV's migration promise is a single weekend. Friday evening, the migration team takes a final snapshot of your existing system. Saturday, the automated import runs and the team validates the results. Sunday, your staff receives a walkthrough of the new system. Monday morning, you open in NexV.

That timeline is possible because the AI-powered mapping engine handles the field translation that traditionally requires weeks of manual configuration. Patient demographics, treatment histories, ledger entries, insurance plans, and clinical images are mapped programmatically with automated validation checks at each stage.

What About Clinical Images and Attachments?

Clinical images are the most frequently cited blocker in dental software migrations. Practices accumulate thousands of X-rays, intraoral photos, and CBCT volumes over years of operation. The prospect of losing those images or their associations with patient records keeps many practices locked into software they have outgrown.

NexV's migration handles images as first-class data. Every image is imported with its original metadata, patient association, date stamps, and any annotations or measurements that existed in the source system. The images are stored in industry-standard DICOM and JPEG formats in your dedicated AWS environment, accessible through NexV's integrated imaging viewer.

After migration, your images are yours. They live in standard formats in cloud storage you control. If you ever leave NexV, you can download your complete image archive in standard formats with no extraction fee.

The Financial Case for Ripping Off the Band-Aid

Practices often delay switching software because the migration cost feels prohibitive. But this calculation ignores the ongoing cost of staying with an inferior system.

Consider a 5-provider practice paying $500 per provider per month for a legacy PMS, plus $300 per month for a separate patient communication tool, $200 per month for imaging integration, and $150 per month in clearinghouse surcharges. The monthly cost of the fragmented stack is $3,150. Annually, that is $37,800.

NexV's all-in-one platform includes practice management, imaging, patient communication, and claims processing for a flat monthly fee. The delta between the fragmented stack and the consolidated platform often exceeds $20,000 per year, which means the migration pays for itself within the first year even if the migration itself were expensive.

When the migration is free, the math is even simpler. Every month you delay switching is a month of overpaying for a system you have already decided to replace.

What to Ask Your Current Vendor Right Now

Whether or not you are actively considering a switch, you should know the answers to these questions about your current software:

  • What format is my data stored in? If the answer is a proprietary format with no standard export option, your data is being held hostage.
  • What is the cost to export my complete patient database? Get the number in writing. If it exceeds a few hundred dollars, you are looking at a retention mechanism, not a service fee.
  • What is the timeline for a data export?Any answer longer than “we can have it to you this week” indicates a process designed to slow you down.
  • Do clinical images export with patient associations? If images export as a flat file dump with no metadata, you will spend weeks manually re-associating them with patient records.
  • Is there an early termination fee on my contract? Many vendors layer an early exit penalty on top of the extraction fee, making the total switching cost even higher.

The answers to these questions will tell you whether your vendor views you as a customer or a captive. A vendor that makes it easy to leave is a vendor that earns your business every month. A vendor that makes it painful to leave is a vendor that knows you would go if you could.

The Industry Is Changing

Data portability is not a radical concept. Banking, healthcare, and telecommunications all have regulatory frameworks that guarantee your right to move your data between providers. The dental software industry has operated without these guardrails, and vendors have taken full advantage.

That is changing. Practices are demanding interoperability. DSOs are negotiating data portability clauses into their contracts. And a new generation of cloud-native platforms is proving that migration does not have to be a multi-month, five-figure ordeal. The technology dividend from modern cloud-native architecture makes free migration economically sustainable for vendors who build their own tools.

The migration tax exists because the industry allowed it to exist. The way to end it is to choose vendors who do not charge it, and to demand portability from those who do. Your data is yours. The cost of accessing it should be zero.

For a detailed breakdown of the total cost of ownership across dental software vendors, see our DSO Director's Guide to Dental Software Costs. And for multi-location organizations evaluating a platform change, NexV's migration team will run a free data assessment before you commit to anything.

Ready to see NexV in action?

Book a Demo