Will my Case Center permission sets and access groups migrate to Salesforce?

No. FlitStack AI migrates data and schema only — permission sets, access groups, role-scoped views, and user-role assignments in Case Center do not translate to Salesforce's sharing model. They must be rebuilt in Salesforce using Sharing Rules, Permission Sets, and Sharing Sets configured by your Salesforce admin post-migration. We preserve the Case Center permission matrix as a custom Access_Level__c field on each Case record and deliver a Sharing Rules plan that documents the intended access mapping so your admin can reconstruct the appropriate visibility for each case role.

What does a Case Center party record become in Salesforce?

Each unique party or participant from Case Center — defendants, witnesses, judges, opposing counsel — becomes a Salesforce Contact. Because Case Center stores parties inside individual case records rather than as shared entities, FlitStack de-duplicates across cases by email: if the same email appears in multiple Case Center cases, we create a single Salesforce Contact and link it to all relevant Cases via Case Contact Roles. The original party role (Plaintiff, Defendant, Expert Witness) maps to the Role field on Case Contact Role, and the Case Center role label is preserved in a custom Staff_Role_in_Source__c field on the Case for reference.

Can I migrate Case Center exhibits and evidence files to Salesforce?

Yes. Evidence files — PDFs, images, audio, and video — are downloaded from Case Center's storage and re-uploaded to Salesforce Files via the Content API, linked to the migrated Case record using ContentDocumentLink. Salesforce's default per-file limit is 25MB; files exceeding this threshold are flagged and handled via Salesforce Content or an external storage reference. The original exhibit ID, description, upload timestamp, and uploader are preserved as metadata fields on the ContentVersion record for chain-of-custody traceability.

What happens to sub-cases and nested case hierarchies in Salesforce?

Case Center sub-cases and nested sub-folders map to Salesforce Cases using the standard ParentId field for hierarchical relationships. The migration resolves each sub-case's parent_case_id reference to the corresponding Salesforce Case ID before loading, so the parent-child hierarchy is preserved in the Salesforce Case structure. We validate the hierarchy after load to confirm that the number of child cases in Salesforce matches the source count — any broken parent references are flagged in the reconciliation report.

Does the migration affect my Case Center account during cutover?

No. FlitStack AI uses scoped read access on the Case Center API during extraction — your team continues working in Case Center throughout the migration. A delta-pickup window of 24–48 hours after the initial load captures any cases, parties, or exhibits created or modified in Case Center during the cutover period. Evidence files uploaded during the delta window are fetched in a second extraction pass and appended to the Salesforce load before the final reconciliation report is generated.

How does Case Center hearing and calendar data map to Salesforce?

Case Center hearing records — hearing date, end date, courtroom, hearing type — become Salesforce Event records. The Event's WhatId is set to the migrated Salesforce Case ID, linking the hearing directly to the related case. The courtroom identifier populates the Event's Location field. If your team uses Salesforce's native calendar, these Events appear on the appropriate user's calendar view. We also create a custom Hearing_Type__c field on Event and surface it on the Case's related list for quick reference.

Can custom Case Center metadata fields migrate to Salesforce?

Yes. Any Case Center custom fields — jurisdiction codes, statutory provisions, bond amounts, court district, or other case-specific metadata — migrate to custom fields on the Salesforce Case object. We create each custom field in Salesforce before the migration run using the appropriate data type (text, number, date, pick-list, or long-text area). FlitStack generates a field creation manifest from the Case Center field inventory so your Salesforce admin can review and approve the custom schema before data lands.

