Data Conversions FROM OnBase

4matix validates every file by inspecting the actual binary content, not relying on OnBase-reported file types. Each document is checked to confirm it is truly a TIFF, PDF, JPEG, or other expected format before it is migrated.

No. OnBase metadata is treated as advisory. 4matix verifies the underlying file structure of every document to prevent corrupted, mislabeled, or unreadable files from entering the target system.

Legacy .IMG files are inspected, validated, and converted into standard image formats while preserving page order, metadata, and associated annotations.

Multi-Instance Keyword Groups (MIKGs) allow OnBase to associate multiple related sets of keywords with a single document. They preserve the relationship between repeated data elements, such as multiple borrowers on a loan document.

MIKGs preserve relational metadata. If they are flattened or improperly mapped during migration, critical relationships—such as borrower-to-address or borrower-to-SSN—can be lost or corrupted.

4matix calculates MD5 hashes for every file and verifies those hashes at each stage of the migration. This ensures that every document remains unchanged from extraction through final ingestion.  4matix also migrates the legacy OnBase Document Handle (Item number) to ensure all required documents are successfully imported into the new solution.

4matix uses a backup of the application database and converts the files directly from the filesystem taking the OnBase application out of the equation.

Yes. 4matix migrations are defensible because file integrity is cryptographically verified, field mappings are documented, and validation results are repeatable. This approach meets evidentiary standards for data authenticity.

Yes. 4matix converts OnBase annotation data into formats that are compatible with modern ECM platforms, preserving markup and context rather than flattening or discarding annotations.

4matix decompresses OnBase COLD data (CTX Files) into native print streams which can be COLD processed into a new modern ECM or stored as searchable text in an archive.

Yes. Large print streams (often statement data) can be programmatically segmented into discrete documents, allowing each record to be indexed, validated, and migrated individually.

Yes. 4matix can map legacy line-of-business data and external data sources into the migration, enriching documents with additional metadata required by the target ECM.

Corrupted or malformed files are flagged, isolated, and reported. This prevents bad data from contaminating the target system and provides a documented exception process.

4matix applies automated validation to every file and supplements it with document level reconciliation reports to confirm completeness and accuracy.

4matix treats migrations as data conversion projects, not simple exports. Every file is verified, hashed, validated, and normalized before ingestion, ensuring accuracy, compliance, and long-term usability. Deliveries from a 4matix migration are batched for ingestion into the new ECM and structured to be import ready – no massaging – no manipulation required to import.

Exports from OnBase don’t create live annotation or import ready files and for many customers, require another conversion to be usable with their new ECM.  See our Export FAQ here.