Alchemy Migration - Merkh LLC

System Overview

Alchemy by OpenText, originally known as Alchemy UNITE, is a legacy document management system that was widely adopted in the late 1990s and early 2000s. The platform provided organizations with electronic document storage, indexing, retrieval, and basic workflow capabilities. Alchemy stores its content in a proprietary file structure that combines database-driven metadata with blob-based file storage.

Document libraries are organized into databases, each containing folders, subfolders, and individual documents with associated index values. While Alchemy served organizations well for many years, OpenText has shifted its focus to newer platforms, and vendor support for Alchemy has become increasingly limited. Many organizations still running Alchemy face aging infrastructure and compatibility challenges with modern operating systems.

Specific Technical Challenges

Alchemy's age, proprietary storage format, and lack of modern tooling make it one of the most technically demanding legacy platforms to extract data from.

Database-Embedded BLOB Storage

Alchemy writes document content directly into the database as binary objects rather than to the file system. Extraction requires reading BLOBs directly from SQL and reassembling them into their original file formats at the binary level.

Recursive Hierarchy Reconstruction

The cabinet and folder hierarchy uses internal IDs with no external reference table. Reconstructing the full folder tree requires recursive database traversal, walking parent-child relationships from root to leaf.

End-of-Life Infrastructure Dependencies

Many installations run on end-of-life SQL Server versions such as SQL Server 2000 or 2005 with deprecated data types. The platform itself has limited documentation, and finding technical references for the database schema is increasingly difficult.

Undocumented Annotation Format

Annotation data, if present, uses a format that is no longer documented by any current vendor. Parsing these annotations requires reverse engineering the binary format to extract stamp positions, redaction coordinates, and highlight regions.

No Supported API or Export Utility

No supported API or export utility exists for modern extraction. Everything must be done at the database level through direct SQL queries, making the extraction process entirely dependent on understanding the proprietary schema.

Legacy Character Encoding Issues

Character encoding issues are common when migrating from legacy Alchemy databases that predate Unicode support. Index values and file names may contain garbled characters that must be detected and corrected during extraction.

How Merkh Helps

Precision has deep experience working with Alchemy environments at the database level, including SQL Server 2000 and 2005 instances that most vendors will not touch. We understand how Alchemy stores documents as proprietary BLOBs, how the schema maps index fields to documents, and how folder hierarchies are represented internally. Our team performs direct database extraction to reconstruct folder trees, reassemble binary BLOBs into original file formats, and resolve character encoding issues. For environments where the Alchemy client is no longer functional, we work directly with database backups and produce clean output packages for your target platform.

Alchemy Migration Experts