Sage 50 SData support has ended: your routes today, and a nightly export in testing

Sage stopped maintaining SData, the interface some Sage 50 Accounts reports and dashboards used to read data. If an Excel or Power BI report that once worked has stopped, this page sets out what Sage said, the routes that exist today, and one self-install nightly export we are testing that does not exist yet.

Covers: when Sage support for SData ended, in Sage's own words, the routes to your Sage 50 data that exist today, and an interest test for a proposed self-install nightly export. Doesn't cover: whether ODBC or a connector suits your own reports, the prices or terms of any third-party connector, or any promise that a particular tool will work with your data. Guidance only, not a recommendation of any product. Independent page. Not affiliated with or endorsed by Sage. Sage 50 is a trademark of The Sage Group plc. Read Sage's community page (2 November 2026) and check it yourself.

What changed, and when

SData was an interface that let other programs read data from Sage 50 Accounts: in-house dashboards, Excel and Power BI reports, and integrations. Sage's community hub carries a reply from Sage staff, marked Solved and posted over a year ago, on when support ended.

Source: SData discontinued - what Sage 50 release will no longer connect, Sage Community Hub. Read 2 November 2026.

The same Sage community page, on when support ended:

Support for Sdata is no longer being maintained as of September 30th 2025

no longer supported as of the v33 release of Sage 50 due out later this year

The same reply says there is no testing, security fixes or enhancements for SData, that older versions may keep working, and that Sage does not recommend continued use. The page names no replacement and no workaround.

Your routes today

Sage's own ODBC driver

Sage's own ODBC driver is one route. Our reading on 2 November 2026 records it as giving read access, and as commonly 32-bit, which matters if the Excel or Power BI you use is 64-bit. We have not established its price or its terms for third-party tools. Whether it is enough depends on what your reports need, and this page does not take a view.

Third-party connectors

Third-party connectors exist. CData's Sage 50 UK Power BI connector is built on an ODBC driver, and our reading records that it needs the SData adapter for version 28 and later. We have not checked any connector's price or terms, and this page states none.

What this page has not established

Not established for this page: how many firms used SData, whether any firm has paid for a fix, current prices for any connector, Sage's terms for using its ODBC driver with third-party tools, and whether ODBC is retained in version 33.

A self-install nightly export we are testing

The idea is a self-install Windows tool that copies your Sage 50 data into SQL Server or CSV every night, for Excel and Power BI. The price, if it is built, would be GBP 149 once.

This page is a test of interest, not a shop. There is no payment form and no email field anywhere on it. Pressing the button records one anonymous count for the day, and a short tag if the link you followed carried one.

How this page is checked

Every quoted line above is a line of the page's one data file, and a test fails the build if a served quote is not a line of that file. A second test fails the build if a banned word appears. If a source changes or we find an error, we correct this page and record it here. Read 2 November 2026.

No corrections yet (Sage's community page read 2 November 2026).