CRM migration

Migrate from Thomson Reuters Case Center to monday CRM

Field-level mapping, validation, and rollback between Thomson Reuters Case Center and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.

Thomson Reuters Case Center logo

Thomson Reuters Case Center

Source

monday CRM

Destination

monday CRM logo

Compatibility

100%

13 of 13

objects map 1:1 between Thomson Reuters Case Center and monday CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Thomson Reuters Case Center is a purpose-built digital evidence management system for courts, administrative hearing agencies, and law firms — it organizes documents into paginated, searchable case files, handles multimedia evidence, and provides in-hearing presentation tools with per-page navigation controls. Monday CRM is a visual Work OS that represents work as boards containing items organized by columns; it has native CRM entities for contacts, companies, and deals (called pipelines) but no native concept of a legal case, paginated document bundle, or court hearing schedule. The migration challenge is translating Case Center's evidence-centric data model into Monday's activity-centric model: cases become boards or deal pipeline groups, parties become contacts, documents become items with file attachments, hearing dates become date columns, and annotations become item updates or subitems. FlitStack AI extracts data via Case Center's export API and REST endpoints, transforms the hierarchical document structure into flat Monday items organized by board groups, re-hosts document and multimedia files to Monday's file storage, and maps party records to CRM contacts with original firm/role metadata preserved as custom columns. Monday's automation rules, board templates, and column types must be rebuilt in Monday CRM after migration — we deliver a rebuild reference export so your admin can replicate Case Center workflow triggers as Monday automations. The migration mechanism uses Monday's REST API with rate-limit awareness (1,000 calls/day on Basic, 10,000 on Pro) to handle the throughput required for large evidence libraries.

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 logo

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

monday CRM logo

monday CRM

What's pulling them in

  • Users praise the board-based visual interface for making pipeline stages immediately legible to non-technical team members without CRM training.
  • The no-code automation builder lets sales ops teams create lead routing, stage updates, and email triggers without developer involvement.
  • Integration ecosystem connects to Slack, Gmail, Outlook, and Zapier with minimal configuration, reducing friction for teams already using these tools.
  • The flexible column system lets teams build custom CRM views — deal value, close date, lead source — without needing a developer or pre-defined schema.
  • Teams already using monday Work Management can layer CRM features onto existing boards rather than starting from scratch.

Object mapping

How Thomson Reuters Case Center objects map to monday CRM

Each row shows how a Thomson Reuters Case Center object lands in monday CRM, 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 / Matter

maps to

monday CRM

Board

1:1
Fully supported

Case Center cases become Monday CRM boards. Each board represents one legal matter. The board name derives from the Case Center case title or case number. Board groups within the board can map to Case Center sections (e.g., Discovery, Motions, Exhibits). This is the fundamental unit translation — all other objects (parties, documents, hearings) nest under this board.

Thomson Reuters Case Center

Party

maps to

monday CRM

Contact

1:1
Fully supported

Case Center party records (plaintiffs, defendants, witnesses, counsel) map directly to Monday CRM contacts. Party name maps to Contact name. Party role (plaintiff, defendant, expert witness) is preserved as a custom column on the contact record. Multiple parties associated with one case link via the board's contact integration feature in Monday CRM.

Thomson Reuters Case Center

Party Role

maps to

monday CRM

Custom Column (Party_Role__c)

1:1
Fully supported

Case Center party roles (Plaintiff, Defendant, Expert Witness, Counsel, Court) have no direct Monday CRM equivalent — a custom single-select column on the Contact entity stores the party role value. FlitStack preserves the original role label and flags any non-standard roles for admin review before the full migration runs.

Thomson Reuters Case Center

Document / Exhibit

maps to

monday CRM

Item (within Board)

1:1
Fully supported

Case Center documents and exhibits become Monday CRM items within the board representing that case. Each document's title becomes the item name, and the item's description field stores the document's description and classification (e.g., Exhibit A, Correspondence, Filing). Document upload becomes a Monday file attachment on the item.

Thomson Reuters Case Center

Section

maps to

monday CRM

