Evergreen IT or Evergreen ERP: what is the difference?

Evergreen IT keeps the version current: continuous small updates instead of large migrations. For Business Central in the cloud, Microsoft handles that automatically with two release waves a year, on a schedule published in advance. Anyone running BC online essentially has Evergreen IT without doing anything for it. Evergreen ERP means something else: the state of your business. The question is not whether the latest version is running, but whether the system still reflects what you do today. No update solves that. The difference matters in practice because the market calls both of them „Evergreen“: when a Business Central partner offers Evergreen, they almost always mean an upgrade service, that is, accompanying the two waves and testing extensions. That is useful operations work, but it keeps your version current, not your business.

What does evergreen IT mean?

Microsoft coined the term in 2015 for services whose components are always up to date. The idea behind it is strong and has prevailed: instead of a large, risky migration every few years, small updates arrive continuously. That lowers both risk and maintenance cost noticeably.

For Business Central this is lived practice. In the cloud Microsoft delivers two release waves a year, automatically, and publishes the schedule for them in advance. Anyone running BC SaaS today essentially has Evergreen IT without doing anything for it.

Source: Microsoft Learn: Update cycles

That is why the term is barely contested in the market: it describes a state the platform produces, not a project you have to run. Whoever debates Evergreen IT is debating operations, and with Business Central Online that is largely solved.

What has the partner market made of it?

When a Business Central partner offers "Evergreen", they almost always mean an upgrade service: they accompany the two waves, test extensions against the new version and keep you inside the support cycle. That is useful, and somebody has to do it.

But it is operations, not strategy. And it does not answer the question you actually have, namely whether your system still reflects how you work today. The upgrade service does not even ask that second question, because it lies outside its remit.

The confusion is therefore not a marketing trick but a problem of terminology. Both sides say "Evergreen" and mean different things: one the version level, the other the state of the business. Whoever does not keep those apart buys operations and believes they got strategy, and notices the difference only when a new business requirement is left sitting.

Why is the mix-up expensive?

Anyone who believes the upgrade service settles the matter stops asking. The system is current, after all. The catch: software being current and your business model being current are two entirely different things, and Microsoft only handles one of them for you.

The test is simple. Your business raises a new requirement. How long does it take until it is in the system? If the honest answer is "the quarter after next", you have an up-to-date system that reflects your business of yesterday.

That is not a contradiction, it is the normal case. And it is not down to Business Central. It is down to the fact that every adjustment eats time and budget as long as the data foundation does not hold and nobody is named who is allowed to decide. Your response time to a new requirement is therefore not a technical figure but a mirror of your data quality and your decision paths.

Why do the two belong together?

This is explicitly not an argument against Evergreen IT. The automatic version level is good, and without it the rest would be harder, because you would then have to handle migration projects on top. It is simply not the goal but the precondition.

Only together do the two make a solid picture: the platform holds the version level, you hold the state of your business. The second is work on the data foundation, the processes and the decision paths, and that work is not delegated to a release calendar. In practice that means: the upgrade service stays sensible and gets commissioned, but it is not confused with the question of whether your system still reflects your business. Both need an owner, and in practice those are rarely the same people.

What makes an Evergreen ERP and the four characteristics by which you recognise one is set out in What is an Evergreen ERP.