Migrating Content To Hyland's OnBase since 2001

4matix validates every file by inspecting the actual binary content, not relying on legacy system-reported file types. Each document is checked to confirm it is truly a TIFF, PDF, JPEG, or other expected format before it is migrated.  This is very important when migrating to OnBase because your import files (DIP Files) have to have a file type designation.  This designation - if incorrect - will continually cause problems when trying to view these documents.

4matix has converted most mainstream document imaging and document management systems to OnBase.  These include the big ones like FileNet, ApplicationXtender, Unisys InfoImage, Stellent, Documentum, Laserfiche and many more.

We have also migrated specialty application like CGI Sovera (Healthcare) and ImageRight (Insurance).

Yes.  Though OnBase will accept either - some use cases demand multi-page TIFF.  We validate each import file (single page TIFF) - concatenate them into a multi-page TIFF and validate that as well.

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 system Document ID 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 legacy 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 has been delivering live annotation data into OnBase for a long time.  Annotation conversions are a specialty at 4matix and OnBase is a reliable destination for these data types.  Note that these annotations are not simply document level notes - but text, highlights, redactions, etc.

4matix decompresses legacy COLD data/files into native print streams which can be COLD processed into OnBase or stored as searchable text in the archive.  Statement data can often be broken into individual documents and DIPPED into OnBase.

Yes. 4matix can map legacy line-of-business data and external data sources into the migration, enriching documents with additional metadata required or requested in OnBase.  This data has included CORE banking data, ERP data, EMR data and sometimes just replacement data - say swapping a SSN for account number.

Corrupted or malformed files are flagged, isolated, and reported. This prevents bad data from contaminating the OnBase 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 OnBase and structured to be import ready – no massaging – no manipulation required to import.

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