Insights
Modernisation: upgrade without stopping the business
Most modernisation starts with a deadline: a framework losing support, a vendor leaving, a system only one person understands. This section covers the deadlines that are coming, the migration patterns that keep the business running, and how to take over a system nobody documented. Every date here is checked against the vendor's own lifecycle page.
Support deadlines to plan around
| Platform | Deadline | What to do |
|---|---|---|
| .NET 8 and .NET 9 | Support ends 10 November 2026 | Move to .NET 10 (supported to 14 November 2028) |
| Node.js 18 and 20 | Already end of life | Move to 22 or 24 LTS |
| AngularJS 1.x | End of life since 31 December 2021 | Migrate the front end |
| .NET Framework 4.8.x | Supported with Windows, no new features | Plan a path to modern .NET |
Start here
| If you are asking | Go to |
|---|---|
| Can AMT modernise our system? | Legacy application modernisation |
| We cannot afford downtime | Modernise without downtime |
| We need .NET developers now | Hire .NET developers |
Articles in this section
Coming soon
.NET 8 end of support: what to do before and after 10 November 2026
The upgrade path, what breaks, and the risk of staying
Coming soon
Node.js 20 is end of life: running it safely while you migrate
What end of life means in practice, and the upgrade order
Coming soon
Strangler fig or full rewrite: how to choose
A decision table built on risk, team size and how well the old system is understood
Coming soon
Taking over a system nobody documented: the first 30 days
What to read, run and write down before changing anything