Contact us
Nakisa End of Support: Keep Your Legacy Nakisa OrgChart Running on Modern Windows | Cloudhouse
SAP Org Visualization by Nakisa · Legacy Windows · End of Support

Keep your legacy Nakisa running. No rewrite. No forced re‑implementation.

Older on-premise Nakisa, OrgChart, OrgModeler and OrgAudit, was built on Java and a Flash-era web layer, and it sits on a Windows Server that is now out of support. At the same time, the SAP HCM core it reads from is being pushed toward S/4HANA and SuccessFactors. That leaves HR and IT with a heavy option: rip out the current system and re-implement on new cloud tooling. Cloudhouse™ offers a third way. We package Nakisa and its legacy dependencies so it runs on modern Windows Server, keeping your org charts and org management live, with no code changes and results guaranteed.

Talk to our team See what we have delivered
Dec 2020
When Adobe Flash reached end of life and was blocked from running, the technology the Flex interface in older Nakisa versions was built on
Dec 2027
When SAP Business Suite 7 mainstream maintenance ends, changing the SAP HCM core that Nakisa reads from
0
Lines of Nakisa application code changed to keep the system running on a supported platform
The legacy Nakisa problem

An HR-critical org system, running on a web stack that has aged out.

Nakisa still draws the org charts, models the reorganisations and reports on the workforce for a large number of enterprises, most of them SAP houses. For HR it works, and they would rather leave it alone. The difficulty sits underneath it. The application, the web components it was built on and the Windows Server it depends on have all fallen out of support, and the SAP system it reads from is on the move. That creates three separate pressures.

Platform

Built on a web stack that has aged out

Older on-premise Nakisa runs on a Java application server, with the org charts served through a Flex, Flash-based interface. Adobe blocked Flash at the start of 2021, and the Windows Server and database versions Nakisa was certified against have since reached end of support. The application still runs, but the ground underneath it has moved.

Change

SAP HCM is moving, and Nakisa reads from it

Nakisa connects to SAP HCM through an ABAP add-on. With SAP Business Suite 7 mainstream maintenance ending in December 2027, and HR shifting toward SuccessFactors, the source system is changing underneath the tool. The vendor answer is to re-implement on new cloud tooling, a full project on a timeline set for you.

Risk

Unsupported, and fewer people who know it

An unpatched Windows Server carrying an HR and org system is one of the first things an auditor flags. The consultants who first configured these deployments have long moved on, and internal knowledge thins every year, so each SAP change upstream carries more risk than the last.

How Cloudhouse solves it

Package Nakisa. Modernise the OS. Keep the org charts running.

Cloudhouse containerises the application at the application level. Nakisa, its Java runtime and its legacy web components are sealed inside a self-contained runtime and are never installed or registered on the host operating system. Nakisa runs exactly as your HR team knows it, the SAP HCM connection stays intact, and the unsupported parts are lifted off the estate.

01 / PACKAGE

Contain Nakisa and its dependencies

  • Nakisa, its Java runtime and its legacy web components packaged together
  • Old Windows libraries, the application server and Flash-era parts encapsulated, not installed on the host
  • The SAP HCM integration preserved inside the package
02 / MODERNISE

Run it on current Windows Server

  • The package runs on Windows Server 2022 or 2025
  • The unsupported operating system leaves your estate
  • The host stays patched, supportable and audit-ready
03 / CONTINUE

Business as usual for HR

  • No rewrite and no application code changes
  • Org charts, modelling and reporting run as before, no retraining
  • You choose when, or whether, to re-platform
The Cloudhouse approach

A proven, repeatable pattern, not a one-off fix.

Alchemy runs legacy Windows applications on any modern platform with no rewrites. Cloudhouse has been keeping business-critical applications running safely since 2010, and legacy SAP org visualisation tools such as Nakisa are exactly the kind of application we contain. We have delivered the same packaging approach across regulated industries, each one keeping the org system live and the operating system supported.

Results guaranteed, or your money back
No source code changes, no vendor lock-in
Keeps the SAP HCM integration intact
Governed delivery across testing and go-live
Runs on current Windows Server 2022 or 2025
UK-based engineering and support
Book a 20-minute conversation See case studies
Your options

Re-implement, risk it, or package it.

Every team facing a legacy Nakisa deployment is choosing between the same paths. Set side by side, the trade-offs are clear.

Re-implement on cloud tooling Carry on as-is Cloudhouse
Cost and effort Multi-month re-implementation and re-integration with SAP Low now, higher later A fraction of a re-implementation, delivered in weeks
Disruption to HR New interface, data migration and retraining None until something breaks None, the interface is unchanged
Support and security posture Resolved, eventually Unsupported OS and web stack, at risk now Supported OS, legacy risk contained
Who sets the timeline The vendor roadmap The next incident You do
Proof across sectors

