Phase 2

Architecture and Applications

By Redaktion techport.ai, IT-Beratung · Last updated on 21 August 2026

Ask a mid-sized company how many applications are in use and you get a number. Count them and it is usually twice as many. In between sit spreadsheets that are effectively systems, databases an employee built twelve years ago, and cloud services paid for by credit card.

Architecture sounds like a task for corporations. In a mid-sized company it comes down to something simpler: knowing which system is authoritative for which task, how the systems talk to each other, and which of them will have to be replaced in the coming years. Those three answers make every subsequent decision easier.

Typical problems

The same customer or article number exists in four systems, each with different data.
An interface between two central systems was built by a former employee and nobody can change it.
The ERP is so heavily customised that a version upgrade is considered impossible.
There is a cloud strategy, but half the systems still run in the basement and nobody decided why.
Every new requirement leads to a new tool because nobody knows what already exists.

What we do in this field

We record your application landscape and present it so that it can be explained in a single meeting: which system carries which process, where data originates, what is duplicated and what is being phased out. We prepare the ERP decision with an assessment of staying, switching and rebuilding. We plan interfaces so that they are documented and maintainable. We retire legacy systems step by step rather than in one big jump. And we settle with you what belongs in the cloud and what does not, with an eye on cost, operations, law and dependency.

Topics in this field

Cleaning up the application landscapeWhich systems carry which process, where data originates, what is duplicated and what is being phased out. An overview that speeds up decisions instead of filling folders.Settling the cloud questionCloud decisions per system rather than across the board: cost over the term, operations and specialists, legal requirements, vendor dependency and a defined way back.Focus topicERP strategy and system changeHow to prepare the ERP decision: assess the state of the system, review customisations, estimate migration cost realistically, plan around maintenance deadlines and make the rollout predictable.Interfaces and integrationHow systems talk to each other properly: define the authoritative system, document interfaces, handle error cases, use an integration platform where it fits and limit dependencies.Retiring legacy systemsHow to replace systems without vendor support, without specialists and without documentation: assess the risk, separate the functions, replace step by step rather than in one jump.

Häufige Fragen

Is documenting the application landscape worth it if it is out of date immediately?

It only goes out of date if it is too detailed. An overview at the level of system, process, data origin, owner and contract end stays valid for two to three years and answers ninety percent of the questions that come up in daily work. Anything deeper belongs in the systems themselves.

Should we move everything to the cloud?

No, and nobody seriously does. The cloud makes sense where you use standard software, where load fluctuates or where you lack the specialists to run things yourself. Arguments against it can be latency in production, specific contractual requirements from customers, and cost when base load stays consistently high. The decision is made per system, not across the board.

Let us talk about your situation

In a thirty minute first call we work out where your biggest lever sits and whether we are the right people for it.

Arrange an initial call Our software