Sage is committed to keeping our customers secure and making sure we reduce threats and take advantage of the latest technology, meaning from time to time we need to upgrade the underlying components of our products.

Technology is always changing, including how Sage software works alongside associated software including Operating Systems & Browsers. Sage 200 and Sage CRM will be impacted by industry changes to the TLS protocol currently being made to browsers and operating systems.

What is TLS?

TLS is a security protocol required for services such as Sage ID and the Sage License Service. TLS (Transport Layer Security) is a widely adopted security protocol designed to facilitate privacy and data security for communications over the Internet.

What are the upcoming changes?

The Internet Engineering Task Force (IETF) no longer recommends the use of older TLS versions. Operating system changes to prevent the use of TLS 1.0 / 1.1 can be expected but may impact businesses earlier if the business IT policy removes the use of this protocol ahead of software vendors.

What does this mean for my Sage Software?

TLS is required for services such as the Sage Licensing Service, which enables products to communicate securely. The current versions of TLS 1.0/1.1, are due to be deprecated from the Sage product range and will be upgraded to TLS 1.2, providing greater security and simpler maintenance.

1) Sage 200 Professional:

  • Customers on Sage 200 2013 up to, and including, Spring 2019 will be impacted and must be upgraded to a TLS 1.2 compliant version of Sage 200 prior to the End of Life date detailed by Sage in the Sage 200 Software Lifecycle Policy.
  • Please note: in line with a variety of technology changes, versions where an End of Life date is specified can no longer be licensed after the date indicated and will cease to operate. Not all versions are impacted and those without a date will continue to function. These dates could change at any time, so please check regularly. We encourage upgrades to the latest version to ensure you get the most value from your subscription.
  • Customers may be required to upgrade earlier than the specified date if the business IT policy adopts TLS 1.2 and removes the use of TLS 1.0/1.1, or if Sage 200 API or Sage 200 CRM are in use.

2) Sage 200 CRM and Sage CRM Standalone:

  • Sage CRM Standalone – Sage have released software patches for all supported versions of Sage CRM from 2018 R1 onwards, to ensure TLS 1.2 compatibility. Customers running versions prior to this will need to upgrade in order to be TLS 1.2 compatible.
  • Sage 200 CRM – Sage have released software patches for Sage 200 CRM (Classic Integration) from Sage 200 Summer 2017 RM with Sage CRM 2018 R3 onwards, to ensure TLS 1.2 compatibility. Customers running earlier versions of Sage 200 CRM will need to upgrade in order to be TLS 1.2 compatible.

Next Steps?

If you’re on a version of Sage 200 older than Spring 2019 then the upcoming TLS changes will impact your software. We advise you to get in touch with your account manager to discuss upgrade options and how to get the most out of your system.

You can request a callback and we’ll be in touch or email for more information.

sage 200 version support

Request a call-back if you want to discuss your current Sage system and technical requirements: