Skip to main content
Free tool from Domin Software

System integration planner

Structure one data flow between two applications and generate a map you can review internally or send for an initial assessment.
Illustration of two distinct systems connected by a controlled data flow with validation checkpoints

Start with one data flow

You do not need to choose a protocol or architecture. Start with one process: what triggers the flow, where the data originates, where it should go and how success is confirmed. The planner organises those decisions without assuming that an API exists.

The result is created locally in your browser. It is not a technical specification, feasibility confirmation or automatic estimate.

Our system integration and data-flow automation services describe how we can help implement this type of flow. For the first conversation, provide the system names, one process and the questions still to be resolved.

Describe one data flow

Complete only the fields you can answer. Open questions are a useful part of the plan.

Do not enter passwords, tokens, certificates, database copies or real customer or employee data. Name the data type and use an anonymised example.

Systems and flow trigger

Name both systems and the event that starts the flow.

Where is the information created? For example, an online store.

Where should it go? For example, an order fulfilment system.

For example, payment confirmation or form approval.

Choose the current state of knowledge.

Data, ownership and direction

Define the data scope and how matching records are recognised.

List only the data required in the first stage.

For example, the store owns the order and the warehouse owns availability.

For example, the store order number stored as an external ID.

Choose the closest scenario.

Timing and confirmation

Set the frequency, acceptable delay and proof of success.

Choose the expected cadence.

For example, up to five minutes or by the end of the working day.

For example, the target system returns its case number.

Failures and reconciliation

Plan safe retries, exceptions and discrepancy detection.

For example, a temporary timeout.

For example, when a customer cannot be matched unambiguously.

For example, a daily list of operations without confirmation.

Give a role or team, not a person's name.

First stage and unknowns

Separate the smallest useful scope from later work.

The smallest scope that provides a useful result.

For example, historical data or reverse synchronisation.

For example, API limits, documentation or a test environment.