The fear is the incumbent's best retention tool
Most employers who should change administrators do not, because transition sounds like risk. The incumbent knows this. "You do not want to disrupt members mid-year" is the most effective retention line in the industry, and it works because there is a grain of truth in it.
Here is the honest version: transitions do break things, the breakages are predictable, and almost all of them are sequencing problems rather than technical ones. This is what actually happens and the order that prevents most of it.
What genuinely breaks
Accumulators. Deductible and out-of-pocket progress has to move from the old administrator to the new one. If it arrives wrong, members get asked to satisfy a deductible twice, which is the single most damaging thing that can happen to a member during a transition. This is the item to obsess over.
ID cards. New cards, new payer ID, new claims address. Members carry the old card, providers bill the old address, claims land at an administrator no longer holding the plan.
Eligibility during the gap. For a short window both administrators think they may be responsible. Providers checking eligibility can get an answer from the wrong system.
In-flight prior authorizations. An authorization approved by the old administrator for a procedure scheduled after the change has to be honored. If it does not transfer, a member arrives for surgery and is told they are not authorized.
Claims in process. Claims received but not yet paid on the change date belong to someone. This is the run-out decision below.
Provider payment continuity. Providers on electronic payment with the old administrator need re-enrollment. Missed, it turns into paper checks and phone calls.
What does not break, despite the story
Your network. If you keep the same network, provider relationships do not change. The network contract is between the network and the providers.
Your stop-loss. Stop-loss follows the plan year, not the administrator, though the new administrator must pick up trigger tracking cleanly.
Your plan document. The plan is yours. A new administrator configures to it.
Member care. Nobody loses coverage in a transition. The plan continues. The question is only whether the administrative machinery keeps up.
The run-out decision
When you leave, claims incurred before the change date but received after it have to be adjudicated by someone. There are two options, and the choice has real consequences.
Run-out with the incumbent. The old administrator processes those claims for a defined window, usually three to twelve months, and charges a run-out fee. Advantage: they already have the history and accumulators. Disadvantage: you are paying an administrator you just fired to handle your claims carefully, and their incentive to do so is limited.
Run-in with the new administrator. The new administrator takes claims incurred before the change date. This requires a clean history transfer and a new administrator willing to adjudicate against the prior plan configuration. Advantage: one relationship, one set of reporting, and the incoming administrator has every incentive to get it right.
Ask both administrators what they charge for each and how they handle it. The run-out fee is often the largest single cost of switching and it is negotiable.
The sequence
The order matters more than the timeline.
Get your data first, before you sign anything. Ask the incumbent for the claims history, eligibility file, and accumulator file in standard formats, and confirm in writing what they will charge and how long it takes. Do this while you are still a client. Leverage disappears the moment you give notice.
Confirm the notice period in your services agreement. It is often 90 days and sometimes longer, and it may only permit termination at plan year end. Read this before planning any date.
Reconcile accumulators twice. Once at file transfer, once again about two weeks before go live. Members move, plans have mid-year changes, and the file you got in month one is stale by month three. Ask the new administrator to reconcile against a fresh pull. This is the step most often skipped, and it is the one that produces the double-deductible problem.
Load and test with real claims before go live. The new administrator should adjudicate a sample of your actual historical claims against the new configuration and show you the results line by line. Any difference from what was actually paid is either a configuration error or a mispayment by the incumbent. Both are worth knowing before members are affected.
Transfer in-flight authorizations explicitly. Ask for the list of open authorizations with dates of service after the change. Confirm each one is loaded. This is a small list and a large member impact.
Mail ID cards early, and tell members what changes. The member communication does not need to be elaborate. It needs to say what changes, on what date, what to do with the old card, and who to call.
Keep a bridge on eligibility. For the first two weeks, someone should be watching eligibility responses for members the new system does not recognize. Errors here are quiet and members feel them at the pharmacy counter.
Timing
Plan year boundaries are the cleanest, because accumulators reset and the run-out question gets simpler. Mid-year is possible and sometimes correct, particularly when the incumbent relationship has genuinely failed, but it means transferring partial accumulators, which is the hardest part of the whole exercise.
If you are evaluating for a January start, begin in summer. That is not a sales timeline, it is the notice period plus the data transfer plus a reconciliation cycle.
Questions to ask the incoming administrator
- What is your accumulator reconciliation process, and how many times do you run it?
- Will you adjudicate a sample of our historical claims against the new configuration before go live?
- How do you handle in-flight prior authorizations?
- Do you take run-in claims, and at what cost?
- What does the first two weeks of eligibility monitoring look like?
An administrator that has done this well can answer all five without preparation. One that treats implementation as a project plan handed to the client will describe a timeline instead.
The part nobody says out loud
Most of what goes wrong in a TPA transition goes wrong because the incoming administrator treated data migration as a formality and the outgoing one had no reason to help. Both problems are visible in advance, and both are addressable by doing the data work before the notice letter goes out.
The transition risk is real. It is also almost entirely front-loaded into decisions you control.
If you are weighing a change, send us your recent claims and we will run them through the engine before anything moves, so the comparison happens on your data rather than in a projection. Nothing connects to your systems and you keep the report either way.