Group (within Board)

1:1
Fully supported

Case Center sections within a case (e.g., Evidence, Motions, Correspondence) translate to Monday board groups. Documents and other objects within each section become items in the corresponding group. This preserves the Case Center filing structure within the Monday board layout.

Thomson Reuters Case Center

Hearing

maps to

monday CRM

Date Column + Item

1:1
Fully supported

Case Center hearing records become dedicated items within the case board with a hearing date column. The item name stores the hearing type (e.g., Status Conference, Trial, Motion Hearing). Hearing-specific metadata (presiding judge, location, virtual/in-person) is stored as custom columns on the hearing item.

Thomson Reuters Case Center

Annotation / Note

maps to

monday CRM

Item Update / Subitem

1:1
Fully supported

Case Center annotations and notes attached to documents become Monday item updates on the document item. Each annotation's timestamp, author, and text content migrates as an update entry with the original timestamp preserved. Annotations on specific pages retain page reference metadata in the update text.

Thomson Reuters Case Center

Evidence

maps to

monday CRM

Item with File Attachment

1:1
Fully supported

Case Center evidence files including PDFs, images, audio recordings, and video files are extracted directly from Case Center storage and re-uploaded as Monday file attachments on the corresponding document item within the case board. File type classification, original upload date and time, and file size metadata are preserved as separate custom columns on the item. FlitStack performs checksum verification on each file after upload to confirm successful transfer.

Thomson Reuters Case Center

Custom Document Field

maps to

monday CRM

Custom Column (on Item)

1:1
Fully supported

Case Center allows custom fields on documents (e.g., Bates number, exhibit tag, classification level). These custom document fields are translated to Monday CRM custom columns on the item. Column type (text, number, date, dropdown) is inferred from the Case Center field type.

Thomson Reuters Case Center

Case Metadata

maps to

monday CRM

Board Columns

1:1
Fully supported

Case-level metadata in Case Center (case number, court, judge, filing date, case status) becomes board-level columns in Monday CRM. This information is stored on a designated 'Case Info' item within the board so it is accessible at the board level without requiring a separate database.

Thomson Reuters Case Center

Upload / Submission Log

maps to

monday CRM

Item Update History

1:1
Fully supported

Case Center tracks all document uploads and submissions with timestamps and submitting user. This log migrates as a series of dated updates on the document item in Monday CRM, preserving the full audit trail of who added or modified each document.

Thomson Reuters Case Center

Subcase / Subfolder

maps to

monday CRM

Subitem or Nested Board

1:1
Fully supported

Case Center subcases and subfolders within a case can map to Monday subitems (within an item) or to separate linked boards depending on the complexity. FlitStack surfaces the hierarchy in the migration plan and the client chooses the structure — subitems for flat hierarchies, linked boards for deeply nested multi-party subcases.

Thomson Reuters Case Center

Participant Access Log

maps to

monday CRM

Board Activity Log

1:1
Fully supported

Case Center records which participants accessed which documents, at what times, and under what user accounts. This granular access log data migrates as a series of dated update entries or activity log entries on the corresponding document items in Monday CRM. Each migrated entry preserves the participant identity, the accessed document reference, the access timestamp, and the access type (view, download, annotation), maintaining the complete audit trail for compliance and oversight purposes.

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 logo

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

monday CRM logo

monday CRM gotchas

High

Subitems are not included in bulk exports

High

Daily API call limits vary sharply by plan

Medium

Legacy automations (Sentence Builder) are being deprecated

Medium

Excel and account exports only include table views

Low

Enterprise admins can disable non-admin exports

