Switching
Switch care agency software without rebuilding everything.
The move itself is built into the product. You send exports or spreadsheets from whatever you use today; the platform sorts, checks, and moves every record — and nothing goes live until you have approved a plain-language plan.
Switching01
Switching is the easy part.
Moving years of records is the reason agencies stay on tools they have outgrown. So we built the move itself into the product: you do three small things, the platform does the heavy lifting, and nothing goes live until you have approved it.
You · a short call
Tell us about your agency
Name, state, program. We set up your workspace while we talk.
You · drag & drop
Send us your files
Spreadsheets and exports from whatever you use today. That is your whole job.
Us · automatic
We sort and check everything
Every column identified, every issue found and flagged — before anything moves.
You · one approval
Review one report
Plain language: what moves, what needs a decision. Nothing proceeds without your yes.
Us · with a safety net
You are moved in
Live on ClientCentric, with a rollback window — and every record accounted for.
Migration confidence report
Awaiting your approval| Records | Total | Moving over | With notes |
|---|---|---|---|
| Staff | 24 | 24 | 0 |
| Clients | 61 | 61 | 1 |
| Services | 12 | 12 | 0 |
| Schedules | 215 | 215 | 2 |
312 records — 312 accounted for. Nothing dropped, nothing guessed.
The report an owner approves before anything moves — from the product, not a brochure.
Any starting point
Spreadsheets, CSV or Excel exports — from your current system or a filing cabinet's worth of both.
Nothing moves without your approval
You see the full plan first and approve it in writing. The approval is bound to that exact plan — change anything, and it must be approved again.
Every record accounted for
Imported, merged, archived, or flagged for a decision — each record ends in exactly one documented place. Never silently dropped.
A rollback window after go-live
If anything is wrong in your first weeks, we put everything back exactly as it was — guaranteed by design, not by promise.
What you can send
Spreadsheets and system exports — CSV, TSV, and Excel workbooks, plus PDFs, scans, and photos for the document record. It does not matter whether your data lives in one legacy system, four spreadsheets, or a mix of both; every file is checked the moment it arrives, and a file that is not what it claims to be is refused with the reason recorded.
- CSV, TSV, and Excel exports from any current system
- Every file scanned in quarantine before anything reads it
- Re-uploads become new versions — nothing is overwritten or lost
- Historical documentation imports as locked history, not editable notes
Nothing moves without your approval
After your files are sorted and checked, you get one report in plain language: what moves, what merges, what needs a decision first. Your approval is recorded and bound to that exact plan — if anything about the plan changes afterward, the approval is void and the new plan comes back to you. Every record you gave us ends in exactly one documented outcome: imported, matched to an existing record, merged, preserved in archive, or flagged for a decision. Never silently dropped.
After go-live there is a rollback window. Rolling back removes exactly what the migration created and nothing else — guaranteed by how the import is built, not by a promise.
Keep reading
- How the data migration worksThe pipeline in detail: quarantine, mapping, validation, dry run, approval, import, reconciliation.
- Data migration as a featureWhy the migration engine is part of the product, not a services project.
- Guide: how to switch care agency softwareA practical plan for changing systems without losing your history.
- Security and access controlsAssignment-based access, individual accounts, MFA, and append-only audit history.
- The full platformNineteen modules, one system of record.
Written and maintained by the ClientCentric team from the working product. Last reviewed . Describes the migration workflow of the current product; screenshots come from the working demo with fictional data.