8.13 getting EOL'ed with ~1 month of notice

[DennisHermannsen]

We've deliberately remained on WHMCS 8.13 due to the numerous issues with version 9.

We've been closely monitoring the WHMCS End of Life (EOL) schedule, where the end-of-support date for version 8.13 has been listed as "TBD" for a long time.

When I checked the page today, I was genuinely shocked to discover that the status had changed: support for WHMCS 8.13 is now scheduled to end on December 1, 2026 - roughly one month from now.

I checked the page earlier this month, and the date was still listed as TBD. Furthermore, the latest available snapshot on the Internet Archive, dated September 30, 2026, confirms that the status was still TBD at that point.

Announcing the end of support for a major software version with only around one month's notice is completely unreasonable. This is particularly concerning given the significant issues that still remain with WHMCS 9, which are precisely why we've continued to run version 8.13 in the first place.

Customers need adequate notice to plan, test, and execute a major upgrade - especially when the proposed upgrade path involves a version that continues to present substantial problems. Changing the EOL status from "TBD" to a firm date so close to the deadline, without meaningful advance notice, is simply unacceptable.

 

[websavers]

I came here to mention this very same thing. Given the significant number of problematic changes in 9.x AND that 9.1 was only released 10 days ago, this is an unreasonable expectation. 

If the WHMCS devs had done a better job preparing 9.x such that there weren't endless bugs reported for months after, I can see this being more reasonable. However that's not how things panned out. 

I also would like to request that WHMCS 8.13 remain actively supported until at minimum your planned release date for WHMCS 9.2 so that your customers can feel more comfortable with the 9.x upgrade prior to ending support for 8.x. I would estimate that this would be June 2027.

[bear]

Wild guess it's related to the new forced marketplace accounts requirement, and not worth their time to backport it.