When you’re rolling up practices, the technology environment you inherit is either a clean handoff or a hidden liability. Here’s how to know which one you’re buying, before the deal closes.
Key takeaways
- When a group acquires a practice, the technology team is one of the first real touchpoints with that new practice, so a rough transition costs you more than money. It costs you the relationship.
- Due diligence on the target’s IT environment tells you whether you’re inheriting a clean setup or a dumpster fire, while you can still price it in.
- A good onboarding process becomes a reusable playbook, so the second acquisition is smoother than the first, and the tenth is smoother than the second.
- The knowledge that makes a practice run is often locked in one or two people’s heads. Capturing it before they leave is the difference between a smooth handoff and a scramble.
If your group is growing by acquisition, here’s something worth sitting with. The technology team is usually one of the first real touchpoints a practice has with you after the deal.
Before anyone’s felt the culture or met the leadership, they’ve felt whether their email still works and whether they can see patients on day one. So the transition isn’t a back-office task you get to later.
A good one drives referrals and makes the next practice easier to bring on. A bad one does the opposite, and it does it loudly. Let me walk through how we think about it, because it’s less complicated than it sounds and more important than it looks.
Look before you sign: the dumpster-fire check
The first thing is due diligence, and I mean before the transaction, not after. You’ve got a practice you’re in discussions with, and you want to know whether you’re about to inherit a dumpster-fire IT environment before you commit to it.
That’s a real question, and it has a real answer. We get engaged in exactly those efforts, going in and looking at a target’s environment, working alongside the leadership team to find where the technology gaps are, so you walk into the deal knowing what you’re getting.
The value isn’t the report itself. It’s that you can price the risk, plan the fix, and set expectations while you can still fold it into the deal, instead of discovering the mess the week after close, when it’s already yours.
Capture the knowledge before it walks out the door
Here’s a practical one people underestimate. A lot of what keeps a practice running is tribal knowledge, sitting in one or two people’s heads, and that knowledge gets lost over time, especially through a transition, when people move on.
So part of a real onboarding is a deliberate phase for capturing it. We spend time with whoever runs technology at the practice today, whether that’s an in-house person or the incumbent provider, shadowing them, documenting how things work, and transferring that knowledge to the support team before it disappears.
You’re not just taking over the systems. You’re taking over how they were run, which is the part that isn’t written down anywhere and is the part that bites you at 8 a.m. on the first Monday.
Build the playbook once, use it every time
Now the part that compounds, and this is where the real value is. The tools and the process you use to bring one practice on become a playbook, and it stays with you. The single view of the environment, the project management, the onboarding steps, the templates for a common type of practice, all of it gets reused.
So the second acquisition is smoother than the first, because you’re not starting over. We build these programs specifically because most of the groups we work with are in a growth phase, actively adding practices, and the whole point is that onboarding gets faster and lower-risk each time instead of being reinvented deal by deal.
Put it this way: if you’re planning to grow by ten practices, you don’t want ten first-times. You want one playbook, run ten times, getting sharper each round.
Different starting points, one operating model
One more thing that matters when you’re rolling up, because it trips people up more than anything else. Every practice you acquire is starting from a different place. Different systems, different workflows, different levels of maturity.
So the mistake is forcing a big-bang change on all of them at once, which just manufactures risk you didn’t need to take on. The approach that works is the opposite.
You set a common operating model, a baseline of governance, security standards, and support, and you bring each practice onto it when that practice is ready, one at a time, project-managed, so continuity holds and nobody’s patient care gets disrupted in the process. Standardized where it counts, flexible where it has to be.
Why this is really about the next deal
None of this is exotic. It’s discipline applied to a thing most groups treat as an afterthought. Get the technical due diligence right and you know what you’re buying. Capture the knowledge and you don’t lose the plot when people leave. Build the playbook and every future deal gets easier.
And underneath all of it is the relationship, because the practice you onboard well is the practice that refers you the next one. In a roll-up, a clean transition isn’t a cost of doing the deal. It’s how you earn the deal after it.
One view across every practice you own
Here’s a problem that shows up the moment you own more than one practice: you can’t see them. Each one has its own systems, its own reporting, and its own way of doing things, so from the top you’re stitching a picture together out of a dozen sources that don’t agree with each other. Part of getting a group onto one operating model is getting it onto one view.
A single pane of glass across the whole environment, so leadership can see what’s happening across every location instead of chasing each practice for its own numbers. You bring a practice on, it lands on the shared view, and for the first time the group can be run like one organization instead of a holding company for a stack of separate ones.
How the transition happens on the ground
One worry comes up in every acquisition, and it’s about people, not technology. The practice you’re buying has folks who keep the lights on, and they’re wondering what happens to them the day the deal closes.
A transition doesn’t have to mean tearing that out. Often the right move is to bring the existing technology staff onto the team, rebadge them, and ramp up local support, rather than pretending you can run a practice entirely from somewhere far away. That does two things at once: it keeps the institutional knowledge we just talked about from walking out the door, and it means there are hands nearby when a location needs them. A standardized operating model and a local presence aren’t in tension. The good transitions have both.
Through all of it, the number that matters most is zero, as in zero days a practice can’t see patients. The whole reason for the discipline, the diligence, the knowledge capture, the playbook, the phased rollout, is that a provider should be able to walk in the morning after a milestone and do the job exactly like the morning before.
A transition the patients never notice is the only kind worth running, and in a roll-up it’s also the one that makes the next practice want to join you.
Questions we get about this
We usually sort out IT after the deal closes. What’s the risk in that?
By then you’ve lost your negotiating room and your visibility. Problems you could have priced in become problems you simply absorb. Due diligence before close is what turns a surprise into a line item you saw coming and planned for.
How do we keep from starting over on every acquisition?
Treat the first onboarding as a playbook, not a one-off. The tooling and process that brought on practice one should carry to practice two, so each deal gets faster instead of reinventing the wheel. That’s the whole reason to build it deliberately the first time.
What usually goes wrong in a practice IT transition?
Two things, most often. A big-bang cutover that ignores how different each practice really is, and tribal knowledge walking out the door before anyone wrote it down. Both are avoidable with a phased model and a real knowledge-transfer step, and both are expensive when you skip them.
Focus is a healthcare-exclusive Unified Partner across Managed IT, Managed Security, and Managed Data, with 16+ years in healthcare, 2,000+ EHR conversions across 1,500+ organizations, and HITRUST CSF certification. If you’re growing by acquisition and IT keeps being the part you handle after the deal, that’s a conversation we have often.
