Széchenyi Plan Plus – Government of Hungary – Co-funded by the European Union
Go to the top of the page

ReFactor by UDEMX

Your legacy system still works today. Tomorrow it is a risk. ReFactor: we rewrite it — without downtime.

We understand your business on-site, accelerate delivery with AI, and part of our fee is due only when the agreed outcome is delivered.

The problem mid-size companies already feel

An 8–20 year business-critical system still runs — orders, warehouse, manufacturing, CRM — but it is becoming a growing burden.

Knowledge sits with 1–2 people

Fewer and fewer people understand the system. If they leave or retire, day-to-day operations are at risk.

Slow and not scalable

Hard to integrate with webshops, BI, AI or partner APIs. Every change is risky and takes too long.

Security and compliance risk

Outdated frameworks, missing patches, no audit trail. This is a business issue, not only an IT one.

A previous rewrite burned the company

Big-bang programmes make leaders afraid of another risky cutover — while the current system gets more expensive every day.

The three pillars of ReFactor

On-site domain understanding

We do not migrate code blindly. We start with on-site interviews to understand the business — that is the foundation of quality.

AI-accelerated, gradual rewrite

With the Strangler Fig pattern we replace modules one by one, without downtime. AI accelerates; our engineers validate.

Partially success-based pricing

In the main delivery phase part of the fee is tied to a jointly defined outcome. We carry a share of the risk.

How it works

Four sequential phases — you can stop after any of them.

  1. 0 — Domain Discovery

    1–3 days of on-site interviews, process and system mapping, AI-assisted code survey. Output: architecture map, risks, roadmap and estimated ROI.

  2. 1 — Pilot / first module

    Replace the most valuable or riskiest module. You get a live first module, a proven method and a precise quote for the rest.

  3. 2 — Gradual modernization

    Rewrite and go-live module by module, with parallel operations and CI/CD — until the whole system is cloud native.

  4. 3 — Operations

    Optional DevOps/SecOps operations, support and continuous improvement under an SLA.

Why the risk stays low

The old system keeps running

We never replace everything at once. Through a gateway we switch one business capability at a time; the rest stays on the legacy system. No overnight big-bang cutover.

A written success metric

At the end of the pilot we define success in writing. If we miss it in the main phase, we do not invoice the success fee.

Phased fees

Discovery and the pilot are standalone, calculable steps. A precise price comes after Discovery — it differs from system to system.

Proof and credibility

15+ years, ISO 27001 and ISO 9001, regulated industries. ReFactor builds on existing UDEMX strengths.

  • ISO 27001 / ISO 9001
  • 15+ years of software delivery
  • Java, Kotlin, .NET, PHP, Golang, Kubernetes

Merkantil Bank

Regulated finance and PSD2-related delivery — modernization where downtime is not an option.

OBH — courts

Public-sector, business-critical systems where reliability and compliance come first.

TEVA

More than 10 years in pharmaceuticals, in a regulated and audited environment.

EPS Global

Long-term technology partnership on business-critical processes.

Exclusive Change

Financial services, where a safe, gradual cutover is essential.

Who ReFactor is for

Hungarian mid-size companies that can pay, feel real pain — and whose decision-maker is reachable.

A good fit if

  • roughly 50–250 people, a stable, profitable company
  • an 8+ year in-house system (Delphi, legacy PHP, .NET Framework, old Java, Access/Excel)
  • manufacturing, logistics, finance, pharma, energy or services
  • the decision-maker is CEO, owner, CTO, COO or CFO

Not a fit right now if

  • the system was recently modernized, or you run packaged software
  • there is no real pain, or the budget matches a company under 20 people

Frequently asked questions

How can you rewrite our system module by module if it is not modular?

The legacy system does not need to be modular — we create the modules on the new side. Through a seam (a gateway in front of the old system, or at screen level) we replace one business capability at a time while the rest keeps running. This is the proven gradual modernization pattern designed for tangled monoliths.

What happens to our data if we share one database?

This is the most critical part of the process, so we treat it as such. During the transition the old and new systems typically share the same database, so consistency is preserved; we split data ownership only later, in a controlled way. Where separate data stores are needed, we use synchronization and automated reconciliation, and we avoid a risky one-shot data migration.

Do we have to stop operations during the cutover?

No. The legacy system keeps running while we go live capability by capability. There is no overnight big-bang switch — the change is gradual and reversible, so daily operations do not stop.

What if it still fails?

The process starts with a paid assessment and a pilot, where we prove the seams and the data strategy before committing to the full scope. In the main delivery phase part of the fee is tied to a jointly defined success metric: if we miss it, we do not invoice the success fee. We therefore carry part of the risk.

How much does it cost and how long does it take?

A precise price and timeline come after the paid Discovery, because this differs significantly from system to system. Discovery itself is a valuable deliverable: an architecture map, a risk list, a modernization roadmap and an estimated ROI — even if you do not continue with us.

Will our data stay safe? Can we stay compliant?

UDEMX is ISO 27001 (information security) and ISO 9001 certified, and we have delivered in regulated environments (finance, pharma, public sector). A modern cloud-native system can also run on your own servers (private cloud), so you do not have to hand data to a public cloud provider.

What happens to the old system and the current team?

We do not throw the legacy system away overnight — we retire it as new capabilities go live. We involve the existing team and transfer knowledge, so you end up with a modern, well-documented system that is easier to maintain and staff.

Request a free discovery consultation

30 minutes, no obligation. We will see whether ReFactor is a real fit for your system.

I accept the privacy policy.