Know what connects to what before you change it

Most integration estates are documented in a wiki that was accurate once. Discovery reads the systems themselves and shows you what data sits where, what it means and what depends on it.

When it is the right first step

  • A replacement is planned. Nobody can say for certain what breaks when the old system is switched off.
  • The knowledge has left. The people who built the integrations have moved on, and what they knew went with them.
  • An estimate depends on it. A migration or modernisation budget turns on how many fields and rules there are, and nobody has counted.
  • Someone has asked. An auditor, a regulator or your own risk function wants to know which systems feed which.

What you get

  • A map of the systems in scope. What data each one holds, how the engine has classified it, and how it relates to data in the others.
  • The mapping model. Field-level correspondences between the systems, each with the confidence score the engine assigned to it.
  • A spreadsheet export. The mapping in a form your team can check, argue over and reuse without access to the engine.
  • A report and a review. What we found, what it means for the decision in front of you, and what we would do next, walked through with your team.

How it runs

  1. Agree the scope. Which systems, which data, and which decision the work has to support.
  2. Install the engine in your environment. It connects to the systems in scope. Read access is all it needs for this.
  3. Classify and map. The engine works out what each element means and how it relates to the others. Where it is unsure, it flags the element instead of guessing.
  4. Review and hand over. We go through the findings with your team and hand over the report, the model and the export.

How it is priced

Fixed price, for a scope agreed before we start.

If the data shows the scope needs to change, we agree that with you first. The price does not move on its own.

What you provide

  • Hosts for the engine, sized to the data in scope. The tiers are on the technical page.
  • Read access to the systems in scope.
  • Someone who knows the systems, for the review sessions.

What it is not

It is not an architecture strategy. Discovery tells you what is there and what depends on what. What to do about it is your decision, though we will tell you what we would do.

If the engine stays installed afterwards, what it has classified stays in the graph store in your environment. A migration or an integration project then starts from that, instead of repeating it.

Tell us what you need to move or connect

We will tell you whether this is the right service for it, or which one is.

Book a demo