How Do We Work Down Legacy AR in the Old System After Switching EMRs Without Losing It All?
What Actually Protects Your Old-System AR Through an EMR Switch
The goal is simple: every open balance in the legacy system worked to resolution before it ages out, while the new system runs clean from day one. Here is what does that, move by move.
1. Decide Before Go-Live Whether Balances Transfer or the Old System Stays Live
The single decision most transition plans skip is the one that costs the most later: do open AR balances migrate into the new system, or does the old system stay active so those claims are resolved where they were created? Transition guides tell practices to make this call explicitly, and the ones that skip it discover the answer by default when collections drop. Make the decision in writing before go-live, name who owns the legacy queue, and set the date the old system can actually be retired based on the AR being worked down, not a contract renewal.
2. Assign a Dedicated Owner to the Legacy Queue, in Parallel
Legacy AR does not get worked in spare moments, because there are none during a go-live. The staff who used to work those claims are learning the new system, and the old queue sits untouched. The move is to give the legacy runoff its own owner who works nothing but the old system until it is clear: posting the remaining payments, working the open claims, appealing the denials, and running the balances to zero while the rest of the team runs the new EMR forward. Two systems, two owners, no overlap, so neither one starves the other.
3. Keep Old-System Access Alive Until the AR Is Actually Down
The quiet killer is the cancelled license. A practice retires the old EMR on the date the contract lapses, and any claim still open that day becomes nearly impossible to work: no notes to appeal from, no way to correct and resubmit, no record to prove timely filing. Before you cancel, confirm the legacy AR is genuinely worked down, not just aged out. Negotiate read or billing access through the runoff period, export what you are allowed to keep, and archive the documentation you will need to defend any late-stage appeal. The license is cheap next to the AR it protects.
4. Track Every Legacy Claim Against Its Filing and Appeal Deadline
Open claims in a dormant system age against the same payer clocks as everything else, and nobody is watching those clocks. Build one worklist of every legacy balance with its payer, its timely-filing window, and its appeal deadline, and work it deadline-first so the short-window payers do not lose their claims while the runoff drags. A claim that ages past filing in a system nobody logs into is money that was always collectible, lost to nothing but neglect. Tracking it in one place is what turns a silent runoff into a controlled wind-down.
5. Hand the Legacy Runoff to a Dedicated Team
Practices that switch EMRs without the two-quarter collections crater do it by handing the legacy runoff to a dedicated team: remote specialists who work the old system to zero while the in-house staff learn the new one, live in 1 to 2 weeks. Your team never has to split its attention between two systems, the old AR gets worked every day instead of whenever someone remembers, and a trained backup covers every gap. Below is what it sounds like when nobody owns the old system yet, in practice teams’ own words.
Key Pain Points and Discussions by Providers
real reports from practice staff, lightly edited
“We went live in March and by summer collections were down and I could not explain it to the partners. Then it hit me: nobody had touched the old system since go-live. All that AR was just sitting there aging while we were busy learning the new one.” – practice administrator, internal medicine group
“The old EMR contract was up, so we let it lapse to save the fee. Two weeks later we needed a note to appeal a denial in that system and there was no way back in. We wrote off claims we absolutely could have collected, just because the login was gone.” – billing lead, small group practice
“My whole team was heads-down on the new system, and I could not spare a single person to work the legacy queue. So it did not get worked. For two months the old AR was nobody’s job, and it showed up as a hole in the numbers.” – office manager, primary care practice
“The migration plan had timelines for everything except finishing the old system. Data conversion, training, go-live, all mapped out. The six months of AR runoff after? Not a line item. So it became the thing that fell through.” – practice manager, internal medicine group
“The balances that hurt most were the short-window payers. By the time anyone got back into the old system to work them, they had aged past timely filing. Clean claims, real money, gone because they sat in a system nobody logged into.” – billing manager, multi-provider practice
Our Answer
Here is what we actually do. A dedicated remote specialist takes ownership of the legacy queue on day one and works the old system to zero while your team runs the new EMR: posting remaining payments, working open claims, appealing denials, and running balances down against each payer’s filing and appeal deadlines. Before any old-system license is cancelled, they confirm the AR is genuinely worked down and archive the documentation you will need to defend late-stage appeals. Our specialists are credentialed professionals, overseas-trained physicians and US-licensed nurses and pharmacists, working inside both your old and new systems, with AI drafting the first pass on each claim and a human verifying every submission. This is our revenue cycle management support paired with an AI-first workflow, in one paragraph.
Why This Keeps Happening
If the money was always collectible, why does it disappear after an EMR switch? Because a migration is planned around go-live, and go-live is the finish line everyone can see. The old system’s runoff is the part after the ribbon is cut, and it does not get a project plan. Industry guidance on EHR transitions is explicit that revenue cycle teams need continued access to the legacy system to work down open AR, resolve disputes, and support appeals, and that the common approach is to leave those claims in the old system and keep processing them there. When that decision is never made on purpose, the default is that nobody works them, and aging does the collecting instead of your team.
The volume is the second half of the problem. Days in accounts receivable is the metric that quietly blows out during a transition. The Medical Group Management Association reports that better-performing practices hold days in AR around 35, while the worst-performing quartile sits above 60, and a runoff nobody works pushes an entire book of business toward that bad end. Delayed claims during and after migration increase AR days and slow reimbursement, and a legacy queue left alone is the purest version of that: a whole population of claims not aging normally but aging abandoned. Closing that gap is exactly what dedicated accounts receivable recovery is built to do.
And the cost is not evenly spread. The claims that hurt most are the short-window payers, the ones whose timely-filing limits run 90 to 180 days from the date of service. Those age out first, and a timely-filing denial is administrative, not clinical, which makes it one of the hardest denials to overturn. A clean, collectible claim that sat in a dormant system past its filing window is not a discount or a write-off you chose; it is money you earned and simply never went back for. Multiply that across two quarters of a runoff nobody owned, and the switch that was supposed to modernize your practice quietly costs you a chunk of a year’s collections.
Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:
| What you tried | What actually happened | Who ended up doing the work |
|---|---|---|
| Told the existing team to work the old system on the side | There were no spare hours during a go-live; the legacy queue sat untouched for months | Nobody, in practice |
| Migrated open balances into the new system to keep it simple | Converted balances arrived without the original notes and denials, so they could not be worked cleanly | Whoever inherited the messy import |
| Cancelled the old EMR license on the contract date to save the fee | Lost access to notes and records mid-runoff; collectible claims became write-offs | The contract calendar, not the AR |
| Gave the legacy runoff to a dedicated remote specialist | Old system worked to zero in parallel, deadlines tracked, access kept alive until the AR was actually down | Someone whose whole job it is |
The Solution
So what does “someone whose whole job it is” look like on a legacy runoff? The specialist takes the old system as their entire assignment and works it forward every day: posting the payments still landing, working the claims still open, and appealing the denials that were never touched since go-live. Your in-house team never has to divide its attention between the system they are learning and the one they are leaving, because the leaving is somebody else’s full-time job. That parallel ownership is the whole point of dedicated revenue cycle management during a transition, and it is what keeps the old AR from becoming a hole in the numbers.
Then comes the part a calendar cannot do. Before any old-system license is allowed to lapse, the specialist confirms the legacy AR is genuinely worked down, not just aged past the point of caring. They export what the contract lets you keep, archive the documentation you will need to defend a late appeal, and hold the line on cancellation until the balances are real zeros. When a short-window payer’s clock is running, the claim gets worked deadline-first, so filing windows close on collected claims instead of abandoned ones.
Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow reads each open claim, flags the filing and appeal deadline, and drafts the correction or appeal; a person confirms the claim is right and owns the submission. Every security control that protects the chart and billing data moving between your old and new systems is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving records through a transition workflow is only safe when the controls are real.
Who Actually Does This Work
Fair question: why would an outsourced team work your old system better than your own staff? Because working AR to zero is their entire day, not the thing they squeeze in while learning a new EMR. The people running your legacy runoff are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US revenue cycle and denials workflows. They know how to read a payer’s filing window, how to build an appeal from legacy notes before access disappears, and how to run a dormant book of AR down without your in-house team touching it. That is not a spare-time task handed to whoever is free; it is a specialty.
We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a legacy runoff never stalls because the one person who knew the old system is out.
And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.
Put the routine and the people together, and a specific list of things simply stops happening.
Ready to Stop Losing Legacy AR to Your EMR Switch?
How We Permanently Fix the Process
A person alone is not the fix, and neither is a bot alone. The fix is a documented runoff plan: which balances stay in the old system and which transfer, who owns the legacy queue, the exact date the old system can be retired based on the AR being down, and the filing and appeal deadline for every open claim, all written down and worked the same way every day. Before we take a single legacy claim for a new practice, we chart your open old-system AR by payer and age so we can see where the money actually sits, and we build the wind-down against that, not against a generic template.
From there the runoff becomes a living playbook rather than a decision nobody made. It records which payers still owe on the old system, which claims are near their filing window, how to appeal from legacy documentation before access lapses, and the exact date and conditions under which the old license can safely be cancelled. It is written down, kept current as balances clear, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so the old system keeps getting worked whether or not any one person is at their desk that week.
That is the difference between surviving this transition’s collections dip and fixing the process for good, and it is what a dedicated revenue cycle management partner actually buys you. A switch used to mean two quarters of unexplained cash loss and a book of AR left to age. Under this model the old system gets worked to zero in parallel, the playbook stays, the backup steps in, and the legacy runoff stops being the cost of modernizing.
The Whole Thing in Four Sentences
Legacy AR craters after an EMR switch because the migration plan budgets for go-live and not for the six-to-twelve-month runoff, nobody is assigned to the old system, and its license is often cancelled while claims are still collectible. Telling the existing team to work it on the side, migrating messy balances into the new system, or cancelling the old license on the contract date all fail the same way. The fix is to decide up front whether balances transfer or the old system stays live, assign a dedicated owner to the legacy queue in parallel, keep old-system access alive until the AR is actually down, and track every claim against its filing and appeal deadline. An internal medicine group runs exactly this model with us today, names withheld, no patient data shown.
If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.
Ready to stop losing legacy AR to your EMR switch? Try us risk free: two weeks, your real old-system AR queue, a dedicated specialist working it to zero while your team runs the new EMR, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.
One Flat Weekly Rate. 45 Hours of Coverage.
No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.
One dedicated remote specialist working your legacy AR in the old system to zero while your team runs the new EMR, single-location internal medicine practice
5+ remote specialists covering legacy runoff and new-system AR in parallel across a multi-provider group or several sites mid-transition
10+ remote specialists, multi-location group, MSO, or PE-backed platform running legacy AR wind-down across many practices switching EMRs at once
45 hours of coverage for less than others charge for 40.
Standard US full-time year: 40 hrs x 52 weeks = 2,080 hours, the federal basis for computing hourly pay per the U.S. Office of Personnel Management. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour. Typical US market rates for healthcare virtual assistants run $9.50 to $13.00 per hour for 40 hours of coverage.
Work Down Your Legacy AR This Month
You have seen the whole method. The pilot proves it on your own old-system AR, with a tracker your team can watch every day.
Start My 2-Week Free TrialRequest Information
Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.
Frequently Asked Questions
Where the Claims on This Page Come From
Sources & References
- MGMA Practice Operations and Revenue Cycle Benchmarks. Days-in-AR benchmarks for medical group practices, reporting better-performing practices near 35 days and the worst-performing quartile above 60. mgma.com
- CMS Medicare Claims Processing and Timely Filing Guidance. Federal rules on claim submission windows, including the 12-month Medicare timely-filing limit relevant to legacy claim runoff. cms.gov
- HFMA Revenue Cycle and AR Management Resources. Guidance on accounts receivable, denials, and the revenue impact of aged and abandoned claims during system transitions. hfma.org
- AMA Practice Management and Health IT Transition Resources. Physician-practice guidance on EHR transitions, billing continuity, and administrative burden during system changes. ama-assn.org
- Physicians Practice Revenue Cycle and EHR Transition Coverage. Practice-management guidance on protecting collections and working down legacy AR when switching EHR systems. physicianspractice.com