Good uses for AI suggestions
- Custom-field and unfamiliar-column mapping
- Practice-specific category interpretation
- Document classification and proposed matter association
- Potential duplicate identification
- Explaining records that need human attention
Migration by design
Bring your firm's history with you
Switching practice-management systems should not mean rebuilding years of matters by hand. Usus is developing an assisted import process that combines exact parsing, AI-suggested mapping, lawyer review, and reconciliation before records reach the working database.
In development · Source-specific import support will be published only after testing against representative exports.
The migration promise
AI may suggest. It must not silently rewrite history.
Identifiers, money, dates, record relationships, and original files demand exact handling. AI is most useful where the source is ambiguous: unusual columns, custom fields, inconsistent categories, and semi-structured notes.
A staged, reviewable import
Nothing enters the live system until the firm can inspect it
- 01
Preserve
Keep an untouched source export with checksums so every imported value can be traced back.
- 02
Parse
Use source-specific code for known tables, identifiers, dates, amounts, and document paths.
- 03
Interpret
Use AI to suggest mappings for ambiguous columns, custom fields, categories, and semi-structured content.
- 04
Stage
Convert records into a neutral migration package, not directly into the working database.
- 05
Review
Show proposed mappings, confidence, duplicates, exceptions, and unresolved records to the firm.
- 06
Reconcile
Compare counts, files, time, invoices, payments, and financial totals before completion.
- 07
Import
Write approved records with source identifiers, provenance, and an auditable completion report.
- 08
Reverse
Keep a failed or unsatisfactory import removable so the firm can correct and run it again.
A report, not a green checkmark
The firm should know exactly what moved
A completed migration should account for the source, including the records that still require a decision.
2,418
contacts imported
736
matters imported
18,205
documents verified
412
custom fields preserved
14
possible duplicates for review
3
unresolved records, each explained
Illustrative report only—not the result of a completed Usus migration.
Different data, different authority
Where AI helps—and where exact code remains in charge
Exact handling and reconciliation
- Trust transactions, invoices, payments, and rates
- Matter identifiers and record relationships
- Deadlines, dates, time zones, and calendar events
- Original filenames, document bytes, and checksums
- User permissions and conflict-check records
Confidential from the first step
A migration may contain the firm's entire client history
Usus is being designed to analyze migration packages locally where practical. If an external AI service is ever offered for migration, it will be optional and accompanied by clear disclosure of the provider, transmitted fields, retention, training terms, and deletion process.
The firm-provided export remains the source of truth. Usus will not scrape a competitor account or bypass the source platform's access controls.
Planned sequence
Build confidence from operational records outward
First
Firm and matter foundation
Users, contacts, organizations, matters, relationships, custom fields, notes, tasks, and calendars.
Then
Documents and templates
Files, folder relationships, metadata, document classifications, and repeatable document structures.
After validation
Financial history
Time, invoices, payments, and trust information only with exact parsing and completed reconciliation controls.
The sequence may change based on actual export formats and founders-program priorities.
Migration cohort
Help Usus test against the exports firms really receive
We are looking for firms willing to discuss source formats, custom fields, historical records, reconciliation expectations, and the questions that make a migration trustworthy.
Clio and MyCase are trademarks of their respective owners. Usus is not affiliated with or endorsed by either company.