System replacement

Replacing SAP, Oracle and Salesforce without losing your processes

We help replace a system that is no longer available: the business logic is preserved, the data is migrated, the accounting integration stays, and the platform runs in a controlled environment.

Discuss a project Common questions

Stack and integrations

FastAPI PostgreSQL RabbitMQ Docker On-premise Grafana

In short

What we build: Replacing SAP, Oracle, Salesforce and other foreign ERP or CRM systems with a local platform.
Who for: Companies whose foreign licences have become a risk or are unavailable, with critical processes running on them.
Stack: FastAPI with PostgreSQL, accounting integration over HTTP/OData/files, RabbitMQ, on-premise, Grafana.
Timeline: A pilot process in six to ten weeks, a phased migration in six to twelve months. In a bank or a critical-infrastructure operator, three to five years.

A good fit when

→ Licences for the foreign system have become a risk
→ You need a link to your accounting system and internal services
→ The process is too specific for an off-the-shelf product
→ On-premise deployment, auditing and readiness for security requirements are mandatory

What you get

→ An audit of current processes and a function replacement matrix
→ Migration of reference data, documents and history
→ Integration with accounting, BI, warehouses, document management and LDAP/SSO
→ A phased launch plan that does not stop the business

Process

01 An inventory of functions and data
02 A pilot of one key process
03 Migration, parallel running, and retiring the old system from the critical path

Why not an off-the-shelf product

Custom development earns its place where your processes matter.

Ready-made SaaS is good for standard scenarios. But once the business logic depends on specific roles, documents, integrations, security or data, the cost of the workarounds quickly exceeds the cost of a proper architecture.

We start with discovery, separating what genuinely has to be built from what is cheaper to cover with an existing service. That is why the project ends up smaller, clearer and easier to run.

Related cases

Common questions

Do you replace SAP completely?

Usually in stages: the critical processes first, then the lower-risk modules.

Can historical data be preserved?

Yes. We design the migration and archive access separately, so the new system does not inherit complexity it does not need.

Do you work under regulatory constraints?

We account for segmentation, logging, on-premise deployment and operational documentation requirements.

What does a replacement project cost?

Projects of this class vary widely with the volume of functions and data. We start with an audit, after which the full migration budget is fixed rather than guessed.

How long does moving off SAP take?

A pilot of one key process takes six to ten weeks. Full migration of large modules takes six to twelve months with the old system running in parallel. In regulated environments the driver is regulatory reporting and acceptance testing, and the honest figure is three to five years.

Is there a real project behind this?

Replacing a foreign WMS with a local one, integrated with the accounting system and deployed on-premise. The write-up is on the cases page.

Is there an off-the-shelf product instead?

For CRM and ERP there are local products, and we will point you to them. We take the work when an off-the-shelf system covers less than half of the processes or needs customisation that defeats the point.

Written up in more detail

Next step

Let us go through your problem.

We will show you a possible architecture, the risks, the order of the budget and what an MVP could prove.

Discuss a project