Leaving Raven Health: your plan, the billing tail, units

Which Raven plan you are on sets the timeline

Raven’s pricing page lists three ways to buy it, and each leaves differently:

• Standalone software, priced per learner with an annual commitment. Your own biller already submits claims, so this is a standard ABA migration: clients, programs, authorizations, one parallel cycle. The commitment end date is the date to plan towards.
• Premium All-In-One, where Raven handles claims for a percentage of what is paid, month to month. You are re-establishing billing as well as moving software: a biller to engage, payer submission to re-point, and a revenue gap to prevent. Give that workstream the head start.
• Self-Billing, on custom terms, so the answer is in your own agreement.

Ask Raven for the export before you give notice

Raven does not publish documentation on exporting your data, so do not assume a format. Ask in writing, while the account is fully active, for:

• the client and guardian list, with payer details;
• every authorization, with units authorized and units delivered to date;
• the program and goal library, per learner;
• per-session data values and signed session notes;
• on Premium, a complete claims-status report covering everything Raven has submitted.

What comes back decides how much mapping follows. What our side accepts, and how it handles rows that do not fit, is set out once in how the import centre works.

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.

If Raven was billing for you

Billing goes first: biller engaged, payer submission re-pointed, and Raven told the last date of service it owns. Then the 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 from the cutover date of service onward. Open claims at cutover are the revenue at risk, which is why the claims-status report is on the list above.

Raven also lists offline-mode capture on every plan. Cold-start offline collection is not supported here, and field teams need to know that before the first Monday.

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. For the shape of what you are moving, see the authorization tracker.