Skip to content

What should be examined in an integration current state assessment?

Digitalisation Integrations
17.11.2026

In many organisations, integration issues only come to light when changes need to be made. For example, an organisation may embark on an ERP renewal project, introduce a new service, or look to automate its business processes. It is often at this point that employees realise that no one has a clear understanding of how the organisation’s systems actually communicate with one another.

This is why assessing the current state of integrations is one of the most important steps before major organisational changes. The assessment does more than simply list the systems and key interfaces currently in use. It also provides an overall picture of how information flows through the organisation, where the greatest risks lie, and which integrations are truly business-critical.

The system map as the foundation of a current state assessment

A current state assessment typically begins with creating a system map. In practice, this means identifying which systems the organisation uses and how they are connected. Some connections are easy to identify: the billing system communicates with the ERP system, the online store transfers orders to the ERP, and the HR system passes information on to payroll.

In reality, however, the overall system landscape is often more complex. It may include integrations built over the years that have never been properly documented. Some data transfers may run through external service providers, while others may rely on legacy technical solutions that no one has reviewed in a long time.

Identifying business-critical integrations

One of the most important steps in a current state assessment is identifying the integrations that are critical to the organisation’s business operations. Not all connections are equally significant in themselves, but some are directly linked to the company’s core processes, such as order management, invoicing, payment transactions, production planning, payroll and reporting.

Disruptions to these processes can quickly affect business operations. For example, if an order fails to transfer from the online store to the ERP system, or an invoice is not generated, the impact can soon be felt in both the customer experience and cash flow. This is why a current state assessment should go beyond simply listing technical connections. It should also establish a clear understanding of which business processes the integrations actually support.

Interviews as part of a current state assessment

Over the years, knowledge of an organisation’s integration environment can become concentrated among a handful of individual experts and buried in old email threads. This makes identifying and capturing tacit knowledge a critical part of the assessment. Interviews with key individuals therefore play an important role in uncovering hidden dependencies. For example, a reporting process may depend on a single data transfer, or an otherwise routine business function may rely on an old integration whose significance has long since been forgotten.

Manual work and integrations

As part of the assessment, it is important to identify where information is still transferred manually. In many organisations, gaps in automation are still being addressed through manual work: data is transferred between systems using Excel spreadsheets, CSV files or email. Solutions that were originally intended to be temporary can easily become a permanent part of everyday operations.

Manual work is not just inefficient. It also increases the risk of errors and ties up specialists’ time with tasks that could be automated. At the same time, it makes the organisation more vulnerable, as responsibility for critical information may rest with individual employees.

Monitoring provides visibility into integration issues

A current state assessment should also examine how integrations are monitored. Problems are often only detected when a user reports an error or a business process comes to a complete standstill. Particularly when it comes to business-critical integrations, organisations should be aware of potential disruptions before they affect customers or end users.

Effective, continuous monitoring helps identify issues quickly and significantly reduces their negative impact on business operations.

A current state assessment provides visibility into the digital environment

The value of a current state assessment becomes particularly clear when planning future development initiatives. When the starting point is fully understood, projects such as ERP renewals, cloud migrations and integration modernisation can be planned and managed much more effectively. It also helps avoid situations where critical dependencies are only discovered once a development project is already underway.

A well-executed current state assessment supports decision-making, helps prioritise development activities and brings hidden dependencies to light. Ultimately, it is about more than integrations. It is about how well an organisation understands its own digital environment.

Need help with your integrations? Get in touch and let’s find the right solution for your organisation.