Guide · 7 min read · updated 2026-10-07

Sophos UTM (SG series) end of life: what it means and how to migrate to XGS

If you still run a Sophos SG appliance or a UTM 9 virtual machine, the clock has stopped. Sophos ended UTM on 30 June 2026, no licence extensions are being processed, and no support of any kind continues past 31 December 2026. Here is what that means in practice and how we move customers across.

The dates

  • 30 June 2026: Sophos UTM end of life. UTM SKUs deactivated; no new terms or extensions.
  • 1 July – 31 December 2026: customers with a licence running past 30 June still receive support, but only until 31 December 2026 regardless of licence end date.
  • After 31 December 2026: no support, no security updates. When a UTM licence expires its protection features stop.

The XG series hardware (the generation between SG and XGS) reached end of life on 31 March 2025, so a migration should land on current XGS hardware or Sophos Firewall as a virtual machine.

Why not just leave it running?

A UTM 9 box will keep routing after 31 December. It will also stop receiving IPS patterns, antivirus updates and firmware fixes, which on an internet-facing device is the definition of an unmanaged risk. Cyber-insurers and auditors treat end-of-life perimeter devices as a finding. The sensible move is to migrate while Sophos support still exists to help with the odd problem.

What the migration involves

  1. Size the replacement. Most SG 1xx/2xx desktops map to an XGS 108–138; SG 3xx/4xx to an XGS 2100–3300. Our sizing tool and the sizing guide cover this.
  2. Export and translate the configuration. Sophos Firewall OS is a different operating system from UTM 9; there is no one-click upgrade. Objects, rules, NAT, VPN peers, web and application policies and user authentication are rebuilt, mostly by script, then reviewed by hand.
  3. Parallel run. The XGS is built and tested alongside the UTM, VPN peers are pre-shared, and users are told about the cutover window.
  4. Cutover. Typically after hours: swap the WAN and LAN cables, bring up the VPNs, test, and keep the UTM on the shelf for a week.
  5. Hand over. Documentation, Sophos Central registration, and an optional managed-firewall service so it stays current.

A desktop-class migration is usually one working day of engineering plus the cutover evening; a rack-mount with many VPN peers and policies is two to three days.

What it costs

Three parts: the XGS appliance, an Xstream or Standard Protection subscription, and our installation and migration labour, all quoted in rand on one page. Sophos has run migration promotions through its distributors (appliance discounts and bonus licence months); we apply whatever promotion is current at quote time. The migration page maps SG models to their XGS replacements.

Virtual UTM?

Sophos Firewall runs as a virtual machine on VMware, Hyper-V, KVM and Citrix, and in Azure and AWS. The migration steps are the same; the base licence for a virtual firewall is a paid, termed item rather than perpetual, which we include in the quote.

Questions people ask

Can my UTM licence be transferred to the XGS?

No. UTM and Sophos Firewall licences are different products. The XGS comes with a perpetual base licence and you buy a new protection subscription; Sophos's migration promotions have historically softened this.

Will my RED devices and access points still work?

Current SD-RED models and Sophos APX/AP6 access points are managed by Sophos Firewall. Older RED 10/15 and legacy AP models are not; we check your inventory in the survey.

How much notice do users need?

The cutover itself is 30–60 minutes of disruption if the parallel build is done properly. Remote-access VPN users need the new connection profile, which we distribute beforehand.

Plan my UTM migration