Every year in Autumn, an older version of Sage 200 moves into 'end of support' status and another version enters a status of 'extended support'. This is detailed in our support policy and is standard industry practice for technology companies. We believe that using the latest software is the best way for us to help our customers to run their business effectively and by concentrating our resources on looking forward, we can help businesses move forward too. As a member of our partner channel, it’s essential that you undertake value added conversations with customers using older versions of Sage 200. Through these interactions, you can help them to understand the benefits that upgrading can deliver for their business. For most customers, the new version of the software is included in their annual Services fee (excluding customers who have signed up to perpetual agreement). To support you with your conversations, you can use our essential guide to see the benefits and features that customers will gain from their upgrade. Please remember that following the introduction of the Sage 200 release in August 2017, its easier for customers to adopt the latest version using ClickOnce deployment and where possible, reduces the dependency on implementing additional files for bespoke customisations.
Sage 200 2013 (both 2013 R1 and 2013 R2) entered extended support on 01 November 2017. These versions will no longer be supported from 01 November 2018.
Sage 200 2015 enters extended support on 01 November 2018, with all support for this version ending on 30 September 2019. Full details of the change of service is outlined within our Resource Centre. All developer support for this version will end when extended support begins. End of support dates realignment With immediate effect, our end of support dates for Sage 200 products have been changed to realign with other Sage software products, such as Sage CRM.
End of support dates now fall at the end of September each year, starting with Sage 200 2015 as detailed above. We have also updated our documentation to reflect this. |