Migrate your Thomson Reuters Case Center data
Cloud-based digital evidence management platform for courts, administrative agencies, and law firms. It creates automatically paginated, searchable case files from documents and multimedia for in-person, virtual, and hybrid hearings.
In its favor
Why people choose Thomson Reuters Case Center
The signal that keeps Thomson Reuters Case Center on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Court-mandated adoption — multiple US states (17 and growing per Thomson Reuters) and UK/Commonwealth jurisdictions specify Case Center for digital evidence management, so opposing counsel must use it whether they would have chosen to or not.
Single source of truth for evidence with automatic indexing and pagination eliminates the manual work of paper bundles, PDF stitching, and version-mismatched exhibit numbers.
Real-time synchronized presentation in hearings — when the judge says 'go to page 47,' every party (in-person, virtual, jury, witness) lands on the same paginated page, reducing hearing time materially (Thomson Reuters cites a 77-day trial completed in 45 days).
Permission-controlled subcase creation lets one master case file generate party-specific views (witness, jury, self-represented litigant) without duplicating the underlying evidence.
ISO 27001:2013 certification and Microsoft Azure backing satisfy court procurement and judicial information security requirements that block many smaller vendors.
Custom enterprise pricing with no public tiers means small law firms cannot evaluate cost before engaging sales; firms not bound by court mandate often choose cheaper alternatives like Trial Director or OnCue.
Case Center is purely evidence and presentation — it has no time tracking, billing, conflict checking, or matter lifecycle features, so firms must run it alongside Clio, Centerbase, or another practice-management system.
Initial rollouts have surfaced glitches; the North Carolina Administrative Office of the Courts publicly noted judiciary access issues to evidentiary files during phased deployment, prompting some firms to delay adoption.
No public API or programmatic export path means migrating away requires manual case-by-case export through the built-in tools — a substantial blocker for any firm wanting to consolidate evidence into a unified DMS.
When a court switches mandated platforms (or a firm relocates its practice to a non-Case Center jurisdiction), the historical case archive becomes harder to repurpose than it would be in an open DMS.
Reasons to switch
Why people leave Thomson Reuters Case Center
The recurring reasons buyers give for replacing Thomson Reuters Case Center. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Thomson Reuters Case Center fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Thomson Reuters Case Center pricing overview
Thomson Reuters Case Center uses a custom enterprise pricing model with no publicly available per-user or per-case rates. Pricing is negotiated based on court, agency, or firm deployment size and is only available through direct sales contact. There are no self-serve or free tiers.
Custom Enterprise
Tier 1 of 1
Custom (contact sales)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Thomson Reuters Case Center's schedule — see our quote-based pricing →
What gets migrated
Thomson Reuters Case Center object support
Object-by-object support for Thomson Reuters Case Center migrations. Per-pair details surface during scoping.
Cases
Fully supportedCases are the root container in Case Center. They hold evidence documents, assign court participants by role, and generate the paginated case file. We map the source case structure 1:1 and preserve all participant assignments and case-level metadata during migration.
Evidence Documents
Fully supportedDocuments and multimedia are uploaded into a Case as evidence. Case Center automatically paginates, indexes, and generates a presentation-ready file. We preserve document ordering, pagination sequence, and all uploaded file variants including video and audio.
Subcase Files
Fully supportedCase Center creates subcase files that share selected files or sections with specific parties based on administrator-set permissions. We map subcase hierarchies and reproduce the permission-based file sharing structure in the destination system.
Permissions and User Roles
Mapping requiredCase Center assigns roles (judge, attorney, witness, jury, self-represented litigant, court staff) that control document visibility. Role models vary between court-hosted and law firm deployments. We map roles to the closest destination equivalent and flag any role that has no direct equivalent in the target system.
Search Index and Annotations
Mapping requiredCase Center builds AI-powered search indexes across all case materials including handwritten text and images, and supports Boolean search. Annotations (hyperlinks, notes) are attached to specific pages. We preserve the annotation layer but note that search index reconstruction depends on the destination platform's search engine capabilities.
Redactions
Mapping requiredRedactions are applied to specific pages within documents and are preserved as metadata. Migration to a destination that does not support the same redaction model requires converting redactions to a static burned-in overlay or a field-level redaction flag depending on the target system.
Custom Fields
Mapping requiredWhile Case Center supports case-level metadata and subcase creation, the custom field model is not as flexible as a full CRM. We map any custom fields we find to standard or custom fields in the destination and flag where the destination schema requires a value that the source did not capture.
Multimedia Files (Video/Audio)
Fully supportedCase Center supports video and audio evidence with synchronized playback in hearings. We preserve the original media files and ensure they are linked to the correct exhibit number and case record in the destination platform.
Disclosure and Evidence Exchange Records
Mapping requiredCase Center maintains records of evidence being shared with opposing counsel and tracks what has been disclosed. We migrate the disclosure log as a structured record, noting that the export of disclosure metadata depends on whether it was recorded in Case Center or in a separate matter management system.
| Object | Support | Notes |
|---|---|---|
| Cases | Fully supported | Cases are the root container in Case Center. They hold evidence documents, assign court participants by role, and generate the paginated case file. We map the source case structure 1:1 and preserve all participant assignments and case-level metadata during migration. |
| Evidence Documents | Fully supported | Documents and multimedia are uploaded into a Case as evidence. Case Center automatically paginates, indexes, and generates a presentation-ready file. We preserve document ordering, pagination sequence, and all uploaded file variants including video and audio. |
| Subcase Files | Fully supported | Case Center creates subcase files that share selected files or sections with specific parties based on administrator-set permissions. We map subcase hierarchies and reproduce the permission-based file sharing structure in the destination system. |
| Permissions and User Roles | Mapping required | Case Center assigns roles (judge, attorney, witness, jury, self-represented litigant, court staff) that control document visibility. Role models vary between court-hosted and law firm deployments. We map roles to the closest destination equivalent and flag any role that has no direct equivalent in the target system. |
| Search Index and Annotations | Mapping required | Case Center builds AI-powered search indexes across all case materials including handwritten text and images, and supports Boolean search. Annotations (hyperlinks, notes) are attached to specific pages. We preserve the annotation layer but note that search index reconstruction depends on the destination platform's search engine capabilities. |
| Redactions | Mapping required | Redactions are applied to specific pages within documents and are preserved as metadata. Migration to a destination that does not support the same redaction model requires converting redactions to a static burned-in overlay or a field-level redaction flag depending on the target system. |
| Custom Fields | Mapping required | While Case Center supports case-level metadata and subcase creation, the custom field model is not as flexible as a full CRM. We map any custom fields we find to standard or custom fields in the destination and flag where the destination schema requires a value that the source did not capture. |
| Multimedia Files (Video/Audio) | Fully supported | Case Center supports video and audio evidence with synchronized playback in hearings. We preserve the original media files and ensure they are linked to the correct exhibit number and case record in the destination platform. |
| Disclosure and Evidence Exchange Records | Mapping required | Case Center maintains records of evidence being shared with opposing counsel and tracks what has been disclosed. We migrate the disclosure log as a structured record, noting that the export of disclosure metadata depends on whether it was recorded in Case Center or in a separate matter management system. |
Gotchas
What to watch for in Thomson Reuters Case Center migrations
Issues we've hit on past Thomson Reuters Case Center migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Court-hosted vs. firm-hosted deployment affects migration scope
No public API documentation for direct data extraction
Multimedia evidence requires separate media handling
Redaction metadata may not survive cross-platform migration intact
| Severity | Issue |
|---|---|
| High | Court-hosted vs. firm-hosted deployment affects migration scope |
| High | No public API documentation for direct data extraction |
| Medium | Multimedia evidence requires separate media handling |
| Medium | Redaction metadata may not survive cross-platform migration intact |
Leaving Thomson Reuters Case Center?
Where Thomson Reuters Case Center customers move next
12 destinations Thomson Reuters Case Center can migrate to.
How a Thomson Reuters Case Center migration works
Four steps, Thomson Reuters Case Center-specific
Connect
Not publicly documented for Case Center into Thomson Reuters Case Center. Scopes limited to read-only on the data we move.
Map
We translate Thomson Reuters Case Center-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Thomson Reuters Case Center quirks before production.
Migrate
Full migration with Thomson Reuters Case Center rate-limit handling. Rollback available throughout.
FAQ
Thomson Reuters Case Center migration FAQ
Answers to the questions buyers ask most during Thomson Reuters Case Center migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Thomson Reuters Case Center migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Thomson Reuters Case Center.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Thomson Reuters Case Center setup and destination — written quote back within a business day.