Colour theme
Book a consultation

Moving a legacy site beyond Internet Explorer

Identify a legacy site's browser dependencies, test a supported destination and use managed IE mode only where the operating system and application support it.

A person using a laptop at a wooden table

A business website that still depends on Internet Explorer needs an application plan. Changing the default browser won’t be enough. Staff may rely on an old supplier portal, reporting tool or internal system whose dependencies haven’t been documented.

Microsoft’s browser lifecycle FAQ distinguishes the retired Internet Explorer 11 desktop app on affected Windows versions from IE mode in Microsoft Edge. IE mode support depends on a supported operating system; Microsoft’s commitment is through at least 2029.

Don’t interpret that as a guarantee that any old site or operating system remains supported.

Find the dependency

Ask users to demonstrate the complete task and record the site, supplier, sign-in method, downloads, printing and any browser-specific components.

Include infrequent work such as annual submissions or exports. A landing page opening successfully doesn’t show that the whole workflow works.

Check the supplier’s supported browsers and application lifecycle. Ask for a supported replacement or upgrade path where the old requirement remains.

Test a current browser first

Use test records and a supported browser on the intended operating system. Check the full transaction, attachments, reports and accessibility needs.

Record failures clearly for the supplier. Avoid disabling browser security broadly to make one page load.

Review extensions, saved credentials and downloaded components as part of the test. A browser change is a good time for IT to remove obsolete dependencies.

Scope IE mode where still needed

If the supplier and platform support IE mode for the legacy workflow, have IT manage the configuration for the required sites. Confirm what uses the legacy engine and what opens normally.

IE mode isn’t a general instruction to browse every website using old compatibility behaviour. Keep the exception narrow, owned and reviewed.

Don’t remove Windows components indiscriminately to uninstall Internet Explorer. Follow the supported vendor process and test the applications that depend on them.

Complete the user handoff

Provide a tested shortcut and short instructions. Check which favourites and settings should move; don’t assume every item transfers automatically or that saved credentials should be copied across.

Keep a support route for staff when a site changes. Plan how the business will move away from the remaining dependency before its supported route ends.

Our application development work can help assess an internal legacy application and define a replacement that preserves the business workflow.


Featured Image Credit