DocStar Migration - Merkh LLC

System Overview

DocStar is an ECM platform often used for accounts payable automation, document management, and workflow routing. Now part of the Epicor ecosystem, DocStar offers web-based access to document repositories, automated capture and classification, and configurable workflow rules that streamline business processes.

DocStar is popular with mid-market manufacturing, distribution, and retail organizations that use Epicor ERP. The platform's tight integration with Epicor allows AP invoices, purchase orders, and shipping documents to flow directly into DocStar for indexing, approval routing, and archival.

Specific Technical Challenges

DocStar's variable storage architecture and deep Epicor ERP coupling make extraction far more involved than a straightforward database export.

BLOB vs. File System Storage Variance

Content is stored in SQL Server with BLOBs or as file system references depending on the version and configuration. The extraction approach differs significantly between the two, and some installations use a mix of both storage methods.

Per-Installation Custom Field Schemas

Custom fields use a flexible schema that varies per installation. No two DocStar deployments have the same field structure, so every migration requires a unique discovery phase to map the specific field definitions in use.

Bidirectional Epicor ERP Links

Epicor ERP integration stores cross-reference data in both DocStar and Epicor databases. Migrating only the DocStar side breaks the link, leaving Epicor pointing to documents that no longer exist in the expected location.

Three-Way Match Audit Data

AP automation workflows contain three-way match data linking purchase orders, receipts, and invoices with line-item detail. This matching data must be preserved for audit purposes and does not export through standard document retrieval.

GUID-Based Category Hierarchies

Category hierarchies and folder structures use internal GUIDs that do not resolve to human-readable paths without database lookups. Reconstructing the visible folder tree requires traversing GUID references across multiple tables.

Separate Audit Trail Tables

Audit trail entries are stored in a separate table with foreign keys to documents that must be explicitly extracted. Skipping the audit table means losing the complete history of who accessed, modified, or approved each document.

How Merkh Helps

Precision navigates the challenges of DocStar migration by determining the storage method in use, mapping the per-installation field schema, and extracting documents with their full metadata context including audit trails and AP matching data. We reconstruct GUID-based folder hierarchies into human-readable structures and map Epicor integration references so that ERP-to-document links survive the migration. Our team has worked with DocStar environments ranging from small AP automation deployments to large multi-department installations, delivering reconciled output packages ready for the target platform.

DocStar Migration Experts