All posts
Nov 12, 2026·engineering·7 min read

Angular 14 to 20: what actually matters when you migrate a long-lived front end

Six major versions in one go. A practical checklist for teams moving an Angular 14 application to Angular 20: toolchain, Angular Material, standalone, control flow, build system and tests.

AngularMigrationTypeScriptFront-End ArchitectureAccessibility

From 2023 to 2026 I was the architect of several Angular front ends on ZHservices, the public services platform of the Canton of Zurich. Part of that work was moving them from Angular 14 to Angular 20. This post is not about the client. It is the checklist I would hand to any team that has an Angular 14 application in production and needs to get current.

1. One major version at a time

ng update supports one major version per step. Going from 14 to 20 means six steps: 15, 16, 17, 18, 19, 20. Each step runs its own migration schematics, and they only work in order.

Do every step on its own branch, build it, run the tests, and merge it. Six small, boring upgrades are much safer than one big one.

2. Plan the toolchain first

The upgrade usually stalls on Node.js and TypeScript, not on Angular. According to the official compatibility table:

AngularNode.jsTypeScript
1414.15+ or 16.10+4.6 to 4.8
1616.14+ or 18.10+4.9.3 to 5.1
1718.13+ or 20.9+5.2 to 5.4
2020.19+, 22.12+ or 245.8 or later

Angular 19 is the last version that runs on Node 18. Check your CI agents, build images and every developer machine before you start, otherwise step 6 fails on infrastructure, not code.

3. Angular Material: the real work is in v15

If you use Angular Material, version 15 is the expensive step. The components moved to the MDC-based implementations, and the old ones were kept only as deprecated legacy variants, which were removed in version 17.

The MDC components have different DOM structure, spacing and styles. Custom CSS that targets internal Material classes breaks. Plan visual review time for every screen, not just a green build.

4. Check accessibility again after Material

On ZHservices, WCAG 2.1 certification was part of the same project. That is why I treat every Material change as an accessibility change: focus order, labels, contrast and screen reader output can shift with a new DOM. Run your automated checks and test the key flows with keyboard and screen reader after the Material step, not only at the end.

5. Standalone components and the new control flow

Two migrations change how your code looks, and both have schematics:

  • Standalone components became stable in Angular 15 and the default for new projects in Angular 17. ng generate @angular/core:standalone migrates existing modules in stages.
  • Built-in control flow (@if, @for, @switch) arrived in Angular 17. ng generate @angular/core:control-flow converts templates. In Angular 20, *ngIf, *ngFor and *ngSwitch are officially deprecated and are expected to be removed in a later major version.

You do not have to do either during the version upgrade. I recommend finishing the version jump first, then running these migrations as separate, reviewable changes.

6. Build system

Angular 17 introduced the esbuild-based application builder as the default for new projects. Existing projects can switch, and the Angular 20 update offers to move to @angular/build. Faster builds are nice, but check custom webpack configuration, environment handling and asset paths before you switch.

7. Removed APIs

Some old APIs are gone in Angular 20, among them TestBed.get() (deprecated since version 9) and the InjectFlags enum. ng update migrates most of these automatically, but search your code for anything the schematics cannot see, such as dynamic usage or shared libraries outside the workspace.

8. Tests are what make it safe

An upgrade like this is only as safe as the test suite behind it. Unit tests (for example with Jest) catch broken APIs, end-to-end tests (for example with Cypress) catch broken flows, and a CI pipeline runs both on every step. If the suite is thin, write tests for the critical flows before you start. That time pays for itself on the first major version.

Summary

  • Six steps, one per major version, each merged on its own.
  • Node and TypeScript first.
  • Angular Material 15 is the big one: budget visual and accessibility review.
  • Standalone and control flow after the upgrade, as separate changes.
  • Tests and CI decide how calm the migration is.

If your agency or software house has an Angular application stuck on an old version, I take on migrations like this fully remote. Get in touch via mazzotta.dev.

By Roberto Mazzotta · Nov 12, 2026

Have a build like this in front of you?