Thomson Reuters Case Center to Salesforce Sales Cloud Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Thomson Reuters Case Center is a legal evidence management platform built around cases, exhibits, documents, and court-participant roles. It has no native CRM object model — parties are stored as contact-card records inside cases, not as standalone Contact objects with shared ownership. Salesforce Sales Cloud, by contrast, is built on a relational CRM graph: Accounts own Contacts, Contacts link to Opportunities and Cases, and every record has an OwnerId pointing to a Salesforce User. The migration therefore requires a structural translation: Case Center's case-participant records become Salesforce Contacts under Accounts, exhibits and documents re-upload to Salesforce Files, and the case-identifier chain becomes a Salesforce Case hierarchy with custom fields preserving Case Center's exhibit numbering, hearing dates, and jurisdiction metadata. Court-user accounts that do not map to Salesforce Users are flagged and routed to a fallback owner before the migration commits. Because Case Center exposes a rate-limited API for data extraction, FlitStack sequences the extraction in batches, validates record counts against Case Center's internal counts, and runs a field-level diff in a Salesforce sandbox before the production load.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Thomson Reuters Case Center

What's pushing teams away

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.

Choosing

Salesforce Sales Cloud

What's pulling them in

The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How Thomson Reuters Case Center objects map to Salesforce Sales Cloud

Each row shows how a Thomson Reuters Case Center object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Thomson Reuters Case Center

Case (Case Center)

maps to

Salesforce Sales Cloud

Case (Salesforce)

1:1

Fully supported

Case Center case records map 1:1 to Salesforce Case records. The Salesforce Case Number auto-generates, but we preserve the original Case Center case identifier in Source_Case_ID__c. Jurisdiction, case type, and status fields translate via value-mapping against Salesforce's standard Status pick-list and custom Case Type field.

Thomson Reuters Case Center

Sub-case / Sub-folder

maps to

Salesforce Sales Cloud

Case (with ParentId)

1:1

Fully supported

Case Center sub-cases nest under parent cases. Salesforce Cases support a ParentId field for hierarchical case chains. We resolve the parent reference during migration so sub-cases land with the correct ParentId pointing to the migrated parent case ID in Salesforce.

Thomson Reuters Case Center

Party / Participant (contact card inside case)

maps to

Salesforce Sales Cloud

Contact

1:1

Fully supported

Case Center party records — opposing counsel, defendants, witnesses, judges — become Salesforce Contacts. Because Case Center stores parties inside individual cases, we de-duplicate across cases by email: if the same email appears in multiple Case Center cases, we create one Salesforce Contact and link it to all related Cases via Case Contact Roles.

Thomson Reuters Case Center

Party Role

maps to

Salesforce Sales Cloud

Case Contact Role

1:1

Fully supported

Case Center role labels (Plaintiff, Defendant, Expert Witness, Judge, Clerk) map to Salesforce Case Contact Role Role pick-list values. If Case Center uses a role not in Salesforce's standard list, we create a custom Role__c field on Case Contact Role and populate it from the source value.

Thomson Reuters Case Center

Exhibit / Evidence File

maps to

Salesforce Sales Cloud

ContentDocument / Salesforce Files

1:1

Fully supported

Evidence files from Case Center (PDFs, images, video, audio) are downloaded from Case Center's storage, re-uploaded to Salesforce Files, and linked to the migrated Case via ContentDocumentLink. The original exhibit number is stored in Exhibit_ID__c on the linked ContentVersion record for traceability.

Thomson Reuters Case Center

Hearing / Calendar Event

maps to

Salesforce Sales Cloud

Event

1:1

Fully supported

Case Center hearing records (date, time, courtroom, hearing type) translate to Salesforce Events. The Event's WhatId links to the migrated Case. StartDateTime and EndDateTime are set from the source hearing schedule; Location is populated from the courtroom identifier in Case Center.

Thomson Reuters Case Center

Annotation / Note on Evidence

maps to

Salesforce Sales Cloud

Note

1:1

Fully supported

Case Center annotations and notes attached to specific exhibits become Salesforce Notes linked to the corresponding ContentVersion. Original annotation text and annotator name are preserved in the Note Body and OwnerId fields respectively. Timestamps from Case Center — including creation date and last-modified date — map directly to the CreatedDate and LastModifiedDate fields on the Salesforce Note record to maintain full audit history.

