HighEdit was used for many years as a document editing and reporting technology in business and healthcare applications. Even though HighEdit itself is no longer an actively developed product, many organizations still depend on documents created with it.
These files are typically stored in the proprietary HED document format.
For organizations modernizing a legacy application, replacing an EHR, consolidating systems, or decommissioning old infrastructure, this creates an important question:
What should happen to the existing HED documents?
The answer depends on how the documents are still being used.
Some should be preserved as long-term archive documents. Others may need to remain editable. Some may contain information that needs to be extracted and transferred into a new system.
With HEDBridge, organizations can convert and process existing HighEdit HED files without maintaining the original HighEdit application indefinitely.
Why Discontinued Document Formats Are a Risk
A proprietary document format is usually convenient while the application that created it is still available.
The application knows where the file is stored, understands the file format, and can render the document for the user.
The problem becomes visible when that application is replaced.
The HED files may still exist on a file server, backup system, or archive, but modern applications cannot necessarily open them directly.
This creates a dependency on discontinued software.
Over time, that dependency can become harder to maintain because the original environment may rely on:
- Older Windows versions
- Legacy application frameworks
- Unsupported databases
- Old hardware
- Deprecated libraries
- Application-specific integrations
- Software that is no longer maintained
The documents themselves may still be perfectly valid, but accessing them becomes increasingly difficult.
The First Step: Understand What You Have
Before converting anything, determine what is stored in the existing HighEdit environment.
A repository may contain more than one type of HED document.
Typical examples include:
- Completed reports
- Historical correspondence
- Patient letters
- Clinical documents
- Invoices
- Forms
- Templates
- Internal documents
- Generated reports
- Editable working documents
Not all of these should necessarily be migrated in the same way.
A completed document from ten years ago has different requirements from a template that is still used to generate new documents today.
The migration strategy should therefore begin by categorizing the archive.
Option 1: Convert Historical HED Files to PDF
For documents that are complete and no longer need to be edited, PDF is usually the most practical target format.
This includes documents such as:
- Historical letters
- Completed reports
- Archived patient documents
- Signed or finalized forms
- Invoices
- Correspondence
PDF makes these documents accessible without requiring the original HighEdit technology.
It can be opened in modern browsers, desktop applications, document management systems, EHR platforms, and archive systems.
For organizations that mainly need to preserve the original visual representation of a document, PDF is often the simplest migration path.
Option 2: Convert HED Files to PDF/A for Long-Term Archiving
If the documents are intended for long-term retention, organizations may prefer PDF/A.
PDF/A is specifically designed for electronic document preservation.
This makes it particularly relevant when migrating:
- Healthcare records
- Legal archives
- Government records
- Financial documents
- Compliance documents
- Historical business records
Converting HED documents to PDF/A removes the dependency on HighEdit while creating files intended for reliable long-term access.
Option 3: Convert HED Files to DOCX
Not every document should become a read-only archive.
Some HED files may still need to be edited after the migration.
Examples include:
- Letter templates
- Report templates
- Standard forms
- Reusable documents
- Documents used as starting points for new content
In these cases, DOCX may be a better target format.
DOCX is widely supported and can be used by many modern document processing applications.
Converting HED files to DOCX can therefore help organizations retain editable content while moving away from the discontinued HighEdit format.
Option 4: Move from HighEdit to TX Text Control
For software vendors and organizations modernizing an application rather than simply archiving documents, TX Text Control can provide a natural successor technology.
TX Text Control supports modern document processing scenarios including:
- Document editing
- Document generation
- Reporting
- Mail merge
- DOCX processing
- PDF creation
- Server-side document processing
- Web-based document editing
Existing HED documents can be converted as part of the migration while the application itself is moved to a modern document processing architecture.
This provides a path away from HighEdit without losing access to the historical document repository.
Option 5: Extract Information from HED Documents
Sometimes the goal is not simply to preserve the original document.
A migration may need to extract information from the HED files so that it can be indexed, searched, analyzed, or imported into another application.
For example, organizations may need to:
- Extract plain text
- Identify document content
- Create searchable archives
- Move information into another database
- Build migration metadata
- Analyze large legacy repositories
HEDBridge can therefore be used not only as a file converter, but also as part of a broader document migration and extraction workflow.
Do Not Assume the Database Contains Everything
This is particularly important in legacy enterprise and healthcare applications.
A database migration may successfully transfer structured information while formatted documents remain in separate HED files.
For example, the database might contain:
- Patient IDs
- Document IDs
- Dates
- Document categories
- Encounter information
- Storage paths
The actual formatted content may still be stored in an HED document on a file server.
Migrating only the database can therefore leave part of the historical record behind.
A complete migration should include both the structured data and the associated documents.
Preserve the Relationship Between Files and Records
The filename of an HED document may not be meaningful to a user.
A repository might look like this:
004928375.hed
004928376.hed
004928377.hed
004928378.hed
The corresponding application database may contain the information required to determine which patient, customer, case, or transaction each document belongs to.
During conversion, it is important to preserve this relationship.
For example:
004928375.hed -> 004928375.pdf
004928376.hed -> 004928376.pdf
004928377.hed -> 004928377.pdf
Migration software can then use the existing identifier to associate the converted file with the corresponding record in the destination system.
Large HighEdit Archives Require Batch Processing
A legacy repository can easily contain hundreds of thousands of documents.
Manual conversion is not practical at that scale.
A migration tool should therefore support automated batch processing so that complete directories or archives can be converted systematically.
HEDBridge is designed for these scenarios.
A batch conversion process can:
- Locate HED files.
- Convert each file into the required target format.
- Preserve filenames or document identifiers.
- Record successful conversions.
- Log failures.
- Continue processing the remaining archive.
- Retry problem documents separately.
This is significantly more reliable than manually opening and exporting individual files.
For a local batch run, use the HEDBridge console with a separate source and destination folder:
HEDBrigde.exe /s:D:\Legacy\HED /d:D:\Migration\PDF /f:pdf --recursive --continue-on-error
If the migration also needs document metadata for reconciliation, extract ApplicationFields to a separate audit folder:
HEDBrigde.exe /s:D:\Legacy\HED --extract-fields --recursive /d:D:\Migration\Audit
Test a Representative Sample First
Before converting an entire archive, select a representative group of documents.
Include documents from different:
- Years
- Departments
- Document types
- Templates
- Application versions
- Storage locations
Then verify the results carefully.
Important areas include:
- Text
- Tables
- Fonts
- Images
- Headers and footers
- Page breaks
- Pagination
- Special characters
- Document dimensions
This helps identify unusual documents before processing the complete repository.
Keep the Original HED Files During the Migration
A conversion project should generally avoid deleting the source documents immediately.
Keeping the original HED archive during the migration provides a reference if:
- A conversion fails
- A document needs to be compared
- Metadata mappings are incorrect
- A different output format is required later
The organization can decide how long to retain the original files based on its own retention policies and migration requirements.
The important point is that the legacy files should not be the only way to access the documents.
Plan the Migration Before Decommissioning HighEdit
The best time to analyze and convert HED documents is while the legacy application is still available.
At that stage, the organization can still answer important questions such as:
- Where are the HED files stored?
- How are they referenced by the database?
- Which documents are templates?
- Which documents are historical?
- Which files are still actively used?
- Are there multiple repositories?
- Are there different generations of HED files?
- Which metadata must be preserved?
Once the original application is removed, recovering this information can become significantly more difficult.
HEDBridge as a Migration Path from HighEdit
HEDBridge is designed to provide access to documents created with HighEdit after the original technology has reached the end of its lifecycle.
Depending on the migration scenario, HED documents can be converted to modern formats including:
- DOCX
- RTF
- TXT
- HTML
- TX Text Control compatible formats
The console produces standard PDF files. When PDF/A is required for retention, validate or normalize those PDFs with the organization's approved archival tool after conversion.
HEDBridge can also be integrated into batch migration workflows where large document repositories need to be processed locally.
This is particularly useful when documents contain sensitive information that should not be uploaded to external conversion services.
Replace the Dependency, Not the Documents
A discontinued document technology does not mean that the documents created with it have lost their value.
Historical documents may need to remain accessible for many years after the original application has been replaced.
The goal of a HighEdit migration should therefore be to remove the dependency on the legacy technology while preserving the documents themselves.
For most organizations, that means using a combination of:
- PDF or PDF/A for historical documents
- DOCX for editable documents
- TX Text Control for modernized applications
- Data extraction when document content needs to be migrated or indexed
HEDBridge provides the connection between the legacy HighEdit archive and these modern document workflows.
The earlier this conversion is included in the migration plan, the easier it becomes to retire the original HighEdit environment without losing access to important documents.