Checking six legacy technology dependencies
Review six legacy browser, operating-system and database dependencies with current vendor guidance, ownership and a tested migration plan.

An old tool can keep working after its ordinary support ends. That makes it easy to overlook until an application change, failed device or security advisory forces a decision.
Review the exact product and its dependencies before removing or upgrading it. These six checks cover tools named in older technology inventories; they aren’t a complete list of unsupported systems.
1. Internet Explorer dependencies
Distinguish the retired desktop application on affected Windows versions from managed IE mode in Microsoft Edge. Support depends on the operating system and the application’s requirements.
Use the legacy browser migration guide to identify the workflow and test a supported destination. If the home page opens, test reports, uploads and transactions too.
2. Adobe Flash Player
Adobe’s end-of-life notice confirms that Flash Player is no longer supported and recommends uninstalling it.
Check for dependent training content, internal tools and vendor applications. Find a supported replacement. Don’t install a browser plugin from an unofficial download site to revive old content.
3. Windows 7 and other retired Windows versions
Windows 7 and 8.1 no longer receive security updates, and Windows 10 support ended on October 14, 2025. Treat any of these as a legacy system that needs a support review. Record the edition, hardware, connected equipment and software that prevents migration.
Agree on a supported destination with the application supplier. For most businesses that means Windows 11 on hardware that meets its requirements. Our Windows migration guide covers planning the transition.
4. Older macOS installations
Apple doesn’t publish end-of-support dates for macOS. Its security releases page shows which versions are still getting fixes, so check each Mac’s model and installed version against it.
Confirm the business applications run on a supported version, and plan to replace a Mac that can’t run one.
5. Oracle database releases
Have the database owner check the release, deployment and contracted support against Oracle’s lifetime support policy.
Premier, Extended and Sustaining Support each cover patches differently. Don’t reuse old forecasts for 18c, 19c or 21c as current deadlines. Confirm the available upgrade path with the application supplier and database administrator.
6. SQL Server 2014
Microsoft’s Extended Security Updates FAQ records the end of ordinary extended support on July 9, 2024. Eligible ESU arrangements can provide limited security updates through July 8, 2027.
Verify entitlement and delivery for your deployment. ESU is temporary and limited to security fixes, so plan the migration alongside it.
Plan the change around the business task
For each dependency, record the owner, supported destination, records to preserve, test cases and rollback route. Include integrations, access, printing and scheduled jobs.
Test recovery before changing a production system. Set a review date for any temporary exception and make the remaining risk visible to the person who decides on the replacement.


