Keep your legacy ERP
without rewriting it.
The ERP client that runs the business is usually the last thing anyone wants to touch. A rewrite takes years and can lose behaviour nobody wrote down. There is a middle path: leave the application alone, and modernize how people reach and use it.
Step 1: stop installing it
Run the client on a Windows host and open it from a link. New hires, contractors and remote staff can use it the same day, and there is no per-laptop setup to maintain.
Step 2: put controls around it
Once the app is reached through one front door, add what it never had: SSO, roles, clipboard and file-transfer policy, a watermark and session recording. You get the benefits of modern access without touching the old software.
Step 3: automate the repetitive parts
Re-keying data between systems is where a lot of ERP time goes. Workflows can click, type, wait and extract text against the app's live UI tree, and run on a schedule or from a webhook, with a run history for every execution.
Step 4: decide about the rewrite on better terms
With access sorted and the busiest processes automated, the pressure to rewrite drops. If you do rewrite, you will know more about how the application is really used, and recordings can show it.
What to check before you start
Confirm the application runs well on a Windows host, and where that host sits relative to your database and internal systems. Check licensing for the app and for Windows. A short trial on your own application answers most of this.
Why rewrites stall
Old ERP clients carry years of rules that live nowhere but in the code and in people's heads. A rewrite has to rediscover all of it, while the business keeps running on the old system. That is why so many stall, or ship something that is missing behaviour people relied on.
What changes for people
For users, the application looks the same, because it is the same. What changes is how they reach it: a link instead of an installer. For IT, the change is bigger: one place to run it, one place to secure it, and a clear record of who uses it.
Placing the host
ERP clients usually talk to a database or a server. Put the Windows host where that connection is fast and allowed, such as inside your network or alongside the database. Users reach the host through the stream, so they do not need that network access themselves.
Using recordings to plan the future
If you do eventually replace the application, recordings of real sessions are a record of how it is actually used, which screens matter and which are never opened. That is far better input for a replacement than a requirements document written from memory.
Illustration
A worked example
Imagine a distributor on a twenty-year-old ERP client. Remote staff cannot use it without a VPN and a long setup, and the finance team re-keys invoices into it by hand every day.
They stream the client from a host next to the database, so remote staff open it from a link. Then a workflow takes over the invoice entry, with a person checking the results. The rewrite is still on the roadmap, but it is no longer urgent, and it will be informed by the recordings.
Getting started with a legacy ERP
- Confirm the client runs well on a Windows host.
- Place the host so it can reach the database and any licence server.
- Check Windows and application licensing for hosted use.
- Decide who gets access first, and pilot with a small group.
- Turn on the controls you need: SSO, clipboard policy, watermark, recording.
- List the repetitive tasks that are worth automating.
Related features
Questions.
The app is streamed as it is, with no modification. Your own licence terms still apply, so check them.