End of support is a vendor lifecycle decision. An older interface, an acquisition, a remote support team or an expensive renewal does not by itself prove that a product has reached end of life. Ask for the published lifecycle policy for your exact product and version.
1. Support dates
Confirm when standard and extended support end and which services each includes. Record the source and applicable contract.
2. Security updates
Check supported versions, patch delivery and unresolved vulnerabilities with your IT owner. CISA identifies unsupported software as a security risk because vulnerabilities may no longer be patched; this does not establish that a particular vendor is unsupported.
3. Incident response
Compare incident history, contractual response commitments and actual recovery evidence. Do not assume a cloud product has a particular uptime guarantee.
4. Everyday usability
Observe users completing real tasks, including keyboard access and error recovery. Distinguish a usability issue from a support lifecycle issue.
5. Records and exports
Test representative exports, version information, access and retrieval. Confirm how you would retain evidence after leaving the system.
6. Migration requirements
Request a documented migration plan, responsibilities, validation steps and rollback method. A proposed replacement is a reason to ask questions, not proof of bad intent.
7. Commercial changes
Compare renewal terms, included services, licence scope and switching costs. Percentage increases alone do not establish product support status or misconduct.
Illustrative workflow: make the decision
Bring the lifecycle policy, incident evidence, task observations and migration test to a joint quality, IT and finance review. Decide whether to keep, remediate or replace the system using documented criteria. Plan continuity before retiring it.
Reference and next step
CISA and NSA cybersecurity misconfiguration advisory ↗
Use the QMS software evaluation guide, estimate a plan or discuss your process with Qlutch.