Thomson Reuters Case Center

Custom Case Field (metadata)

maps to

Salesforce Sales Cloud

Custom Field on Case (__c)

1:1

Fully supported

Case Center custom fields (jurisdiction codes, statutory provisions, bond amounts, court district) require custom fields on the Salesforce Case object. Each custom field is created in Salesforce before migration, using Field_Type__c to name the field and preserve the data type (text, number, date, pick-list).

Thomson Reuters Case Center

User / Staff Assignment

maps to

Salesforce Sales Cloud

User

1:1

Fully supported

Case Center staff users (case managers, clerks, administrators) resolve to Salesforce Users by email match. Case Center users without an email in Salesforce are flagged and assigned to a designated fallback User; their original Case Center role is preserved in a custom Staff_Role_in_Source__c field on the Case record they are assigned to.

Thomson Reuters Case Center

Permission Set / Access Group

maps to

Salesforce Sales Cloud

Permission Set / Sharing Rule

1:1

Fully supported

Case Center permission scoping by role (counsel-only, judge-only, party-public) has no direct Salesforce equivalent. We document the access matrix and provide a Salesforce Sharing Rules plan for the admin to configure post-migration. Case-level access is preserved as a custom Access_Level__c pick-list on the Case for manual reconstruction.

Thomson Reuters Case Center	Salesforce Sales Cloud	Compatibility
Case (Case Center)	Case (Salesforce)1:1	Fully supported
Sub-case / Sub-folder	Case (with ParentId)1:1	Fully supported
Party / Participant (contact card inside case)	Contact1:1	Fully supported
Party Role	Case Contact Role1:1	Fully supported
Exhibit / Evidence File	ContentDocument / Salesforce Files1:1	Fully supported
Hearing / Calendar Event	Event1:1	Fully supported
Annotation / Note on Evidence	Note1:1	Fully supported
Custom Case Field (metadata)	Custom Field on Case (__c)1:1	Fully supported
User / Staff Assignment	User1:1	Fully supported
Permission Set / Access Group	Permission Set / Sharing Rule1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Thomson Reuters Case Center gotchas

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

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Thomson Reuters Case Center gotchas		Salesforce Sales Cloud gotchas
Severity	Issue	Severity	Issue
High	Court-hosted vs. firm-hosted deployment affects migration scope	High	Workflow Rules and Process Builder are retired
High	No public API documentation for direct data extraction	High	Bulk API batch quota exhaustion during large imports
Medium	Multimedia evidence requires separate media handling	Medium	Storage overage billing is non-obvious
Medium	Redaction metadata may not survive cross-platform migration intact	Medium	Account-Contact many-to-many relationship mapping
		Low	Territory and team member import ordering dependencies

Pair-specific challenges

Case Center's party records are case-scoped, not shared contacts

Thomson Reuters Case Center stores party and participant information inside individual case records — the same person appearing in multiple cases may exist as a separate contact card in each case. Salesforce Contacts, by contrast, are shared records linked to Accounts. If Case Center does not use email as a consistent unique identifier across cases, the same individual may be de-duplicated into multiple Salesforce Contacts. We resolve by email match and flag ambiguous records where email is absent or duplicated, surfacing them in the pre-migration reconciliation report so your team can confirm which records to merge post-migration.
Evidence files re-uploaded to Salesforce Files may exceed the 25MB per-file limit

Case Center routinely handles multimedia evidence — video depositions, audio recordings, and high-resolution scanned exhibits that regularly exceed 25MB. Salesforce Files default to a 25MB per-file limit for standard uploads; larger files require Salesforce Content or an external document management integration. FlitStack flags files over the threshold before the migration runs and provides a two-path recommendation: chunked upload via Salesforce Content API or external storage with a ContentDocumentLink reference to the source URL.
Permission sets and access groups have no Salesforce equivalent and must be rebuilt

