Of all the line items in an EMR proposal, data conversion is the one most likely to be quoted vaguely, priced as an allowance, and revised upward once the project is underway. Vendors are not necessarily being evasive; the cost depends on the source system, the volume and quality of the data, and how much of it the practice wants moved, and none of that is known at the sales stage. But buyers can still compare quotes rigorously if they know what to ask. This guide explains how conversion is priced, what is typically included, and how to put competing quotes on equal footing.
Why migration pricing is so opaque
Data conversion is a service, not a product. The vendor or its conversion partner has to obtain an export from the legacy system, map the source fields to the new system's data model, transform and load the data, validate the result, and repeat the process at least once more on a fresh export close to go-live. Each of those steps takes a different amount of effort depending on how the old system stores data and how clean it is. A practice that has been on a well-supported system with a documented export format is a small project; a practice on a discontinued product with no vendor support and free-text allergy fields is a large one.
Vendors handle this uncertainty in one of two ways. Some quote a fixed price for a defined scope and charge for anything outside it. Others quote an estimate or an allowance and bill for actual hours. Both approaches are legitimate; the problem arises when buyers compare a fixed-scope quote to an hourly estimate as if they were the same thing.
The pricing models vendors use
| Model | How it works | Risk to buyer |
|---|---|---|
| Fixed fee, defined scope | One price for a listed set of data elements from a named source system | Anything outside the list is a change order; scope definitions can be narrow |
| Per-provider or per-chart | Price scales with the number of clinicians or active patient records | Definition of "active" matters; inactive charts may be excluded or charged separately |
| Time and materials | Hourly rate against an estimate | Estimate is not a cap; poor source data drives hours up |
| Tiered packages | Basic, standard, and full conversion at set prices | Basic often means demographics only; clinical data is in the higher tiers |
| Third-party conversion partner | Vendor refers you to a specialist who quotes separately | Two contracts, two points of accountability; coordination is on the buyer |
Some vendors also waive or discount conversion as a sales incentive, particularly when they have a pre-built converter for the practice's current system. That is a real benefit, but the waiver usually covers the standard scope only, so the buyer should still get the scope in writing.
What a standard conversion usually includes and excludes
There is no industry-wide definition of a standard conversion, but most vendor packages cluster around a similar core.
- Almost always included: patient demographics, insurance and guarantor information, appointment schedules for future dates, and a problem list, medication list, and allergy list for active patients.
- Often included with limits: immunization history, a defined number of years of lab results, and clinical notes as PDF or text attachments rather than structured data.
- Frequently excluded or priced separately: scanned documents and images, historical claims and payment data, custom templates and order sets, provider preference lists, recall and reminder settings, and any data from a second legacy system.
- Almost never included: conversion of discrete clinical data into the new system's structured fields beyond the core lists, cleanup of duplicate patients, or data from systems the practice retired years ago.
Ask specifically: "Will my clinical notes come over as searchable structured data or as PDF attachments?" The answer changes both the price and how usable the historical record will be.
What drives the price up
Understanding the cost drivers helps a buyer predict which quotes will hold and which will grow. The source system is the largest factor: a vendor with an existing converter for it can move data cheaply, while an unfamiliar or unsupported source requires custom mapping. Data volume matters less than data quality; a million clean records cost less to convert than fifty thousand messy ones. Multiple source systems, such as a separate practice management and EMR, roughly double the work. Scanned documents are priced by count or by gigabyte, and a practice that has been scanning for a decade may have more of them than it expects.
The number of conversion passes also matters. A responsible migration includes at least one test load for validation and one final load at cutover; some projects need three or four. Quotes that include only a single load are cheaper on paper and riskier in practice. Finally, the legacy vendor's cooperation is a hidden driver: some charge for a full export, some provide it slowly, and some provide only a proprietary format that requires extra work to parse. That cost often appears on the legacy vendor's final invoice rather than the new vendor's quote, but it is part of the migration all the same.
How to compare quotes on equal terms
To compare vendors fairly, give each one the same information and ask each the same questions. Provide the name and version of the current system, the approximate number of active and inactive patients, the number of providers, the years of history the practice wants moved, and the approximate volume of scanned documents. Then ask each vendor to respond to a fixed list.
- Which data elements are included in the quoted price, listed explicitly?
- Which elements are available at additional cost, and at what price?
- How many test loads and validation cycles are included?
- Is the price fixed for the stated scope, or an estimate? If an estimate, what is the cap?
- Have you converted from our current system before? How many times in the past two years?
- Who performs the work: your staff, a subsidiary, or a third party? Who is accountable for defects?
- What is the practice's responsibility, in hours, for mapping decisions and validation?
- What happens to data that fails to load? Is it reported, retried, or dropped?
Lay the answers side by side. A quote that looks 40 percent cheaper often turns out to include one load, exclude scanned documents, and treat clinical notes as out of scope. Adjusting each quote to the same scope usually narrows the gap considerably and sometimes reverses the ranking.
Contract language that protects you
Once a vendor is chosen, the conversion scope from the sales process should be attached to the contract as a schedule, not left in an email. The schedule should list the included data elements, the number of loads, the acceptance criteria for a successful conversion, and the price for common additions. It should state that the vendor will provide a validation report showing record counts by data type from source and target, and that final payment for conversion is due on the practice's acceptance rather than on the vendor's completion.
Two further clauses are worth negotiating. First, a cap on time-and-materials conversion charges, with any overage requiring written approval before the work proceeds. Second, an obligation on the new vendor to export the practice's data in a documented, non-proprietary format at the end of the relationship, at a stated price. The practice that is careful about getting data into a system should be equally careful about the terms for getting it back out, because the next migration is a matter of when, not whether.
Common questions
What does a basic EMR data conversion usually include?
Typically patient demographics, insurance information, future appointments, and the active problem, medication, and allergy lists. Clinical notes, scanned documents, and historical billing data are often limited, excluded, or priced separately.
Should clinical notes be converted as structured data or as PDF attachments?
Structured conversion is more useful but far more expensive and often impractical across different systems. Most practices accept notes as attachments and convert only the core clinical lists as discrete data. Ask the vendor which it is quoting.
How many test loads should a migration include?
At least one test load for validation and one final load at cutover. Complex projects often need two or three test loads. Quotes that include a single load carry more risk.
Can we negotiate a cap on conversion fees?
Yes. For time-and-materials quotes, ask for a not-to-exceed amount with written approval required for overages, and tie final conversion payment to the practice's acceptance of a validation report.