Converting a single legacy HighEdit HED document is straightforward.
Converting 500,000 HED documents from a production archive is a completely different type of project.
Large HighEdit migrations require automation, traceability, error handling, and a strategy for reconnecting converted files with the records in the original system.
HEDBridge is designed for these batch conversion scenarios.
Why HighEdit Archives Can Become Very Large
Enterprise and healthcare applications can remain in operation for decades.
If an application generates only a few hundred documents per day, the archive can eventually contain hundreds of thousands or millions of files.
A legacy repository might contain:
00000001.hed
00000002.hed
00000003.hed
...
00984217.hed
Manually opening and exporting these documents is impossible at this scale.
The conversion process must be automated.
Start by Understanding the Repository
Before beginning a batch conversion, determine how the existing document storage works.
Questions to answer include:
- How many HED files exist?
- Are they stored in one directory or many?
- Are files distributed by year or patient?
- Are filenames unique?
- Does the database store absolute or relative paths?
- Are there duplicate files?
- Are templates mixed with completed documents?
- Are all files actually HED documents?
Understanding the archive before processing it prevents many migration problems later.
Choose the Right Target Format
A batch migration does not necessarily mean that every document should have the same output format.
Typical choices include:
- PDF for completed documents
- PDF/A for long-term archives
- DOCX for editable documents
- TX Text Control compatible formats for application modernization
- HTML or RTF for specialized workflows
For a large archive, classification rules can be derived from document metadata or database records.
Preserve File Identifiers
One of the simplest migration strategies is to keep the document identifier unchanged.
For example:
1837291.hed
becomes:
1837291.pdf
The extension changes, but the underlying identifier remains the same.
This can make it much easier to update database references or import documents into the destination system.
Build a Repeatable Conversion Process
A batch conversion should be repeatable.
If processing is interrupted or migration requirements change, the team should not need to start again manually.
A robust workflow can follow these steps:
- Enumerate source HED files.
- Determine the required target format.
- Convert each document.
- Write the output file.
- Record the conversion result.
- Continue with the next file.
- Collect failures for later review.
This allows the archive to be processed systematically.
Log Every Conversion
Logging is critical when processing large document collections.
A migration log might contain:
Source: 1837291.hed
Output: 1837291.pdf
Status: Success
Source: 1837292.hed
Output: 1837292.pdf
Status: Success
Source: 1837293.hed
Status: Failed
Reason: Invalid document
At the end of the migration, the team should be able to answer:
- How many files were discovered?
- How many were converted?
- How many failed?
- Which files failed?
- Which output files were created?
Without this information, proving that a large archive was completely migrated becomes difficult.
Run a Batch Conversion from the Console
The HEDBridge console can process a complete folder without opening the desktop application. Use --recursive for nested folders and --continue-on-error so one damaged document does not stop the migration:
HEDBrigde.exe /s:D:\Archive\HED /d:D:\Archive\PDF /f:pdf --recursive --continue-on-error
If the destination must contain one flat list of files, add --flat:
HEDBrigde.exe /s:D:\Archive\HED /d:D:\Archive\PDF /f:pdf --recursive --flat --continue-on-error
Run HEDBrigde.exe --license before a migration to confirm that the machine has a valid trial or paid token.
Do Not Stop the Entire Batch for One Bad File
Large historical archives can contain unexpected files.
A document may be:
- Corrupted
- Incomplete
- Zero bytes
- Incorrectly named
- Created by a different application
- Damaged during an earlier storage migration
A single problem file should normally not stop processing of the remaining archive.
Instead, record the failure and continue.
Failed documents can then be investigated separately.
Validate More Than the File Extension
Successfully creating a PDF does not automatically prove that the migration is correct.
Validation should include representative document checks.
Verify:
- Text content
- Page count
- Tables
- Images
- Fonts
- Headers and footers
- Special characters
- Pagination
- Document dimensions
For very large archives, automated validation can be supplemented with manual review of representative samples.
Process a Pilot Batch First
Do not begin with the complete production archive.
Select a representative pilot group containing documents from:
- Different years
- Different application versions
- Different document types
- Different departments
- Different templates
A pilot batch can reveal problems while the scope is still manageable.
Only after the conversion strategy has been validated should the complete archive be processed.
Keep Source and Destination Separate
Use separate locations for source and converted documents.
For example:
/archive/highedit/source/
/archive/highedit/pdf/
Avoid overwriting or deleting the original HED files during the initial conversion.
Keeping source and destination separate makes troubleshooting and validation easier.
Consider Storage Requirements
Large conversions can require significant temporary and permanent storage.
If an archive contains millions of files, calculate available disk space before beginning.
Consider:
- Source archive size
- Output archive size
- Temporary storage
- Log files
- Backup requirements
- Validation copies
Storage planning is part of the migration process.
Reconnect the Converted Files to the Database
The document repository often works together with a database.
A database record might contain:
DocumentId: 1837291
PatientId: 38291
FilePath: archive/1837291.hed
After conversion, the migration can update or transform the reference:
DocumentId: 1837291
PatientId: 38291
FilePath: archive/1837291.pdf
Alternatively, the destination EHR or document management system may import the file and store it under a completely new identifier.
Either way, the relationship between record and document must be preserved.
On-Premises Batch Conversion
Large legacy archives often contain confidential information.
Healthcare repositories in particular may contain protected patient information.
HEDBridge can process the documents locally instead of requiring them to be uploaded to an external online conversion service.
This allows the conversion workflow to remain within the organization's own infrastructure.
HEDBridge for Large Migration Projects
HEDBridge supports conversion of HighEdit documents into formats including:
- DOCX
- RTF
- TXT
- HTML
- TX Text Control compatible formats
The console creates standard PDF files. If the archive requires PDF/A, validate or convert the generated PDFs with the organization's approved PDF/A tool and retain that validation result with the migration log.
This makes it suitable for migration projects where entire HighEdit repositories must be moved into a modern document environment.
Treat the Conversion Like a Data Migration
A bulk HED conversion is more than a file format operation.
At enterprise scale, it should be treated like a structured migration project.
Inventory the source.
Preserve identifiers.
Log every result.
Validate representative documents.
Keep failed files traceable.
Maintain the connection to database metadata.
With this approach, even very large HighEdit archives can be systematically converted without depending on manual processing or the continued availability of the original HighEdit environment.