Case Center controls access by assigning users to role-scoped views within each case — a feature with no direct Salesforce analogue. Salesforce Sharing Rules, Permission Sets, and Sharing Sets manage access differently: they are tied to object ownership, record type assignment, and profile-level permissions rather than per-case role labels. We preserve the access matrix as a custom Access_Level__c field on the Case record and deliver a Sharing Rules configuration plan to your Salesforce admin post-migration for manual reconstruction.
Case Center API rate limits may extend extraction time for large case volumes

Thomson Reuters publishes API rate limits per request class in their developer portal, and bulk evidence exports consume API quota quickly at scale. FlitStack implements backoff logic and batch-sizing tuned to Case Center's documented limits, but organizations with 500+ active cases and high-volume multimedia may see extraction take longer than the base migration window. We surface this in the pre-migration estimate and split the load into sequential extraction runs if needed.
Exhibit chain-of-custody metadata requires a custom object for full fidelity

Case Center tracks exhibit handling — timestamps, handler, location, and redaction history — as part of its exhibit record. Salesforce Files store the file and basic metadata (created date, created by, version number) but do not natively support chain-of-custody logging per exhibit. For legal and compliance use cases where exhibit handling history is required, we create a custom Exhibit_History__c object linked to ContentDocument, logging each state change with a timestamp, handler, and action description sourced from Case Center's exhibit audit trail.

Migration approach

Six steps for a successful Thomson Reuters Case Center to Salesforce Sales Cloud data migration

Inventory Case Center records and map to Salesforce schema

FlitStack runs a discovery extraction against the Case Center API — pulling case records, sub-cases, party records, exhibit metadata, hearing records, and annotation data — and produces a schema inventory report. We compare the Case Center field inventory against Salesforce's standard and custom Case, Contact, and ContentVersion objects and deliver a pre-migration schema plan specifying which Salesforce custom fields to create before data lands.
Resolve user and staff assignments by email

Case Center staff users, counsel, and court personnel are matched to Salesforce Users by email. Unmatched users — those without a corresponding Salesforce login — are flagged in a pre-flight report and assigned to a designated fallback Salesforce User. Party records without email are de-duplicated by name and organization where possible; records that cannot be resolved are flagged for manual review before the migration run.
Migrate Accounts and Contacts before Cases

Salesforce requires Contacts to reference an AccountId, and Cases reference Contacts via Case Contact Roles. We sequence the migration so Accounts are created first from party organization names, then Contacts are created with AccountId lookups resolved, then Case Contact Roles link parties to cases. This ordering ensures referential integrity — no Contact lands without an Account, and no Case Contact Role links to a non-existent Contact.
Run a sample migration with field-level diff

We select a representative sample of 200–500 records spanning cases, parties, exhibits, and hearings and load it into a Salesforce sandbox environment first. A field-level diff report is generated that compares source values from Case Center against destination values in Salesforce, with any transformation, truncation, mapping discrepancy, or data-loss risk highlighted in red for immediate visibility. You review the diff report, validate that each mapped field carries the expected value, and confirm or adjust the mapping configuration before the full migration run commits to production.
Execute full migration with delta-pickup window

The full extraction-to-load run commits Case Center records to Salesforce in sequenced batches. A delta-pickup window of 24–48 hours after the initial load captures any records modified in Case Center during cutover. Evidence files are uploaded to Salesforce Files via the Content API, with files over 25MB flagged and handled via the alternative content strategy. An audit log records every operation; one-click rollback is available if the reconciliation report shows record counts or field values outside agreed tolerances.
Deliver sharing rules plan and post-migration documentation

Since Case Center permission scoping cannot migrate directly, we deliver a Sharing Rules configuration plan that maps Case Center's role-view matrix to Salesforce's sharing model — specifying which users should see which Cases based on their Case Contact Role. We also provide a full field-mapping reference document and a post-migration de-duplication run for Contacts that were split during migration due to inconsistent source identifiers.

Platform deep dives

Context on both ends of the pair

Thomson Reuters Case Center

