Reference Guide

RightFax version
lifecycle and EOL dates.

Many organizations discover they are running unsupported RightFax versions only after something breaks. This reference covers every version from 16.2 through 25.4, its sustaining maintenance date, and what that date actually means for your environment.

End of Life
Expiring Within 12 Months
Supported
Current Release

Version Status

Support lifecycle reference

Based on OpenText published lifecycle data. Sustaining maintenance marks the date after which the version receives no new patches, security fixes, or vendor support. Current date used for status calculation: July 2026.

Version Release Date Sustaining Maintenance Date Status Support Window
RightFax 25.4 October 2025 November 2030 Current Release
Oct 2025Nov 2030
RightFax 24.4 November 2024 November 2029 Supported
Nov 2024Nov 2029
RightFax 23.4 December 2023 December 2028 Supported
Dec 2023Dec 2028
RightFax 22.2 June 2022 June 2027 Supported
Jun 2022Jun 2027
RightFax 21.2 August 2021 August 2026 Expiring Aug 2026
Aug 2021Aug 2026
RightFax 20.2 April 2020 April 2025 End of Life
Apr 2020Apr 2025
RightFax 16.6 May 2019 May 2024 End of Life
May 2019May 2024
RightFax 16.4 July 2018 July 2023 End of Life
Jul 2018Jul 2023
RightFax 16.2 May 2017 May 2022 End of Life
May 2017May 2022
Source Note
Version dates sourced from the OpenText Product Lifecycle page at opentext.com/lifecycle and supplemented with OpenText release documentation. Sustaining maintenance marks the transition from full support to a limited maintenance state where no new patches or security fixes are issued. Organizations on versions past this date should treat their RightFax environment as unpatched infrastructure.

Risk Assessment

What running EOL RightFax
actually means

The end of life date is not a suggestion or administrative formality. It marks the point at which your fax infrastructure stops receiving security patches, and where vendor support for critical failures becomes unavailable. The practical consequences are significant for organizations in regulated industries.

Security
Unpatched Vulnerabilities Accumulate
Once a version reaches sustaining maintenance, OpenText no longer issues security patches for it. Vulnerabilities discovered after that date remain permanently unaddressed. RightFax handles sensitive document transmission in healthcare and financial environments where this exposure carries direct regulatory consequences.
Support
Vendor Support Is Unavailable
When a critical failure occurs on an EOL version, OpenText support will not assist with resolution on that release. What would be a routine support case on a current version becomes a high-pressure internal recovery effort. In environments where fax uptime is tied to patient care or regulated transaction workflows, this is a meaningful operational risk.
Compatibility
OS and Infrastructure Drift
Legacy RightFax versions were certified against operating systems and SQL Server versions that have themselves reached end of life. As the environment around an EOL RightFax installation continues to be updated, compatibility issues compound. Certificate changes, TLS version requirements, and OS patches can each introduce instability in an unsupported RightFax version.
Compliance
Regulatory Audit Exposure
PHIPA, PIPEDA, HIPAA, and most financial services regulatory frameworks require organizations to maintain supported, patched software stacks. Running EOL infrastructure is a documented finding in compliance audits. In environments subject to annual audits or external assessments, an unsupported RightFax installation represents a finding that requires a remediation plan.

Planning Guidance

Upgrading on your terms
versus under pressure

The operational reality of RightFax upgrades is that they are not simple version bumps. Depending on the source version, direct upgrades to current releases may not be possible, and the migration of fax data, user configurations, and integration connections requires planning time that an emergency transition does not allow.

Key Planning Considerations
Lead time matters. Organizations running versions approaching EOL should begin planning 6 to 12 months ahead of the sustaining maintenance date. The planning window needs to account for procurement of the new license, infrastructure readiness, testing in a non-production environment, and scheduling a maintenance window that works around business-critical fax workflows.

Direct upgrade paths are not always available. Very old versions often require intermediate staging servers to migrate the database schema through supported upgrade steps before reaching the current release. This adds time and infrastructure requirements that cannot be improvised during an emergency. See our knowledge base article on legacy upgrade planning for the staging server approach.

RightFax 21.2 reaches sustaining maintenance in August 2026. Organizations running 21.2 who have not yet initiated upgrade planning are in the narrow window where a controlled transition is still achievable before the version expires.

Ready to Plan

Need a migration roadmap for your version?

We scope RightFax upgrade engagements based on your current version, environment complexity, and business timeline. Whether you are planning ahead or dealing with an expiring version now, we can map the path forward and execute it.

Start Engagement → View Knowledge Base
25+
RightFax Deployments
Sr.
Engineer on Every Engagement
GTA
Ontario and Canada Wide
Zero
Downtime Focus