Upload everything you have.
Send CSVs, Excel files, PDFs, scanned documents, photos, ZIPs, export folders, and document libraries. The source material does not need to be cleaned or reorganized before the migration starts.
Butler Solutions migration
Bring your data. Our AI does the work.
Migration is part of switching to Butler, not a separate project you manage on top of it. Founding customers get migration free. Standard migrations are priced for what they actually take: flat fees for known scope, custom for genuinely complex work.
Butler migration program.
Butler migration is the switching program for firms, agencies, and investigation teams moving into Legal Core, Bail Core, or PI Core. Migration covers client and customer records, matters or cases, defendant and indemnitor records, calendars, tasks, notes, document libraries, payment and billing context, trust-account references, forms, and configuration details when the source data supports them. Butler's migration team handles the work; customers do not have to clean every spreadsheet, rename every file, or rebuild the new system alone. Founding customers in the first 100 spots per vertical receive migration free as part of the founding cohort program. Standard cloud-to-cloud migrations are $499 for known scope up to 5,000 records. Complex migrations are $1,499 for legacy systems, multiple sources, or large document libraries. Enterprise migration is quoted for genuinely unusual scope. The AI migration platform launches in late Q3 or Q4 2026. Before that launch, Butler uses manual migration with a 60-minute kickoff call and the same review-and-approval framework. Paid migration fees are credited back as platform credit after 6 months of paid subscription.
Process
Four steps from source data to Butler instance.
The framework is intentionally simple: gather the source material, process it into a Butler-ready shape, review uncertain items with the customer, then cut over when the imported instance is ready.
Our AI processes.
The AI migration platform is designed for multi-format ingestion, schema inference, entity resolution, and document classification. Before launch, Butler follows the same framework with manual processing by the migration team.
You review and approve.
Butler proposes field mappings and record groupings, then surfaces uncertain items in review batches. The customer confirms what becomes part of the Butler instance before go-live.
You go live.
The Butler instance is prepared with imported records, organized documents, review history, and audit trails. The customer moves from review mode to operational mode with the migration team available during cutover.
Timing note
AI migration platform launches in late Q3 or Q4 2026.
Migrations completed before launch use the same four-step framework with manual processing and a 60-minute kickoff call with the migration team. The AI platform automates the heavy lifting; the framework stays the same.
AI migration platform
What the platform is being built to do.
These capabilities describe the AI migration platform scheduled for late Q3 or Q4 2026. Before that launch, Butler uses manual migration with the same review and approval discipline.
Multi-format ingestion
CSVs, Excel files, PDFs, scanned documents, photos, ZIP archives, export folders, and document libraries are accepted as source material.
Schema inference
The platform is being built to infer source data structure so Butler can map fields without forcing customers to pre-normalize every file.
Entity resolution
Names, IDs, contact records, and case references can be matched across exports even when different systems represent the same person or matter differently.
Document classification
Uploaded documents are categorized into Butler's operating categories so files land near the records, workflows, and review points that need them.
Mapping proposals
Source fields map into Butler fields with ambiguous mappings held for human review instead of silently importing uncertain data.
Source systems
Built for the systems firms are actually leaving.
Butler supports migration planning from legal, bail, investigation, and open-format sources. What matters first is identifying the source systems, export formats, and document libraries the customer is bringing into Butler.
Legal practice systems
- Clio
- MyCase
- PracticePanther
- Smokeball
- CASEpeer
- Filevine
- Rocket Matter
- CosmoLex
- AbacusLaw
- PCLaw
- Tabs3
- Time Matters
Bail agency systems
- Captira
- BailBooks
- eBail
- Simply Bail
Investigation systems
- CROSStrax
- Trackops
- CaseFleet
Open formats
- CSV
- Excel
- Google Sheets
- PDFs
- scanned documents
- photos
- ZIPs
- document folders
Pricing
Migration pricing is tied to the work.
Founding customers receive free migration as part of the existing founding cohort program. Paid migration fees are credited back as platform credit after 6 months of paid subscription.
Legal Core
94founding spots remaining
Criminal defense firms moving matters, documents, calendars, billing context, and trust-account references.
Bail Core
100founding spots remaining
Bail agencies moving defendants, indemnitors, court dates, payment context, forms, and field records.
PI Core
99founding spots remaining
Investigation firms moving cases, evidence indexes, surveillance notes, documents, and attorney-client records.
Founding customers
FreeOne founding cohort claim covers both the 25% software discount and free migration. Founding migration does not create a separate counter.
Standard migration
$499For typical switching scenarios from supported source systems where the record shape is known and the document volume is manageable.
Complex migration
$1,499For moves involving multiple systems, unusual exports, large document corpora, or source data that needs more mapping and review.
Enterprise
CustomFor genuinely large deployments, non-standard retention requirements, unusual source systems, or migration plans that need custom sequencing.
Platform credit
Migration fees come back after 6 months paid.
Customers who pay a standard, complex, or enterprise migration fee receive that fee back as Butler platform credit after 6 months of paid subscription. The credit does not apply to pass-through services, background checks, or third-party charges.
Timeline
Most migrations are measured in days or weeks, not quarters.
Timelines depend on source-system access, export quality, record volume, document volume, and review speed. The expectations below are planning ranges, not guarantees.
Cloud-to-cloud
Most cloud-to-cloud migrations complete within 2-5 business days after source exports and kickoff details are received.
On-premise legacy systems
Legacy and on-premise migrations usually take 1-3 weeks because exports, documents, and source-system constraints vary more.
Document migration
Document migration runs in parallel with record mapping and review. It does not automatically extend the whole migration timeline.
FAQ
Migration questions.
What is included in a Butler migration?
Migration can include contacts, client records, matters or cases, defendant and indemnitor records, calendars, tasks, notes, documents, forms, payment context, billing references, and configuration details. The exact import plan depends on the source system, export quality, and which Butler product the customer is adopting.
Who handles the migration work?
Butler's migration team handles the migration plan, source review, field mapping, import preparation, and review batches. Customers provide source exports, confirm priorities, answer ambiguous mapping questions, and approve the final import. The customer is not expected to rebuild the system alone.
How long does migration usually take?
Most cloud-to-cloud migrations complete within 2-5 business days once source exports are available. Legacy, on-premise, multi-source, or large document migrations usually take 1-3 weeks. These are expectations, not guarantees, because source-system access and export quality can change the timeline.
What customer involvement is required?
Customers participate in a kickoff call, provide exports or access instructions, identify must-preserve data, and review mapping batches. Butler handles the operating work, but customer review matters because legal, bail, and investigation data often contains context that software cannot infer safely without approval.
How does Butler verify data integrity?
Butler reviews record counts, field mappings, sample records, document associations, and uncertain imports before go-live. Customers approve review batches so the final instance reflects the intended operating structure. Ambiguous records are surfaced for review rather than silently forced into the wrong category.
What happens to data in the old system?
Butler imports data into the Butler environment but does not delete the customer's old vendor account or source records. Customers control old-system retention and cancellation. Temporary migration files used by Butler are handled according to the agreed migration plan and removed from staging after completion.
Can Butler migrate document libraries?
Yes. Butler can migrate document folders, PDFs, scans, photos, ZIPs, and related file libraries when the customer can export or provide them. Document migration runs alongside record migration so files can be associated with the correct matter, defendant, case, or investigation record during review.
Can Butler handle custom data shapes?
Yes, within practical limits. Custom fields, unusual labels, inconsistent export structures, and source-system workarounds are common migration issues. Butler maps what can be mapped cleanly, flags uncertain items for review, and quotes custom work when the source data requires unusual handling.
What do founding customers pay for migration?
Founding customers pay no migration fee. The first 100 customers per vertical receive free migration as part of the founding cohort program. The same founding claim also locks in the 25% software discount for 2 years, so no separate migration counter or claim is needed.
How do the $499 and $1,499 migration tiers work?
The $499 standard tier covers cloud-to-cloud migrations with known scope up to 5,000 records. The $1,499 complex tier covers legacy systems, multiple sources, large document libraries, or unusual data shapes. Enterprise migration is quoted when the scope genuinely does not fit those tiers.
How does the migration fee credit work?
Paid migration fees are credited back as Butler platform credit after 6 months of paid subscription. The credit can be applied inside the Butler platform relationship, but it does not change pass-through costs, third-party charges, background checks, payment processing, or separately approved custom work.
When does the AI migration platform launch?
The AI migration platform is scheduled for late Q3 or Q4 2026. Migrations completed before launch use manual processing with the same four-step framework and a 60-minute kickoff call. After launch, the platform automates more ingestion, mapping, classification, and review preparation.
Can Butler combine data from multiple systems?
Yes. Multi-source migration is part of the complex tier or enterprise scope depending on volume and structure. Butler can combine exports from practice management systems, spreadsheets, document folders, and older tools, then surface duplicate records or uncertain matches for review before import.
Can migration happen in phases?
Yes. Some customers keep the old system active during review while Butler prepares the new instance. Phased migration can reduce cutover risk when there are active hearings, court dates, field operations, or document deadlines that should not be disrupted during the switch.
What if something goes wrong during migration?
Butler uses review batches, import checks, and source exports so problems can be identified before go-live. If an import needs correction, Butler adjusts the mapping or import plan before operational use. The old system remains under customer control during the transition.
How is migration data protected?
Migration data is handled as sensitive customer data. Transfers use encrypted channels where available, staging access is limited to migration staff, and imported records are reviewed inside the Butler environment. Temporary files and migration artifacts are handled according to the agreed migration plan.
What should a customer prepare before kickoff?
Customers should gather source-system exports, user lists, document folders, current workflows, priority records, and known problem areas. Butler does not require perfect cleanup before kickoff, but a clear list of critical data and active deadlines helps the migration team sequence the work.
Migration consultation
Bring the exports. Butler will map the path.
A migration conversation starts with source systems, record volume, document volume, and the vertical product you are moving into.