I wrote the standard for making websites AI-operable. Learn More
Migration · Dentrix to Curve Dental
Moving from a server in your back office to a cloud system is usually the right call, and Curve's importer handles the standard shape of a dental practice well. The friction in this pair is not the destination — it is that a cloud target accepts data in the structure it expects, and fifteen years of Dentrix does not necessarily arrive in that structure.
That constraint is worth understanding before you start, because it decides which of your history is worth paying to carry and which is better left in a read-only archive.
Dentrix stores data in a proprietary engine rather than an open database, so extraction runs through some combination of the Dentrix API where it is licensed and available, structured report exports, and direct reads of the underlying tables where access permits. Curve is cloud-hosted and accepts conversions through a defined intake path. That combination — an opaque source and a structured, opinionated destination — is what shapes this engagement: the work is getting your history into the shape the destination will accept without losing the parts that matter.
Each of these gets its own record count in the assessment and its own line in the reconciliation report. Depth of history is a scope decision made with real numbers in front of you, not an assumption baked into a quote.
Patients and family structure
Demographics, contact details, guarantor relationships, and the family groupings that drive statements and balances.
Ledger and account balances
Charges, payments, adjustments, and balances reconciled against a Dentrix-side aging report before load.
Procedures and treatment history
Completed procedures with CDT codes, surfaces, dates, and provider attribution.
Treatment plans
Planned but uncompleted procedures with their fee estimates, so presented treatment survives the move.
Insurance plans and benefits
Carriers, plan definitions, subscriber links, maximums, deductibles, and used-to-date figures, deduplicated during mapping.
Appointments and recall
Future appointments and continuing-care due dates, so the hygiene schedule is intact on day one.
Clinical notes
Progress notes carried as text against the correct patient, visit, and provider.
Images and attachments
Usually held by a separate imaging application. Whether they move, get bridged, or stay in place is settled during the assessment — for a cloud destination this question matters more than it does on-premise.
Written down before you spend anything, because the alternative is finding out in week six. This list is specific to Dentrix to Curve Dental; the assessment turns it into your list, with record counts attached.
— History that does not fit the destination's expected structure. This is the defining constraint of a cloud target: the importer accepts a defined shape, and anything outside it either gets reshaped during mapping or stays in the archive. The assessment tells you which of your data is which, with record counts attached.
— Perio charts as chartable exams, except where Dentrix held them as measurement data. Where they exist as rendered images or as text inside notes, they arrive as images or notes.
— Rich formatting in clinical notes. Content moves; layout generally does not.
— Dentrix customizations — custom buttons, macros, note templates, and screen configuration. Rebuilt on the Curve side as separately scoped work.
— Your local imaging archive, unless bridging it is explicitly in scope. Moving from on-premise to cloud is exactly when practices discover how much of their record lives on a server they were about to decommission.
— Insurance claims as live, resubmittable items. Open claims are worked to completion in Dentrix before the switch.
None of this is in either vendor's documentation. It is the category of thing that looks fine in a test load and produces a wrong number in month two, which is why the process puts a full sandbox load and a reconciliation you sign in front of any production cutover.
01
With an on-premise destination you can generally load what you have. With a cloud destination the accepted structure is fixed, which turns some of your history into a reshaping problem rather than a copying problem. That reshaping is the work, and it is why the mapping document matters more here than on an on-premise-to-on-premise pair.
02
The moment the practice goes cloud, the old server starts looking like an expense nobody wants. Keep it. Read-only Dentrix is the archive that makes prior-period questions answerable and the migration reversible, and it should outlive the cutover by at least a year.
03
Dentrix's family and account structure does not translate one-to-one to any destination. Divorced families, patients who are their own guarantor, and dependents on a third party's insurance are where naive maps produce wrong balances. Signed off before the test load, reconciled after.
04
Curve converts practices as a matter of course and for a straightforward single location they may well be all you need — I will say so if that's what the assessment shows. Independent work earns its fee on multi-location groups, practices with a prior conversion buried in their data, and anyone who wants the reconciliation and rollback owned by someone accountable to them rather than to the vendor they are buying from.
01 — 02
A read-only audit of your Dentrix instance produces record counts, a risk register, and a fixed quote. Then a field-by-field mapping document you sign before any code runs.
03 — 04
The complete migration runs into a Curve Dental sandbox — not a sample. You spot-check records you choose, and sign a written reconciliation. If the counts don't tie, we don't cut over.
05 — 06
Scheduled around your calendar with the rollback plan written in advance, followed by 30 days of included corrections for the things that only surface in real use.
A single location with reasonable history usually lands in Standard Migration. Multi-location groups, or practices where imaging bridging and a long clinical archive are both in scope, move toward Complex. The assessment is what makes a fixed migration price possible, and its fee is credited toward the migration if you proceed.
Tier
Scope
Price
Migration Assessment
A read-only audit of your source system.
$1,500 – $2,500
Standard Migration
One source system to one destination.
$6,500 – $15,000
Complex / Multi-Entity Migration
Multiple locations, systems, or long history.
$18,000 – $40,000
Quite possibly, and that's a real answer rather than a polite one. For a single clean location, the vendor's conversion is often sufficient and cheaper. What independent work adds is extraction from an opaque source system, interpretation of your specific field conventions, a reconciliation you sign, and a rollback plan — which matters most for multi-location groups and for practices whose data has already been through one conversion.
Keep it, read-only, for at least a year. It is both your prior-period archive and the thing that makes the migration reversible. Budgeting to decommission it immediately is the most common expensive mistake in an on-premise-to-cloud move.
More than people expect for ledgers and procedures, less than people hope for clinical notes and perio. The honest number comes from the assessment, per object, before you commit to anything.
Cutover is scheduled for a closed weekend and the practice opens Monday on Curve. Nothing touches production until the sandbox load has been validated and you have signed the reconciliation report.
The assessment is the read-only audit — what data exists, what is extractable, what will be lost, and a fixed-price quote for the migration itself. It is priced at $1,500 – $2,500 depending on scope, fixed before anything starts, and the report is yours whether or not you go further.
Tell me what you're moving. I read every one of these personally and reply within one business day, usually with a couple of specific questions about your source system — the answers change the price, so it's worth asking early.
Nothing is committed by this form. No payment, no contract, no scheduling sequence. It starts a conversation.
If your destination vendor can handle it, I'll say so. Some conversions genuinely don't need an independent migration.
Standard – Complex
Whether perio exists as data.
Standard – Complex
The account-versus-patient split.
Every pair
Twenty-odd pairs are written up across seven industries — and the written ones are not the limit of the work. Search the full list, or just ask.
Dentrix and Curve Dental are trademarks of their respective owners. This page describes independent data migration work involving those systems and does not imply any affiliation with, partnership with, or endorsement by either vendor.
Before you give notice on Dentrix
The most expensive mistake in this category is losing source-system access before the extraction is done. The assessment is read-only, fixed-price, and yours to keep either way.
I respond personally within 1 business day. No pitch — just a real conversation.