I wrote the standard for making websites AI-operable. Learn More
Migration · Eaglesoft to Open Dental
Open Dental is cheaper, open, and you own your data on the far side. None of that helps if the migration garbles clinical notes, drops perio exams, or leaves the account structure in a state where nobody's balance is right on Monday.
The good news, relative to some of the other systems in this category: Eaglesoft sits on a real relational database, which makes extraction meaningfully more tractable. The difficulty moves to interpretation — specifically, the way Eaglesoft splits accounts from patients.
Eaglesoft stores its data in SQL Server, which is a genuine advantage — with appropriate access, the tables can be read directly rather than scraped out through reports. Open Dental runs on MySQL with a published, documented schema. That makes this one of the more transparent pairs on this page from a pure data-plumbing standpoint, and it means the assessment can produce hard record counts rather than estimates. What remains hard is semantic: deciding what a decade of your practice's field conventions actually meant.
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 account structure
Demographics, contact details, and the account-to-patient relationships that determine who is billed for whom. Mapped explicitly — see the quirks section, because this is the crux of this pair.
Ledger and balances
Charges, payments, adjustments, and running balances reconciled against an Eaglesoft-side aging report before load. History depth is a scope decision.
Procedures and treatment history
Completed procedures with CDT codes, surfaces, quadrants, dates, and provider attribution — the clinical spine recall and treatment planning both depend on.
Treatment plans
Planned but uncompleted procedures with their phasing and fee estimates, so nothing presented to a patient last month vanishes this month.
Insurance plans, subscribers, and benefits
Carriers, plan definitions, subscriber and dependent links, annual maximums, deductibles, and used-to-date figures — deduplicated rather than imported once per patient.
Appointments and recall
Future scheduled appointments with their types and lengths, plus recall and continuing-care due dates so the hygiene schedule survives.
Clinical notes and perio charts
Progress notes carried as structured text against the right patient, visit, and provider. Perio exams carried as measurement data where Eaglesoft holds them as measurement data.
Images and attachments
Radiographs and intraoral images generally live in a separate imaging application rather than in Eaglesoft itself. Whether they move, get bridged, or stay in place is settled in the assessment.
Written down before you spend anything, because the alternative is finding out in week six. This list is specific to Eaglesoft to Open Dental; the assessment turns it into your list, with record counts attached.
— Perio charts migrate as measurement data only where the source held them as measurement data. Where an exam exists only as a rendered image or as text inside a note, it arrives as exactly that. This is the single most common surprise in dental migrations, and the assessment answers it for your specific database before you commit.
— Rich formatting inside clinical notes. Clinical content moves; bold, tables, and embedded layout generally do not survive intact.
— Eaglesoft-specific customizations — custom note templates, practice-specific macros, and screen configuration. These get rebuilt in Open Dental as separately scoped work.
— Scanned documents held by a separate document-management layer rather than by Eaglesoft. They are usually recoverable, but as a distinct piece of work identified in the assessment.
— Insurance claim history as live, resubmittable claims. Historical claims arrive as records; claims in flight are handled by working them to completion in Eaglesoft before the switch.
— Third-party module data that never lived in Eaglesoft — imaging, patient communication platforms, payment processors. Each is its own conversation, named in the assessment rather than discovered at cutover.
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
Eaglesoft's account structure and Open Dental's guarantor model diverge in ways that quietly change who owes what. A family where the responsible party changed after a divorce, or a patient who is their own account but a dependent on someone else's insurance, is exactly where a naive map produces plausible and wrong balances. Mapped explicitly, signed off before the test load, reconciled against an aging report afterwards.
02
The same employer plan often exists dozens of times, created one patient at a time. Migrating as-is imports the mess; deduplicating changes benefit tracking. Which way you go is decided during mapping, with a duplicate report in front of you.
03
Procedures are attributed to providers who left years ago. They have to exist as inactive records on the far side or your production reporting silently changes retroactively. Inactive-provider handling is part of the mapping document.
04
Open Dental offers a conversion service and it is legitimate. For a straightforward single-location practice with clean data it may well be all you need, and I will say so. Independent migration earns its fee on multi-location groups, practices with messy or very long history, practices already carrying data from a prior conversion, and anyone who wants the reconciliation and rollback plan in writing.
01 — 02
A read-only audit of your Eaglesoft 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 Open 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 clean location typically lands in Standard Migration. Multi-location groups, practices carrying a prior conversion in their history, or engagements with imaging bridging in scope generally land in 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
On extraction, yes — Eaglesoft's SQL Server backend is more accessible than a proprietary engine, which means harder record counts earlier and generally a lower assessment cost. On interpretation it is not easier: the account-versus-patient structure is its own problem, and the clinical questions about perio and notes are identical.
Clinical completeness is determined by how your practice recorded things, not by the migration. Structured data moves as structured data; anything recorded as an image or free text moves as an image or free text. The assessment inventories which of your clinical data is which, before you spend anything on the migration.
Yes, and for at least the first year I recommend it. A read-only instance is cheap insurance and it is what makes the migration reversible. The rollback plan assumes it exists.
PHI is handled under a BAA signed before any data moves, work happens in an environment scoped for it, and test data is destroyed at the end of the engagement on a documented schedule.
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
A cloud target with a fixed importer.
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.
Eaglesoft and Open 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 Eaglesoft
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.