Fortis Migration - Merkh LLC

System Overview

Fortis is a legacy document imaging and management platform that was widely deployed in the late 1990s and 2000s, particularly in insurance, financial services, and government agencies. The system was designed for high-volume document capture and archival, with a focus on scanned image storage and rapid retrieval via indexed fields.

Fortis stores documents in its proprietary MAG (Magazine) file format—a compressed archive container that bundles multiple document pages together with internal offset tables and index pointers. The platform uses a SQL-based index database to map document metadata to MAG file locations, and documents are retrieved by reading specific byte offsets within the MAG container. This architecture was efficient for the hardware constraints of its era but creates significant extraction challenges today.

With no active vendor support, no modern API, and a dwindling pool of professionals who understand the platform, organizations still running Fortis face an urgent need to extract their content before the institutional knowledge required to do so disappears entirely.

Specific Technical Challenges

Fortis presents some of the most difficult extraction challenges in the legacy ECM space, primarily due to its proprietary MAG file format and the near-total absence of documentation or vendor support.

Proprietary MAG File Format

The MAG (Magazine) file is a proprietary compressed archive that packs hundreds or thousands of document pages into a single binary container. There is no public specification for the format. Each MAG file contains an internal offset table that maps page sequences to byte positions within the file. Extracting individual documents requires parsing these offsets, decompressing the page data, and reassembling multi-page documents in the correct order—all without vendor tools or documentation.

MAG Compression Variants

Different versions of Fortis used different compression algorithms within MAG files. Early versions used a proprietary LZ-variant compression, while later versions switched to modified CCITT Group 4 for TIFF images. A single Fortis installation that was upgraded over the years may contain MAG files using multiple compression formats, and the extraction tool must detect and handle each variant correctly or the output will be corrupted.

Database-to-MAG Pointer Integrity

The SQL index database stores pointers (volume, MAG file name, byte offset, page count) that reference specific locations within MAG files. Over years of operation, database maintenance, backup restores, and volume reorganizations, these pointers can become misaligned. When a pointer is off by even a single byte, the extracted page is garbage. Validating and correcting pointer integrity across millions of records is a prerequisite to any extraction.

Multi-Volume MAG Storage

Fortis archives were typically written to optical platters, tape, or network volumes in a sequential fill pattern. When one volume filled, Fortis moved to the next, but the volume mapping table is stored only in the database. If volumes were relabeled, moved to different drives, or archived to tape without updating the database, the mapping breaks and documents become unreachable without manual volume-by-volume reconciliation.

No Export Utility or API

Fortis shipped with no bulk export tool and no API. The only way to retrieve documents was through the Fortis desktop client, one document at a time. For organizations with millions of documents, manual retrieval is not feasible. Extraction must be performed by directly reading the MAG files and SQL database, which requires reverse-engineered knowledge of the internal format.

Legacy Infrastructure Dependencies

Many Fortis installations still run on Windows Server 2003 or older, with SQL Server 2000 or MSDE databases. The storage hardware may include SCSI-attached optical drives or proprietary WORM devices that require specific drivers no longer available on modern operating systems. Simply accessing the data often requires standing up a legacy environment first.

How Merkh Helps

Precision has built custom extraction tooling that reads Fortis MAG files directly, handles all known compression variants, and validates byte-offset pointer integrity against the SQL index database before extracting a single page. We reconcile multi-volume mappings, reassemble multi-page documents in the correct sequence, and produce clean output packages (PDF, TIFF, or native format) with full metadata ready for import into your target platform. For installations running on end-of-life infrastructure, we work with your team to image the legacy environment and perform extraction in a controlled setting without risking the original data.

Fortis Migration Experts