How to switch from Raven Health and keep billing continuous

Which kind of Raven customer you are

If Raven was software only and your own biller already submits claims, this is a standard ABA migration: clients, programs, authorizations, one parallel cycle. If Raven’s managed billing service handled your claims, you are also re-establishing billing operations — a biller to engage, payer routing to re-point, and a revenue gap to prevent. Split the workstreams and give the billing one the head start.

Authorizations are the thing to time this around

An ABA migration has one genuinely dangerous moment, and it is not the data transfer. It is the seam where authorized units are being drawn down in one system and delivered in another.

Get the authorization pools out first, with their remaining balances as at a specific date, and reconcile that date against your session records rather than trusting either number alone. An authorization that arrives with a stale balance looks correct on screen and produces an over-delivery nobody notices until a denial arrives weeks later.

Where possible, cut over at an authorization boundary rather than mid-period. Where that is not possible — and for most agencies with rolling authorizations it is not — pick a hard cutover date, deliver nothing against the old system after it, and reconcile the balances once rather than continuously.

The mechanics of the import itself — the record types, the dry run, what arrives as documents — are the same for every source system and are covered in migrating practice management software.

What maps, and what does not

Maps as structured data: clients, guardians and payer records; authorizations entered with true remaining balances reconciled against payer statements; program and goal libraries mapped by your clinical leads; and per-session data values, so graphs re-render from numbers.

Arrives as documents: signed session notes and historical reports, per client.

Stays behind: claims submitted by Raven’s billing service and their remittance records — request a complete claims-status report on exit, because open claims at cutover are the revenue at risk — and Raven’s offline capture capability itself. Cold-start offline collection is not supported here, and field teams need to know that before the first Monday.

Cutover order

Billing first: biller engaged, payer submission re-pointed, Raven’s team told the last date of service they own. Then the standard ABA sequence — library freeze, import, clinical-lead verification, authorization reconciliation, Monday. Raven’s billing tail runs until its last claim resolves, alongside your biller handling everything after the cutover date of service.

The Raven Health comparison covers the pricing model difference in detail, and ABA billing software covers what a delivered session turns into once you are here. Authorizations are the thing to guard during any ABA migration — see the authorization tracker for the shape of what you are moving.