One of the UK's largest legacy Nakisa environments, kept running.

Cloudhouse is packaging a major legacy Nakisa deployment today, and applies the same approach to the legacy Windows and SAP-adjacent applications that surround it. The names are withheld, the pattern is the same: keep the org system running, take the unsupported platform off the estate, and avoid a forced re-implementation.

Postal & logistics · National operator

An org platform left unsupported since 2016, still in daily use

A Nakisa environment running org and reporting processes across a large operational workforce, unsupported for years and sitting on an ageing SAP HCM core. Being packaged with Alchemy and moved onto a supported platform without a rewrite, while the wider SAP roadmap is worked through.

Track record · Since 2010

Fifteen years of legacy Windows applications

Cloudhouse has kept business-critical Windows applications running on modern platforms across finance, utilities, manufacturing and the public sector, including legacy SAP-adjacent and enterprise reporting systems.

Technology · The class we contain

Java, IIS and Flash-era web applications

The web stack under older Nakisa, a Java application server, old IIS components and a Flex, Flash-based front end, is exactly the kind of estate Alchemy packages and runs on a supported, patched host.

Regulated sectors · Where it bites hardest

Finance, utilities and the public sector

In audited environments, an unsupported operating system under an HR or org system is a finding waiting to happen. Packaging contains that risk without touching the application HR relies on.

The recurring pattern · M&A and restructuring

Org tooling that never caught up with the business

Deploy once, grow the business around it through mergers and reorganisations, and a few years later the org tool is quietly out of support while still running critical processes. The same fix applies wherever this pattern shows up.

One supplier · Any legacy Windows app

Beyond Nakisa

The same approach handles the rest of the legacy Windows estate around Nakisa, from classic ASP and IIS workloads to other end-of-life line-of-business applications.

Engagements are anonymised. Cloudhouse can arrange a reference conversation with a comparable customer under NDA on request.

Frequently asked questions

Legacy Nakisa end of support, answered.

Is Nakisa still supported?
Nakisa remains an active vendor with a current cloud product. The risk sits with older on-premise deployments, the SAP solution-extension editions such as SAP Org Visualization by Nakisa, and the Windows Server, Java runtime and Flash-era web components they run on, which have reached end of support. The application keeps working, but the platform underneath it no longer does.
Can I keep running my legacy Nakisa deployment safely?
Yes. Cloudhouse packages Nakisa and its legacy dependencies into an isolated Alchemy container and runs it on a supported operating system. The unsupported Windows layer leaves your estate, the endpoint stays patched, and Nakisa runs exactly as your HR team knows it.
Do I have to re-implement on cloud Nakisa or SuccessFactors?
Not on someone else's timeline. Moving to a cloud org tool is a full re-implementation and re-integration on a new interface. Packaging your current Nakisa with Cloudhouse lets you keep the existing system running and decide when, or whether, to re-platform on your own terms.
Can Nakisa run on Windows Server 2022 or 2025?
Yes. Once packaged with Alchemy, a Nakisa environment built for an older Windows Server runs on Windows Server 2022 or 2025 without changing the application. The legacy components are encapsulated inside the container rather than installed on the host.
Does this change the application or require retraining?
No. There is no source code change and no new interface, so org charts, modelling and reporting run as before and users need no retraining. Delivery is governed through testing and go-live, and results are guaranteed.
Does this keep the SAP HCM integration working, and what about the old Flash interface?
Yes. The SAP HCM connection is preserved inside the package, and the legacy web components, including any Flash-era parts, are contained so they run on a supported, patched host. The same approach covers the wider legacy Windows estate around Nakisa, handled by one supplier.
Get in touch

Nakisa won't get younger. Let's talk before your next audit or SAP milestone.

Tell us where the pressure is, an old on-premise Nakisa version, an unsupported Windows Server underneath it, or an SAP HCM move that puts your org tooling in scope. We will show you the approach on your own environment, not a generic demo.

  • On an older on-premise Nakisa build? We will show how to keep it running on supported Windows.
  • Facing a forced re-implementation? We will map a way to defer or avoid it on your terms.
  • Other legacy Windows apps in the estate? We handle them the same way, one supplier.
  • Results guaranteed, so you can commit with confidence.
    • Our offices
    Venture X · White City, London
    Response within one working day

Book a conversation

20 minutes. We listen first. No slide deck unless you ask.
Request a conversation →