Flows

Four directions data travels. One discipline for all of them.

Every flow we build has a source, written transformations, a staging stage where needed, an agreed handoff and a run record.

Flow type

System to system

The most common case: one business system produces an export and another needs to import it. Column names differ, date formats differ, codes mean slightly different things. Someone currently bridges the gap by hand.

We document the mapping field by field, build the transformations, and run them to a schedule. If either system changes its layout, the run record flags the change instead of passing on a broken file.

You provideLegitimate exports, the target import template, a named owner on each side.

You receiveImport-ready files, a mapping document, run records.

Flow type

Team to team

Operations creates data that finance, planning or customer service rely on. The receiving team often re-keys or reshapes it because the original layout suits the creator, not the user.

We sit between the two, agree what each side needs and produce an output that suits the receiver without forcing the creator to change how they work. The handoff agreement names a person on each side.

You provideAccess to how the data is created today and who uses it.

You receiveA shaped output on a reliable schedule, and an agreement both teams signed off.

Flow type

Organisation to partner

Exchanges with suppliers, customers or contractors are harder because you only control one end. Layouts drift, files arrive at odd times, and nobody is sure who should fix what.

We help agree a layout with the partner, transform inbound or outbound files to match it, and stage them where both sides can rely on them. What may be shared with a partner is your decision, taken with your own advisers.

You provideA partner contact, the agreed scope of what is exchanged.

You receiveA shared layout description, transformed files, a record of each exchange.

Flow type

Old to new

When a system is replaced, data has to move once, correctly. Migrations fail when transformations are improvised on the day.

We treat a migration as a flow that runs a handful of times: rehearsals on approved test extracts, checks by the people who will use the new system, then a final run with counts reconciled on both sides.

You provideExtracts from the old system, the new system's import rules, people to check results.

You receiveRehearsal reports, a final run record, and a list of anything that could not be carried across.

Most real flows mix two of these.

Describe yours and we will tell you how we would split it into handoffs.