This communication was sent 22 December 2022.

Notice 22-HE | 22 December 2022

Sage 200

Dear Partner,

In May 2021 the Sage 200 lifecycle was changed to support our evolving strategy, the release of Sage Partner Cloud, as well reflecting the pace at which technology is changing.

Based on feedback from partners, we’ve undertaken a review of the previous and current policy while considering the feedback. We wanted to share our findings with you as well as remind partners of the key points of the policy and language.

Findings & Next Steps

As part of transitioning from our old lifecycle policy, to the new one there is inevitably a period of cross over and change.

Having reviewed the old and new policy, 3 of the versions that will be retired from support when 2023 R1 is released have an extension to their support dates: Versions Summer 2018, Winter 2018 and Spring 2019 which were advertised to end support as of 30 September 2022 meaning almost 5 months of additional support.

We firmly believe that our policy of supporting the current release, and the 2 prior is the right way to move forward, however, we also believe there may be some small improvements we can make to support partners and customers. We’d like a wider view from all partners via our survey. We’d ask for your response to this no later than 16th January 2023, after which we’ll send a further update.

Retirement Dates

We no longer retire versions in the autumn, the R1 product release each calendar year currently determines the date that prior versions no longer receive support. While the policy document currently states January it will change depending on this release date, for example 2023 R1 is scheduled for a February 2023 release date, so all versions indicated will be supported up until its release.

Use of Language

When we stop supporting a version – this is called a version retirement or end of support, please do not refer to it as end of life. Unless we notify you otherwise, the version will continue to work beyond its version retirement date. It is your choice as a partner to determine if you have the knowledge and capability to support this without Sage’s assistance. Equally we want customers to get the most from their software, so we ask that as part of ongoing customer conversations you:

• Ensure customers are aware of the product lifecycle and retirement dates.
• Ensure customers are aware of new features that have been released since their current version and validated against current business needs.
• Check any associated end of support notifications for connected software e.g. Microsoft SQL, Microsoft Windows and work with their IT contacts to ensure that all factors are considered.

Separately, where a variant of a product or a product will cease in its entirety this is called a Product Retirement. Examples of this would be Sage 200 Extra Online, and Sage Line 100. In these cases, separate communications will be created to support partners & customers.

It’s essential that the terminology used is correct.

Questions

If you have any questions of a technical nature, you can contact our support team. For anything else please speak to your account manager.