Source

Strengths

Processes over 900,000 cases with 500 million pages of evidence across 126 countries
ISO 27001:2013 certified security framework governing all customer data
AI-powered search across handwritten documents and images with Boolean support
Automatic pagination and indexing generates presentation-ready case files from first upload
Supports in-person, virtual, and hybrid courtroom configurations with role-specific views

Weaknesses

Custom pricing only — no public tier structure or per-user rates published
No public API documentation for Case Center specifically; Thomson Reuters developer portal focuses on other products
Primarily an evidence management tool, not a full matter or case lifecycle management system
Migrating out requires understanding the difference between court-hosted and firm-hosted deployment contexts
Switching costs are high for courts mandated to use Case Center for evidentiary proceedings

Salesforce Sales Cloud

Destination

Strengths

Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

	Thomson Reuters Case Center Source	Salesforce Sales Cloud Destination
Strengths	Processes over 900,000 cases with 500 million pages of evidence across 126 countries ISO 27001:2013 certified security framework governing all customer data AI-powered search across handwritten documents and images with Boolean support Automatic pagination and indexing generates presentation-ready case files from first upload Supports in-person, virtual, and hybrid courtroom configurations with role-specific views	Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow. Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer. Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures. Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization. Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.
Weaknesses	Custom pricing only — no public tier structure or per-user rates published No public API documentation for Case Center specifically; Thomson Reuters developer portal focuses on other products Primarily an evidence management tool, not a full matter or case lifecycle management system Migrating out requires understanding the difference between court-hosted and firm-hosted deployment contexts Switching costs are high for courts mandated to use Case Center for evidentiary proceedings	Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price. Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise. Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant. API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling. Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Thomson Reuters Case Center and Salesforce Sales Cloud.

Object compatibility
B
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
Thomson Reuters Case Center: Thomson Reuters developer portal documents API rate limits for other products but Case Center-specific API documentation is not publicly available.
Data volume sensitivity
B
Thomson Reuters Case Center doesn't expose a bulk API — REST + parallelization used for high-volume runs.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Thomson Reuters Case Center to Salesforce Sales Cloud

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Thomson Reuters Case Center

Salesforce Sales Cloud

How Thomson Reuters Case Center objects map to Salesforce Sales Cloud

What specifically takes care here

Six steps for a successful Thomson Reuters Case Center to Salesforce Sales Cloud data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Thomson Reuters Case Center to Salesforce Sales Cloud migration cost

What are you migrating?

Frequently asked questions about Thomson Reuters Case Center to Salesforce Sales Cloud data migrations

Can't find your answer?

Related migrations to explore

Move from Thomson Reuters Case Center.
Land in Salesforce Sales Cloud, intact.

Migrate from Thomson Reuters Case Center to Salesforce Sales Cloud

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Thomson Reuters Case Center

Salesforce Sales Cloud

How Thomson Reuters Case Center objects map to Salesforce Sales Cloud

What specifically takes care here

Six steps for a successful Thomson Reuters Case Center to Salesforce Sales Cloud data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Thomson Reuters Case Center to Salesforce Sales Cloud migration cost

Frequently asked questions about Thomson Reuters Case Center to Salesforce Sales Cloud data migrations

Can't find your answer?

How long does a Thomson Reuters Case Center to Salesforce Sales Cloud migration take?

Will my Case Center permission sets and access groups migrate to Salesforce?

What does a Case Center party record become in Salesforce?

Can I migrate Case Center exhibits and evidence files to Salesforce?

What happens to sub-cases and nested case hierarchies in Salesforce?

Does the migration affect my Case Center account during cutover?

How does Case Center hearing and calendar data map to Salesforce?

Can custom Case Center metadata fields migrate to Salesforce?

Related migrations to explore

Move from Thomson Reuters Case Center. Land in Salesforce Sales Cloud, intact.

Move from Thomson Reuters Case Center.
Land in Salesforce Sales Cloud, intact.