A practice management migration predictably suppresses collections for a defined window — staff relearning workflows, claims held during cutover, enrollments re-established. Planning for the dip is the difference between a bad quarter and a crisis.
Every practice management migration produces a collections dip. Vendors rarely mention it, which turns a predictable event into an alarming one.
Where the dip comes from
Enrollment. Electronic claim submission, remittance, and funds transfer are enrolled per payer per system. That takes weeks, and until it completes, claims go out slower and payments post manually.
Charge entry slows. Staff who entered charges without thinking now think about every screen. Charge lag rises for a month or two, and everything downstream inherits it.
Configuration errors surface as denials. Fee schedules, payer IDs, place-of-service defaults. Each is small and each produces a batch of denials that arrive a few weeks later — which is why the worst-looking week is usually not the go-live week.
Legacy A/R gets stranded. Old claims live in the old system. If nobody is assigned to work them there, they age while attention is on the new one.
What to do about it
- Start payer enrollment well before go-live. It is the longest pole and the most ignored.
- Keep read access to the old system, and assign someone to its A/R by name.
- Expect elevated denials in weeks three to six and staff for it.
- Hold cash reserve for roughly one payment cycle.
The honest framing
The dip is not evidence the migration failed. Its duration is what tells you something — a return to baseline within a couple of cycles is normal, and one that persists past a quarter means something is configured wrong rather than merely new.
Record the baseline first
Days in A/R, clean claim rate, charge lag and monthly collections, captured before anything changes. Without them, every disappointing month afterwards is attributed to the migration indefinitely.
That baseline is what lets you say when the new system should have settled and whether it has.
Re-establish ERA and EFT deliberately
Electronic remittance and funds transfer enrollments are tied to submitter and bank details and frequently break on a system change. The symptom is paper checks arriving and posting going manual.
Treat it as a payer-by-payer checklist rather than assuming it carried over.
Do not migrate during your busiest quarter
The dip is survivable when volume is moderate and cash reserves are adequate. Timed against a seasonal peak, the same predictable disruption becomes a genuine cash problem.
Common questions
- Why do collections drop after changing practice management systems?
- Charge entry slows while staff learn, claims are held around cutover, and payer enrollments for electronic remittance and funds transfer often have to be re-established.
- How long does the dip last?
- Commonly one to two months of suppressed submission followed by a recovery as the backlog clears. Plan cash for a quarter rather than a month.
- How do I minimize the disruption?
- Clear as much A/R as possible before cutover, avoid migrating during a seasonal peak, and keep read access to the old system for follow-up on legacy claims.
- Should I migrate open A/R?
- Usually not in full. Working legacy claims in the old system while new claims start clean is simpler than migrating partial claim histories.
- How do I tell a normal dip from a real problem?
- Record baseline metrics before the change. If clean claim rate and days in A/R have not returned to baseline within a quarter, it is not the transition any more.
Denials Piling Up?
We handle the revenue cycle end to end — coding by certified coders, claim submission, denial management and appeals, and A/R follow-up, with six reported numbers every month.