Pair-specific challenges

  • Case Center's evidence-centric data model has no direct Monday CRM equivalent

    Case Center organizes all work around a paginated, searchable case file with sections, exhibits, and in-hearing presentation controls. Monday CRM is a general Work OS — it has no native concept of a legal case, paginated document bundle, or per-page presentation routing. FlitStack translates Case Center cases to Monday boards and documents to items, but the hearing presentation features (directing everyone to the right page, multimedia playback controls) cannot be replicated in Monday CRM. Teams must plan for this gap: case context is preserved in item metadata and descriptions, but the live hearing workflow requires Case Center or a dedicated legal platform. This is not a data loss issue — all factual content migrates — but a functional gap that must be acknowledged during migration planning.

  • Monday CRM per-seat and per-call rate limits constrain large evidence migrations

    Monday CRM enforces API rate limits that directly impact how fast Case Center data can migrate. On Basic/Standard plans the daily call limit is 1,000 API calls per day; on Pro it rises to 10,000. Case Center repositories with thousands of documents and multimedia files require careful batching to stay within these limits. Additionally, Monday CRM pricing is per-seat — unlike Case Center which is licensed per user with bulk evidence storage, Monday charges $12–$17 per user per month regardless of how much case data is stored. Teams migrating large evidence libraries from Case Center should expect the migration to run in off-peak hours using Monday's batch API endpoints, with the full load spread across multiple days rather than completing in a single pass.

  • Document and multimedia files must be re-hosted to Monday's storage

    Case Center stores all documents, images, audio, and video in Thomson Reuters cloud infrastructure tied to the case record. Monday CRM stores files as attachments on items within boards. FlitStack downloads every file from Case Center and re-uploads it to Monday CRM's file storage. Monday's file size limits vary by plan: Standard includes 20GB total storage, Pro includes 100GB. Large evidence libraries (hundreds of PDFs, hours of depositions) may exceed default storage allocations and require Enterprise plan storage add-ons. Additionally, Case Center's automatic pagination and indexing metadata does not carry over — the page numbering and exhibit tagging must be recreated as Monday custom columns (Bates_Number__c, Exhibit_Tag__c) since Monday has no native document pagination concept.

  • Monday CRM's automation model cannot replicate Case Center hearing workflow triggers

    Case Center has purpose-built automation for legal processes: hearing reminders, document submission deadlines, and participant notification triggers tied to case status changes. Monday CRM automations are board-level rules (when item moves to group X, then do Y) with no native concept of legal workflow stages or hearing calendar triggers. Migration of Case Center workflows to Monday automations requires a rebuild — FlitStack exports the Case Center workflow definitions (trigger conditions, notification recipients, deadline logic) as a structured JSON reference document that a Monday admin can use to configure equivalent automations using Monday's Automation Center. Until those automations are rebuilt, hearing reminders and deadline notifications will not fire automatically in Monday CRM.

  • Case Center participant access controls map to Monday workspace permissions with significant narrowing

    Case Center enforces granular role-based access for specific participant types: Judges, Court Staff, Counsel, Self-Represented Litigants — each with fine-grained permissions on which documents and sections they can view, annotate, or present. Monday CRM's permission model operates at the workspace and board level (Admin, Member, Guest, Viewer) with no native court-participant role concept. FlitStack migrates all participant contact records and access log data, but the permission structure cannot be replicated 1:1. Teams must redesign their access model in Monday CRM — typically by board (one board per case with participant guest access) or by using Monday's client portal feature. This redesign is a business decision, not a data migration action, and must be planned before the migration runs.

Migration approach

