Sage Product Lifecycle

Release dates, version history and support and end-of-life dates as published by Sage. Dates within the next 12 months are highlighted; past dates are dimmed. Retrieved 2026-10-14.

• Sage 200 Lifecycle Policy. Each Sage 200 Professional version passes through Current, Extended Support, End of Support and Retirement; Sage 200 Standard is always on the latest version. [1][2]
• Sage 300 support policy. Sage supports the current Sage 300 version and two prior versions, with major releases annually. [3]
• Sage 100 supported versions. Sage supports the current Sage 100 version and two previous versions, and the oldest retires with each new release. [5]
• Sage 50 Accounting obsolescence policy. Sage 50 Accounting (US) supports only the current version, and program, tax and connected-service updates stop for older versions. [4]
• Sage 50 UK software lifecycle policy. Sage withdraws support, updates and upgrades for Sage 50 Accounts and Payroll versions behind the latest releases in a phased approach. [6]
• Sage X3 Lifecycle Policy. Sets how long maintenance support is available for each Sage X3 release, from availability for purchase to the end of maintenance date. [7]

Continuously updated 3

Sage 200 Standard (Runs on Sage's Azure subscription and is always on the latest version; the release lifecycle dates do not apply.)[1], Sage Intacct (Updates are released each quarter automatically to all subscribers.)[8], Sage Intacct Construction (Delivered on the Sage Intacct service, which receives automatic quarterly updates.)[8]

No published lifecycle 9

Sage 50 (Sage 50 Accounts (UK) and Sage 50 Accounting (US) have separate policies; see those entries.), Sage 50 Accounts (Support offered for v26.3 and above with an active subscription and Sage Cover; no end dates published.), Sage 50 Payroll (Versions below v25 have completed their lifecycle; no dates published.), Sage Accounting, Sage HR, Sage Payroll, Sage People, Sage Sole Trader, Sage X3 (Governed by the Sage X3 Lifecycle Policy (maintenance stages by version); the per-version dates are not on the public page.)