We are a NetSuite partner, so take the recommendation at the end with that in mind. What follows is mostly not our opinion. It is what Sage publishes about Sage 200 in its own lifecycle policy, its own knowledgebase and its own results, because on this question Sage's documentation is more useful than anybody's sales page, ours included.
Sage 200 is an active product on a twice-yearly release cycle. Sage 200 Professional 2025 R2 shipped on 28 November 2025 and is supported until November 2028. On-premise deployment is still listed as a supported option in Sage's own lifecycle policy dated August 2026. A 2026 R1 release has been announced.
What has changed is narrower and easier to miss. Sage has taken two significant pieces out of the product, and it now points its growing customers somewhere else.
Manufacturing is gone. Sage's lifecycle policy is blunt about it. The module was "withdrawn from sale effective 01 November 2020", technical support "will cease effective 31 December 2025, regardless of the version in use", and then this: "Sage 200 Manufacturing functionality was removed from the product in the 2025 R2 release." For anyone upgrading, "the data, in tables, will remain but is not accessible in the product anymore." Sage names the replacements itself, and they are both third party: Cim200 Manufacturing and Sicon Manufacturing.
Bill of materials survives, and for simple assembly it is fine. Material requirements planning, shop-floor scheduling and anything a factory would recognise as manufacturing now comes from an independent software vendor on its own contract and its own release cycle.
CRM went the same way, earlier. Sage 200 CRM was "withdrawn from new sale as of 01 April 2021", all its installation components were removed in the 2022 R1 release, and Sage states plainly that "no further versions of Sage 200 CRM will be provided." The current product page offers Sage CRM as an integration, which is a different thing from having it in the box.
Neither of these makes Sage 200 a bad system. They do change what it is. A Sage 200 estate running manufacturing and CRM in 2026 is a Sage core with two third-party products bolted to it, each of which has to be upgraded separately and kept compatible.
This is a clock on your version rather than on the product. On 2025 R2 you have until November 2028 before end of support, so most of this section will not apply to you yet.
Sage supports "the latest major release minus 2 major versions". Sage 200 Standard is exempt because it updates itself. Everyone on Professional is on a rolling clock of roughly three years.
The part that catches people out is not the end-of-support date. It is what happens well before it. Sage's own lifecycle stage table shows that legislative updates and defect resolution stop the moment a version leaves Current status, which is when Extended Support begins, not when support ends.
Sage 200 Professional 2023 R1 and 2023 R2 entered Extended Support on 1 February 2025. So a business running Sage 200 Professional 2023 today has had no legislative updates and no bug fixes for over eighteen months. For a finance team, legislative updates are the tax and compliance changes the software exists to keep up with. Sage's own guidance is to "upgrade to a version that contains the changes."
Sage's own document is not consistent about 2024, and you should know that before acting on any of this. Page 9 of the lifecycle policy lists 2024 R1 and 2024 R2 under "Currently Supported Versions". The matrix on page 10 gives both an Extended Support start of 01/02/2026. Those two statements cannot both be right, and which one holds decides whether a 2024 customer is still receiving legislative updates today. If you are on 2024, that is a question to put to your Sage partner in writing rather than an assumption to make either way.
Two further dates worth knowing. 2023 R1 reached end of support in February 2026. 2023 R2 reaches it in October 2026. And once a version has been out of support for two years, Sage removes the ability to buy additional users at all: "Should there be a need to buy a module or user, a customer should be upgraded to the latest version." For a growing business, that is usually the constraint that bites first, and it has nothing to do with capacity.
You are past about fifty concurrent users. Sage publishes no user cap. What it does publish, in answer to a direct question about limits, is this: "No, however we have only performed concurrent testing up to 50 users." Its largest standard virtual machine is sized for six to fifty users, and its own site-survey process escalates sites "above, for example, 50 users". Past that point you are outside what the vendor has tested, which is a different thing from being over a limit, and a harder thing to get support for.
Your consolidation happens in a spreadsheet. Sage 200 can consolidate. What it does is post a journal: subsidiary balances are "posted to the parent company as an imported journal". The chart of accounts in the parent has to match the subsidiary. Prior-year journals "will distort current year values". Nothing in the Sage 200 help covers intercompany eliminations or minority interests. That is not proof they are absent, but if you need them, ask your partner to show you rather than assume. If your group needs eliminations and a same-week consolidated close, this is the wall.
Your reporting is a nightly snapshot that breaks across companies. Sage 200 Business Intelligence runs on a scheduled data extract rather than on live data, and partners typically schedule it overnight, so the numbers you open in the morning are yesterday's. Two documented limits matter more than that. Asked whether the same report can be run in different companies, Sage answers: "You cannot do this if the companies have a different nominal ledger structure or different sales analysis codes." That is exactly the position of any group that has grown by acquisition. And "there is no guarantee that any customised reports will work with future versions of the software." Business Intelligence is also absent from Sage 200 Standard entirely.
Your upgrade is a negotiation with several vendors. Sage's lifecycle policy is explicit that "any additions/customisations are the responsibility of your business partner and/or the addition provider", and add-ons upgrade as a separate operation from Sage 200 itself. With manufacturing on Cim200 or Sicon, CIS on Sicon, and whatever else you have added over the years, each on its own release cycle, a Sage 200 upgrade stops being one project. Any one of those vendors can hold the whole estate on an old version, and an old version is one that has stopped receiving legislative updates.
Sage runs a page on its own UK site titled "Switch from Sage 200". It presents a ladder: Sage 200, then Sage Intacct Essentials, then Sage Intacct. Sage 200's entry on it reads "Ideal for businesses that want a cloud connected solution", against Intacct Essentials as "Cost-effective, AI-powered cloud financials for growing SMBs". Read on 6 September 2026; Sage has rewritten this page at least once in 2026, so check it yourself rather than take our word for it.
Sage published an article on multi-entity consolidation on 20 April 2026 that sets out four common challenges and their effect on finance teams, in its own words: "Exchange rate fluctuations distort comparisons; manual conversions introduce errors", "Duplicate revenue or expenses inflate group totals; reconciliation takes hours", mismatched charts of accounts where "finance teams may end up spending hours manually mapping accounts or exporting data into spreadsheets", and manual entry in Excel where "overwriting a cell, referencing an outdated exchange rate, or forgetting to update one subsidiary's file can cause errors that cascade through the whole workbook." Those are the symptoms described above. Sage's answer, in full: "Sage ERP solutions, including Sage Intacct and Sage X3, offer consolidation capabilities that integrate with Sage Accounting." Sage 200 does not appear in the body of that article at all.
Sage's own results say it a third way. In its 2025 full-year figures Sage 200's contribution is credited to "a strong renewal rate and higher pricing", and in the first half of 2026 it drops out of the UK and Ireland commentary altogether. Sage Intacct grew 26 per cent to £267m over the same period, though that figure is US revenue rather than UK, and Sage does credit Sage 200 in its North America commentary.
None of that means Sage 200 is being wound down. It means the growth is being steered elsewhere, and Sage is telling you where. For a lot of businesses, following that steer is the right answer. If your problem is finance-shaped, multi-entity consolidation, dimensional reporting, a faster close, and you do not carry stock or make anything, Sage Intacct is a sensible destination and staying inside the Sage family removes a whole category of migration risk. We have written a full comparison of NetSuite against Sage Intacct, which is a different product from Sage 200 with a different upgrade path, and it is the better read if that is the decision in front of you.
NetSuite is not the answer to a Sage 200 problem that is only about finance. Sage Intacct is a serious product and on a finance-only comparison it often wins.
NetSuite earns its place when the thing you have outgrown is not the ledger but the shape of the business around it. One data model covering inventory, manufacturing, warehouse, order management, CRM and financials, rather than a finance system with operations attached to it by integration. If your Sage 200 estate is a core plus Cim200 for manufacturing plus Sage CRM plus the integrations between them, the honest comparison is one system against several products, each on its own release cycle.
It is the wrong answer if you run a single entity, in one currency, with no stock, and your only complaint is that reporting is slow. That is a reporting problem with a much cheaper fix, and the last section covers it.
Sage does not publish a Sage 200 price. UK Sage partners publish indicative figures and the two below are about 21 and 22 per cent apart, so treat any single number carefully. Eventura lists Sage 200 Professional from £309 a month with one desktop user and £51 for each additional desktop user; CPiO lists the same product from £374 plus VAT and £62.50 plus VAT per additional user. Neither is a Sage list price. Modules and third-party add-ons sit on top, and on a group manufacturing site the add-ons can cost as much as the Sage licences do.
Two things about cost comparisons, both of which cut against us. The first is that you should not move to save money on licences. Microsoft publishes Dynamics 365 Business Central at £61.50 per user per month, against the £51 to £62.50 UK partners quote for a Sage 200 Professional desktop user. On published list prices there is no licence saving worth crossing the road for, in either direction.
The second is that Oracle publishes no UK price list for NetSuite. Every NetSuite figure you will find, including from partners like us, is an estimate rather than a list price. That means a NetSuite versus Sage 200 cost comparison is not comparing like with like: one side publishes and the other does not. Our NetSuite pricing guide sets out what we see in real UK projects, and it is still an estimate.
Most businesses running it, on the evidence above. Four cases in particular.
Which version are you on, and when did it leave Current status? If you are on 2023, you stopped receiving legislative updates in February 2025 and that is the thing to fix first, whatever you decide about platforms. It may just mean an upgrade.
Is your problem the ledger, or the business around it? If it is the ledger, consolidation, close speed, dimensional reporting, look at Sage Intacct first and read our comparison of it. If it is stock, production, orders and fulfilment as well as the ledger, that is the case for a single system and where NetSuite belongs in the conversation.
Is something broken, or is one thing annoying? One frustration usually has a fix that costs a few hundred pounds a month. Several of the four signals above, together, is a different conversation.
If you are working through that now, our NetSuite implementation team can scope what a like-for-like comparison looks like for your business, including telling you when the answer is to stay put or to go to Intacct. Our ERP data migration guide covers the extract and mapping work that is the most underestimated part of any move, and our round-up of NetSuite competitors and alternatives covers the wider field.