Migrate from Thomson Reuters Case Center to Freshsales

Evidence files and multimedia have no native Freshsales storage equivalent

Case Center's core value proposition is evidence file management — storing documents, images, audio, and video with presentation-ready viewing for hearings. Freshsales has file attachment support but no equivalent to Case Center's paginated, presentation-mode evidence viewer, no concept of exhibits or evidence types, and a 25MB per-file size limit. FlitStack AI migrates evidence metadata (title, file type, upload date, section, associated case) to a custom Evidence_Reference__c object, but the actual files must be re-hosted externally (SharePoint, Google Drive, or a dedicated evidence management tool) and linked via URL in Freshsales. Your team must plan for this file rehousing before go-live, as evidence file size and count will affect the migration timeline and storage decisions in Freshsales.

Case Center user roles do not map to Freshsales permission model

Case Center distinguishes users by hearing-specific roles: Judge, Counsel, Court Staff, Self-Represented Litigant, and Party. These roles control what evidence each user can see and present during a hearing. Freshsales has no equivalent role-per-case concept — its permission model is org-wide (Admin, Sales Manager, Sales User) scoped to CRM modules. The role information from Case Center migrates as a custom pick-list field (User_Role__c) on the Contact record, but the hearing-access logic cannot be replicated in Freshsales. Teams relying on granular evidence access controls need a separate access management strategy outside the CRM.

Freshsales API rate limits can slow large-volume Case Center extractions

Freshsales imposes tiered API rate limits: Growth plans allow 1000 requests per hour, Pro allows 2000 per hour, and Enterprise allows 5000 per hour. A Case Center instance with thousands of evidence items, hearing records, and user accounts can generate API calls that exceed Growth-plan limits during migration. FlitStack AI paces extraction requests and will recommend a Freshsales plan upgrade before migration if your record volume exceeds the API budget. Rate-limit errors (HTTP 429) during migration cause retry logic that extends the migration window — planning for this upfront avoids surprises at cutover.

Case Center workflows (hearing preparation, evidence upload sequences) cannot migrate

Case Center automates evidence upload workflows, hearing preparation checklists, and invite-list management sequences. Freshsales has its own automation engine (workflows, sales sequences, territory rules) that is incompatible with Case Center's workflow logic. As with all FlitStack migrations, we migrate data only — Case Center workflows must be rebuilt in Freshsales or documented as a separate process for your admin to recreate. We can export Case Center workflow definitions as a reference document for your Freshsales admin during the rebuild phase.

Multi-user case access (N:N permission sets) collapses to primary contact-case link

Case Center allows multiple users to be granted access to a single case via invite lists, and users can belong to multiple cases simultaneously — an N:N relationship. Freshsales Accounts have a primary contact-to-account relationship; multi-case contact access requires either multiple Account records (one per case) or a custom junction object. FlitStack AI resolves this by creating one Account per Case Center case and attaching the primary user contacts. Users who need access to multiple cases are represented as separate Contact records linked to each Account. This structural change means a Case Center user who appeared once may appear multiple times in Freshsales if they participate in multiple cases.