Six steps for a successful Thomson Reuters Case Center to monday CRM data migration

  1. Audit Case Center data volume and document hierarchy

    FlitStack AI runs a discovery scan against the Case Center account to inventory all cases, sections, parties, documents, annotations, hearings, and subcases. We extract the full object count, document file sizes and types, custom field definitions, and the hierarchical structure of each case (which sections nest under which, how parties associate with cases). This inventory drives the migration scope estimate, identifies which cases have complex nested subcases requiring the linked-board approach, and surfaces any documents exceeding Monday's storage thresholds before the migration begins.

  2. Design Monday CRM board and column architecture

    Based on the Case Center audit, FlitStack delivers a Monday CRM schema plan: one board per Case Center case, board groups mapped to sections, items mapped to documents and hearings, and custom columns defined to capture Case Center metadata (Bates numbers, exhibit tags, party roles, hearing types). We recommend the Case Info item pattern for board-level metadata and define the custom column types before any data is loaded. The client reviews and approves the schema plan, and any Monday custom columns requiring Enterprise-tier features are flagged at this stage.

  3. Resolve contacts and set board permissions

    Case Center party records are deduplicated by email — if the same person appears as a party in multiple cases, FlitStack creates a single Monday CRM contact and links it to each relevant board. Board permissions are set according to the client's chosen access model (workspace-wide guest access, per-board invites, or client portal groups). Monday users are matched to Case Center party records by email for contacts that will have Monday accounts; parties without Monday accounts are imported as contacts without active user status.

  4. Migrate cases, parties, and documents in dependency order

    The migration runs in a sequenced order that respects Monday's relational model: boards (cases) are created first, then contacts (parties) are loaded, then items (documents, hearings) are created within boards, and finally file attachments are uploaded. Annotations and access log entries are appended as item updates after their parent items exist. Subitems are created after their parent items. FlitStack uses Monday's batch API endpoints with rate-limit-aware throttling (1,000 calls/day on Basic, 10,000 on Pro) to process large volumes within the platform constraints. The migration runs in a staging environment first.

  5. Run sample migration with field-level diff and verify document integrity

    A representative sample — typically 5–10 cases spanning different document types, hearing records, and annotation volumes — migrates first. FlitStack generates a field-level diff comparing source Case Center values against the Monday CRM records, verifying that Bates numbers, exhibit tags, party roles, hearing dates, and document descriptions all transferred correctly. File attachments are checksum-verified against the original Case Center documents. The client reviews the sample diff and approves before the full migration proceeds.

  6. Execute full migration with delta-pickup window and deliver rebuild reference

    The full Case Center account migrates to Monday CRM using the approved schema. A delta-pickup window (24–48 hours after initial load) captures any Case Center records created or modified during the cutover window. FlitStack delivers the Case Center workflow definitions as a structured JSON export so the Monday admin can rebuild hearing reminders and deadline triggers in Monday's Automation Center. An audit log documents every record created, every file uploaded, and any records that failed validation — with one-click rollback available if reconciliation reveals unexpected gaps.

Platform deep dives

Context on both ends of the pair

Thomson Reuters Case Center logo

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
monday CRM logo

monday CRM

Destination

Strengths

  • Board-based UI makes pipeline stages and deal progress visually obvious without training.
  • No-code automation builder requires no developer resources to create lead routing and stage-triggered actions.
  • Flexible column system supports custom CRM fields without schema changes or admin involvement.
  • Integrates natively with Slack, Gmail, Outlook, and Zapier with minimal configuration overhead.
  • Layered product means teams already on monday Work Management can add CRM without migrating existing data.

Weaknesses

  • No native Contacts object separate from Items — contacts are managed inside a CRM module's People feature.
  • Pipeline and deal relationships use a flat item model rather than a relational object model, making complex CRM associations awkward.
  • Automations are plan-gated (250 actions/month on Standard, 25,000 on Pro) and the legacy Recipe system is being deprecated.
  • Customization and advanced views (Chart, Formula, Dependency) are locked behind Pro and Enterprise tiers.
  • Per-seat pricing with non-refundable annual billing creates cost lock-in risk during migration.

Complexity grading

How hard is this migration?

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

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Thomson Reuters Case Center and monday CRM.

  • Object compatibility

    B

    1 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.

Estimator

Estimate your Thomson Reuters Case Center to monday CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Thomson Reuters Case Center to monday CRM data migrations

Answers to the questions buyers ask most during Thomson Reuters Case Center to monday CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Thomson Reuters Case Center to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Case Center to Monday CRM migrations complete within 48–72 hours of clock time for under 10,000 records. Cases with large evidence libraries or complex nested subcases extend to 2–4 weeks because Monday's API rate limits (1,000 calls/day on Basic, 10,000 on Pro) constrain how fast documents and attachments can be batch-loaded. The longest planning step is designing the Monday board and column architecture to capture Case Center metadata (Bates numbers, exhibit tags, party roles) before data lands.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Thomson Reuters Case Center.
Land in monday CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day