September only: every new portal setup includes a free website build — or a full polish of your current site — at no extra cost. See what's included
ClientCentric

Guides

How to switch care agency software.

Agencies stay on systems they've outgrown because the move feels riskier than the pain. It doesn't have to be — if you demand the right guarantees, in writing, before anything moves.

The short version: export everything you can from the current system (CSV or Excel is fine); demand a written, plain-language migration plan that accounts for every single record; refuse any process whose failure mode is silence; test the real workflows — assign, clock, document, approve — before cutover; and do not go live without a rollback guarantee that is enforced by the software, not promised in an email.

Step one: get your data out, imperfectly

Do not wait for a perfect export. Spreadsheets with messy columns, duplicate IDs, and typo’d dates are normal — a competent migration process expects them, flags each problem visibly, and asks you for decisions rather than guessing. If a vendor asks you to clean your data first, ask what exactly their process cannot handle, and why.

  • Clients, staff, services, and assignments are the core four — start there
  • Schedules and open visits next; historical documentation last (it should import as locked history)
  • Keep the originals: a trustworthy process stores what you sent, unmodified, versioned

Step two: demand accounting, not vibes

The single most important artifact of a migration is the reconciliation: for every record you sent — imported, matched to an existing record, merged, preserved in archive, or flagged for a decision. The arithmetic must balance. If the vendor cannot produce that statement, records can vanish silently, and the day you discover it will be an audit.

Step three: cut over with a way back

A rollback guarantee must mean: the migration’s writes — exactly those — can be removed, restoring the pre-migration state, within a stated window. “We’ll restore from backup” is not the same promise: backups roll back everything, including the work your team did after go-live. Ask precisely which one is on offer.

In ClientCentric, this whole guide is implemented as product: quarantined intake, visible validation, a confidence report bound to your written approval, an import that resumes without duplicating if interrupted, downloadable reconciliation proof, and a scoped rollback window. That is the standard we think you should hold anyone to — including us.

See the destination platform in the demoBook a switch walkthroughNo signup. Fictional data. Everything resets on refresh.

Keep reading

Written and maintained by the ClientCentric team from the working product. Last reviewed .