I wrote the standard for making websites AI-operable. Learn More
Migration · Practice Fusion to Tebra
Small practices moving off Practice Fusion usually hit a different wall than large ones. The volumes are modest and the clinical data is manageable. What constrains the migration is the export path available to you and what your subscription terms permit — and that is a question to answer before you give notice, not after.
The rest is the ordinary honest EHR conversation: core clinical elements carry as structured data, historical charting largely arrives as documents, and interfaces get rebuilt rather than moved.
Certified EHRs support standards-based clinical export and C-CDA is the usual mechanism — a clinical summary interchange standard rather than a full-fidelity database export. For a smaller practice the practical questions are which export facilities your plan includes, how patient-record documents come out in bulk, and how long you retain access after giving notice. The assessment establishes all three first, because on this pair they determine what is possible more than any technical consideration does.
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.
Patient demographics and identifiers
Names, dates of birth, contact details, and identifiers, with a deliberate medical record number strategy.
Insurance and coverage
Payers, plans, subscriber relationships, and active coverage so eligibility and billing work from day one.
Problem list, medications, and allergies
The core clinical safety objects as discrete coded data, validated as their own step with their own sign-off.
Immunizations
Immunization history with dates and products — worth particular attention for practices reporting to a state registry.
Results
Laboratory and diagnostic results, discrete where held discretely and as documents where not.
Encounter notes and documents
Historical notes and scanned documents attached to the correct patient and encounter, predominantly in document form for historical depth.
Appointments
Future scheduled appointments with types and providers.
Written down before you spend anything, because the alternative is finding out in week six. This list is specific to Practice Fusion to Tebra; the assessment turns it into your list, with record counts attached.
— Whatever your subscription terms do not permit you to export. This is the defining constraint on this pair and it is contractual rather than technical. Establish it before giving notice — it is the single most consequential fact about your migration.
— Full discrete fidelity for historical charting. Core clinical elements carry discretely; the long tail arrives as documents. Quantified per object in the assessment.
— Custom templates and any practice-specific charting configuration. Rebuilt in the destination.
— Interfaces: lab, e-prescribing, and immunization registry. Re-established rather than migrated, each with its own lead time, and e-prescribing involves provider enrollment that gates day-one prescribing.
— Accounts receivable as a working AR, if you bill through the source. A runout with the source retained read-only is the standard approach.
— Source internal record IDs. The destination issues its own; anything keyed externally needs the mapping table.
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
This is the whole ballgame on this pair and it is the mistake that cannot be undone. Once notice is given, the clock on your access is running and your negotiating position is gone. Establish what you can export, in what format, and for how long — first.
02
For a small practice, the structured clinical data is modest and quick. Pulling every patient's scanned documents and historical notes out in bulk is where the time goes, and it is bounded by the export facilities available rather than by effort. Start it early.
03
You are obliged to be able to produce records for years after cutover, and cancelling the source does not change that. A complete retained archive is a requirement rather than a nicety, and it belongs in the plan and the budget from the start.
04
If you report immunizations to a state registry, that connection is rebuilt on the destination side and it has its own enrollment timeline. Historical immunization data migrates; the reporting channel does not.
01 — 02
A read-only audit of your Practice Fusion 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 Tebra 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 small single-provider practice with intact export access lands in Standard Migration. Multi-provider practices, large document archives, or degraded export access push it 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
Establish exactly what your subscription permits you to export, in what format, and how long access continues after notice. Then get the extraction done — completely — before the clock becomes a problem. This ordering is the difference between an inconvenience and a permanent loss.
Core clinical elements — problems, medications, allergies, immunizations, results — carry discretely where recorded discretely. Historical notes and scanned material arrive as documents. The assessment quantifies it for your practice, per object, before you commit.
Yes. Retention obligations run for years and are unaffected by cancelling a subscription. A complete retained archive is part of the plan and part of the budget, not an optional extra.
BAA signed before any data moves. Work happens in an environment scoped for PHI, access is limited to what the engagement requires, and test data is destroyed at the end on a documented schedule you receive in writing.
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.
Complex
Discrete data versus a PDF of your chart.
Complex
Which Allscripts product you are on.
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.
Practice Fusion and Tebra 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 Practice Fusion
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.