# Summation Legal Software: Managing Legacy Case Databases and Modern Alternatives Summation legal software is a legacy litigation support and case management platform historically used by law firms to organize deposition transcripts, evidence documents, and case chronology. Decades of critical trial exhibits, transcript annotations, and Bates-stamped productions remain trapped inside these aging on-premise databases. This guide covers how to extract legacy Summation case data, resolve broken image paths, and migrate litigation materials into modern cloud workspaces. Source: https://fast.io/resources/summation-legal-software/ Author: [Derek Labian](https://fast.io/authors/derek-labian/) Last reviewed: 2026-09-10 ## The Role of Summation Legal Software in Litigation Support Decades of trial preparation, transcript digests, and Bates-stamped document productions remain locked inside legacy on-premise case databases that modern operating systems can no longer reliably run. When a firm faces a subpoena on a closed matter or needs to revive a case archive, relying on obsolete desktop litigation support tools creates immediate discovery risk and technical gridlock. Summation is a legacy litigation support and case management platform historically used by law firms to organize deposition transcripts, evidence documents, and case chronology. First introduced by Summation Legal Technologies, the software became an industry standard across litigation departments for more than two decades. Later acquired by CT Corporation to become CT Summation, the product suite subsequently passed to AccessData and eventually to Exterro. Across these corporate iterations, products such as Summation Blaze, Summation iBlaze, Summation Enterprise, and WebBlaze formed the operational spine of trial teams. Litigation support specialists relied on Summation to handle three distinct aspects of case preparation: transcript analysis, document indexing, and case timeline management. Before the arrival of modern cloud review platforms, legal teams managed discovery as physical paper or scanned image collections. Summation allowed paralegals and attorneys to cross-reference witness testimony with marked trial exhibits, search full-text deposition records across dozens of witnesses, and code documents by issue category. The architecture of classic Summation (particularly iBlaze) reflected the computing constraints of its era. At its core, the software relied on a file-based dBase and FoxPro database structure, using database table files paired with memo files to track document metadata, witness names, and attorney notes. Case files were hosted on a local Windows file share or an internal local-area network drive. When multiple litigation team members worked in the same matter simultaneously, the software relied on Windows file share locking to prevent write collisions. For larger installations, Summation Enterprise replaced the flat file structure with a Microsoft SQL Server backend, while WebBlaze introduced early browser-based access for remote document reviewers. Summation also featured the Briefcase system. A paralegal could check out a subset of a case database, export it to a field laptop, and carry it directly into depositions or courtroom hearings without needing an active network connection. Once trial proceedings concluded, the team imported the briefcase database back into the master firm archive, merging new notes and exhibit links. ### Core Database Structures and Transcript Files Understanding Summation requires unpacking the proprietary and semi-proprietary file formats that made up a case directory. A typical matter folder contained distinct subdirectories for document tables, deposition transcripts, image repositories, and index catalogs. Deposition and trial transcripts were stored primarily as synchronized text files or proprietary formats such as Summation Electronic Format alongside standard ASCII files and condensed transcript formats. These files preserved exact page and line numbers, allowing attorneys to execute boolean keyword searches across an entire witness roster. Litigators created transcript digests directly within the software, attaching topical issue codes and margin summaries to specific page and line coordinates. Document images and Bates-stamped exhibits were linked to the database through specialized batch load files, most notably the Document Image Information (DII) format. The DII file served as an instruction manifest, telling the database engine which scanned image files on the local drive corresponded to specific Bates records and metadata fields. Through this mechanism, clicking a document record in the Summation spreadsheet grid instantly loaded the corresponding scanned image in the document viewer. ## What Happened to Summation and Why Legacy Databases Persist The decline of Summation as a dominant litigation platform was driven by a fundamental transition in how evidence is created and produced. Summation was engineered during the paper-discovery era, when litigation support teams scanned paper boxes into single-page black-and-white TIFF files and generated extracted text using early optical character recognition engines. Over the following decade, litigation discovery shifted decisively from scanned paper to native electronically stored information (ESI). Law firms were no longer managing static TIFF images; they were collecting gigabytes and terabytes of native Outlook email archives, live spreadsheet models, instant message logs, and high-definition deposition video recordings. Summation's desktop file-server architecture could not withstand this volume. The file-based database backend suffered from severe database corruption when multiple users ran complex queries simultaneously over local network shares. File size ceilings on legacy tables led to indexing crashes, while processing native file types required cumbersome third-party conversion utilities. Corporate consolidation accelerated this divergence. AccessData acquired CT Summation to combine the case management platform with its digital forensics technology, FTK (Forensic Toolkit). While AccessData rebuilt later iterations of Summation on modern SQL architectures, the product faced intense competition from cloud-native eDiscovery platforms. Exterro later acquired AccessData to expand its enterprise legal governance, risk, and compliance software portfolio. Over time, active standalone enhancement of classic desktop Summation versions ceased. Despite this obsolescence, thousands of legacy Summation databases remain active or archived inside law firm file servers. Law firms maintain these repositories for practical and operational reasons: * Closed Matter Archiving: Professional conduct rules and firm record retention policies require litigation files to be preserved for years following final judgment. Firms frequently keep legacy matter directories intact rather than spending non-billable hours converting old files. * Repeat Litigation and Corporate Memory: Institutional clients often face recurring disputes involving the same product lines, patents, or employment practices. Accessing past transcripts, witness cross-examination outlines, and exhibit collections from cases litigated years ago provides immense strategic value. * Third-Party Subpoenas and Appeals: Dormant cases can be reopened unexpectedly by appellate remands, post-conviction motions, or third-party subpoenas demanding original production records. ### Technical Liabilities of Preserving On-Premise Summation Installs Keeping legacy Summation installations running on internal servers poses acute operational and security challenges. Classic iBlaze relies on outdated desktop components, deprecated Visual Basic runtimes, and legacy database drivers that are unsupported on modern Windows operating systems. Many firms resort to hosting Summation on unpatched, virtualized legacy Windows workstations isolated on their internal network. These legacy systems lack modern security protections and do not connect with modern identity providers. If the host machine suffers hardware failure or storage corruption, the firm risks losing unrecoverable attorney work product, including years of transcript annotations and custom issue coding. Furthermore, institutional knowledge surrounding Summation is vanishing. The litigation support specialists and paralegals who understood DII load syntax and briefcase synchronization are retiring. When a litigation partner requests an urgent record from an archived matter, current legal operations teams often find themselves locked out of the data simply because nobody on staff knows how to navigate the legacy interface. ## Extracting Transcripts, Load Files, and Exhibits from Summation Migrating data out of a legacy Summation repository requires systematically decomposing the case folder into its constituent elements: database tables, full-text transcripts, document images, and attorney annotations. Attempting to copy the folder wholesale onto a generic cloud drive will fail because modern cloud storage cannot parse the underlying index or resolve internal path pointers. A complete Summation case extraction involves five primary components: * Metadata Tables: The primary document database resides in table files paired with memo files. These tables store core bibliographic fields (BegBates, EndBates, Author, Recipient, Date, Document Title) and custom coding values (Privileged, Responsiveness, Issue Tags). * Deposition and Trial Transcripts: Located in the matter's transcript directory, these include verbatim testimony files with line and page markers. * Transcript Annotations and Digests: The notes, summaries, and issue codes applied by trial counsel during discovery. These may be stored within the transcript files themselves or in auxiliary memo fields. * Image Load Files: Plain-text ASCII files that establish document boundaries and link image records to specific graphic files. * Image Repositories: Folders containing single-page TIFF files or multi-page image sets organized into volume directories. To migrate these assets successfully, legal operations teams must understand the syntax of Summation DII files. DII load files use specific character tokens to define document parameters: * `@T Document_ID`: Defines the document break and identifies the Bates number or Document ID for a new record. * `@C Field_Name Value`: Populates a database metadata column with the specified value, such as an author name or document date. * `@D Directory_Path`: Specifies the directory path where associated page images are stored. * `@I Filename`: Specifies the filename of the image file. * `@V Volume_Label`: Specifies the volume or storage media label where the files reside. * `@FULLTEXT File_Path`: References the path to an external OCR or extracted text file. ### Resolving Broken Image Paths and Converting Single-Page TIFFs The most common failure encountered when extracting Summation data is broken image paths. In legacy DII files, image directories were frequently hardcoded to specific network drive letters or legacy server shares. When files are copied to a new machine or cloud drive, those absolute paths break, rendering the documents inaccessible. Legal IT specialists must normalize these paths before ingestion into modern platforms: * Path Normalization: Use text editing scripts or migration utilities to rewrite absolute paths into relative paths matching the target directory structure. * Image Stitching: Summation stored each scanned document page as an individual single-page TIFF file. A fifty-page contract was stored as fifty separate image files. Modern litigation teams expect multi-page, searchable PDF documents. Run a batch conversion script that reads document boundary markers (tokens in the DII file or Bates ranges in the database table) and stitches single-page TIFFs into unified PDF files. * OCR Text Layering: Ensure that the conversion process embeds the extracted text from Summation's OCR files directly into the PDF text layer. This preserves full-text searchability without requiring manual re-scanning. ## Modern Alternatives to Summation for Litigation Teams When evaluating alternatives to Summation, litigation practices must balance capability, cost, and administrative overhead. In the classic Summation era, a single desktop program handled everything from transcript reading to document productions. Today, the legal technology landscape has divided into distinct categories. ### 1. Heavy Enterprise eDiscovery Platforms Platforms such as Relativity, Everlaw, and DISCO represent the enterprise tier of eDiscovery. These systems are engineered for large-scale corporate litigation, government investigations, and multi-party disputes involving millions of documents. * Strengths: Advanced Technology-Assisted Review, predictive coding algorithms, native email threading, complex review team permissioning, and automated production export engines. * Limitations: Substantial monthly hosting fees, user seat licensing costs, and heavy administrative overhead. For mid-sized firms, boutique practices, or archived closed matters, storing terabytes of historical case data in an enterprise eDiscovery engine is economically unsustainable. ### 2. Traditional Cloud Document Management Systems Systems like NetDocuments and iManage serve as the primary document repositories for law firm administrative files, pleadings, and correspondence. * Strengths: Tight integration with Microsoft productivity suites, automated document versioning, matter-centric filing from Outlook, and enterprise document profiling. * Limitations: These platforms are document management tools, not litigation evidence platforms. They lack specialized capabilities for full-text transcript search across page and line coordinates, synchronized deposition video playback, and dynamic metadata extraction across heterogeneous discovery productions. ### 3. Intelligent Cloud Workspaces Intelligent cloud workspaces like Fast.io provide an agile, cost-effective alternative for litigation teams seeking to manage case files, transcripts, and evidence without enterprise eDiscovery overhead. Fast.io combines structured matter organization with native AI extraction and search. * Matter-Centric Organization: Create dedicated [shared workspaces](/product/workspaces/) for each client and matter, standardizing subfolders for pleadings, transcripts, exhibits, and productions. * Large-File Handling: Litigation files frequently exceed standard upload limits. Fast.io supports chunked uploads, enabling teams to transfer massive video depositions, forensic disk images, and large production archives without connection timeouts. * Native Video Streaming: High-definition deposition video recordings can be streamed directly in the browser via HLS video streaming, eliminating the need to download large multi-gigabyte video files to local workstations. * Auditability and Version Control: Every file maintains per-file version history and an append-only audit log, tracking exactly who accessed, downloaded, or updated case materials. * Automated Data Extraction with Metadata Views: Instead of manually typing Bates numbers, deponent names, and exhibit references into spreadsheets, firms can deploy [Metadata Views](/product/document-data-extraction/). Operations teams describe extraction targets in plain English, and the AI extracts structured fields (such as Bates Begin, Bates End, Document Date, Deponent, Exhibit Number, and Counterparties) into a live, queryable data grid. * Intelligence Mode for Case Materials: Enabling Intelligence Mode auto-indexes transcripts, motions, and evidence for semantic search. Attorneys can ask complex factual questions across all case files, receiving natural-language answers backed by page-level citations to the underlying transcripts. * Secure Client and Co-Counsel Delivery: Branded [shares](/product/sharing/) allow teams to send exhibit binders to expert witnesses or receive discovery productions from clients through branded, expiring upload links without relying on unencrypted email attachments. Fastio runs on cloud infrastructure partners, including Google Cloud Platform and Cloudflare, that are certified to industry-leading security standards. Case documents are protected by encryption in transit and at rest, paired with granular role-based permissions at the organization, workspace, folder, and file levels. ### Comparing Litigation Platform Categories The following table outlines how legacy desktop databases compare against modern alternatives across core operational dimensions: | Platform Category | Representative Systems | Primary Use Case | Transcript and Evidence Handling | Maintenance Overhead | |---|---|---|---|---| | Legacy Desktop Database | Summation iBlaze, Enterprise | Historical case management and transcript indexing | File-based TIFF linking, manual transcript digests | High; requires obsolete OS environments and local servers | | Enterprise eDiscovery | Relativity, Everlaw, DISCO | Multi-terabyte discovery processing and TAR review | Extensive review queues, redaction, production bates-stamping | High; specialized administrators and ongoing hosting fees | | Cloud Legal DMS | NetDocuments, iManage | Daily legal drafting, contracts, and email archiving | Standard folder search; no native deposition video streaming | Moderate; firm-wide IT configuration and user provisioning | | Intelligent Cloud Workspace | Fast.io | Active matter evidence rooms, transcript search, closed case archives | Semantic RAG search, automated Metadata Views, HLS video streaming | Low; browser-based deployment with self-serve workspaces | ## Step-by-Step Migration from Summation to an Intelligent Workspace Migrating a firm's legacy Summation catalog into an intelligent cloud workspace transforms stagnant archive files into an active, searchable repository. By following a structured migration plan, legal operations leads can preserve critical attorney work product while retiring legacy server infrastructure. ### Step 1: Inventory and Prioritize Case Databases Begin by scanning firm storage for all legacy Summation data. Identify whether each matter database was built in iBlaze or Enterprise. Categorize cases into active litigation, dormant matters with ongoing preservation obligations, and fully closed files eligible for permanent record archiving. Prioritize active and high-value matters for full conversion. ### Step 2: Extract Database Tables and Transcripts Use database export utilities to dump Summation tables into standard comma-separated CSV files. Ensure that custom coding columns, issue tags, and document notes are fully exported. In the transcript directory, verify that all verbatim transcript files are extracted and labeled with the correct witness names and deposition dates. ### Step 3: Batch Convert Image Load Sets to Searchable PDFs Process the load files and associated TIFF image folders: * Parse the document boundaries to group single-page images into unified documents. * Convert single-page TIFF files into multi-page PDF documents. * Apply optical character recognition or merge existing text files to produce searchable PDF assets. * Name each resulting PDF using a standardized format: BatesBegin_BatesEnd_DocumentDate_ShortTitle.pdf. ### Step 4: Establish a Matter-Centric Workspace Hierarchy Deploy a clean, matter-centric folder structure in your [cloud workspace](/product/workspaces/): ``` Client Matters └── Client_Name └── Matter_ID_Matter_Name ├── 01_Pleadings ├── 02_Transcripts ├── 03_Exhibits ├── 04_Productions └── 05_Work_Product ``` Place multi-page exhibit PDFs into the exhibits folder, deposition transcripts into the transcripts folder, and original production sets into the productions folder. ### Step 5: Configure Metadata Views for Case Documents Once files are uploaded, open [Metadata Views](/product/document-data-extraction/) to replace the old Summation spreadsheet grid. Describe the fields you want extracted in natural language: * Bates Begin and Bates End (Text) * Document Date (Date and Time) * Document Type (Text: Contract, Correspondence, Pleading, Deposition Exhibit) * Deponent or Author (Text) * Key Issue Tags (Text) The system automatically scans the ingested PDFs and populates a filterable data grid. Litigation teams can sort, filter, and search across thousands of case documents without configuring manual database fields. ### Step 6: Activate Intelligence Mode for Instant Fact Retrieval Enable Intelligence Mode on the workspace. Fast.io indexes all uploaded transcripts, exhibits, and pleadings for semantic search. Attorneys and paralegals preparing for trial can use natural-language queries to cross-examine testimony: * "What did the chief technical officer testify regarding the server outage?" * "Identify all exhibits where the defendant discussed licensing terms prior to contract execution." The system returns answers synthesized directly from case materials, providing clickable, page-level citations back to the source transcripts and exhibits. ### Preserving Attorney Work Product and Issue Coding The primary danger during any legal database migration is the loss of attorney work product. Documents can always be re-scanned, but the thousands of hours attorneys and paralegals spent tagging exhibits, writing transcript digests, and building case chronologies cannot be easily replaced. To preserve this investment: * Export Transcript Digests: Extract Summation's internal transcript summaries into structured CSV files. Map the deponent name, page number, line number, issue code, and attorney note into distinct columns. * Ingest Notes as Collaborative Documents: Upload transcript digests into Collaborative Notes within the matter workspace. This allows current litigation teams to review historical case summaries directly alongside active files. * Map Issue Tags to Metadata Views: Add custom issue columns to your Metadata View so that documents previously coded with specific tags (such as 'Notice', 'Breach', or 'Privileged') retain their classification in the modern workspace. ### Securing Matter Archives and Applying Access Controls Once legacy matters are safely migrated, administrators must secure the archives according to firm governance standards. Check with your firm's own counsel or records policy to determine whether specific jurisdictional rules dictate how long closed matter records must be retained. In Fast.io, administrators can apply read-only permissions to archived matter folders, preventing accidental modifications while keeping files instantly accessible for authorized staff. The append-only audit trail logs every query, download, and view, preserving an immutable chain of custody. When litigation teams need to collaborate with external experts or co-counsel, they can generate branded shares with expiring links and password controls. External parties receive access only to designated exhibit folders without gaining visibility into internal attorney notes or unrelated firm workspaces. ## Frequently asked questions ### What happened to Summation legal software? Summation evolved through several corporate acquisitions. Originally created by Summation Legal Technologies, the platform became CT Summation, was acquired by AccessData to combine with its FTK digital forensics suite, and was later acquired by Exterro. Standalone desktop Summation software is now considered legacy, as development shifted toward unified enterprise Legal GRC platforms. ### How do you access legacy Summation transcripts and case files? Accessing legacy Summation files requires extracting data directly from the case directory rather than relying on obsolete desktop executables. Document metadata can be exported from database tables to CSV, deposition transcripts can be opened with standard text processors, and single-page TIFF files can be stitched into multi-page searchable PDFs using their load files. ### What are the best modern alternatives to Summation for litigation teams? Modern alternatives depend on case size and budget. For massive, multi-party discovery and predictive coding, enterprise platforms like Relativity, Everlaw, and DISCO are standard. For daily practice document filing, cloud systems like NetDocuments or iManage are common. For agile litigation matter workspaces, exhibit repositories, transcript search, and automated metadata extraction, intelligent cloud workspaces like Fast.io offer a lightweight, cost-effective replacement. ### Can you convert Summation DII files to modern document formats? Yes. A DII file is a structured ASCII load file that uses tokens for document boundaries and image paths. Legal operations teams can parse DII files with conversion scripts or migration tools to identify page ranges, convert individual single-page TIFF images into unified multi-page PDFs, and merge OCR text into a modern searchable format. ### How do litigation teams preserve attorney transcript digests during migration? Litigation teams can preserve transcript digests by exporting the annotation tables from Summation into delimited CSV or text files before decommissioning the database. These exports capture deponent names, page and line numbers, issue codes, and attorney notes, which can then be imported into modern collaborative notes or structured metadata views in a cloud workspace. ## About Fast.io Fast.io provides shared workspaces where people and AI agents work on the same files, with built-in semantic search and citation-backed chat over what they hold. Agents reach it through a remote MCP server at https://mcp.fast.io/mcp, a REST API at https://api.fast.io/current/, and a command line client published on npm as @vividengine/fastio-cli.