Migration of existing systems for interoperability
A system may still serve its users while its technology becomes difficult to maintain. Replacing it risks losing working behaviour and years of information.
How this work runs.
One run, start to finish. A box with an accent tick is a tool acting and opens its own page; a rounded box is an artefact or a record; a diamond is a decision the work cannot pass without. A dashed line is a hand-off the suite has not mechanised yet.
- sends a scoped job
- A job sent to the tool that does it, with its limits written in. What comes back is a record of the result.
- reads what the other publishes
- Nothing is sent. The next tool reads what the one before it has published, at the moment it needs it.
- adds to a running record
- A new entry on a record that only grows. Whoever needs it reads it later, and neither side waits.
- hands over a task
- A piece of work still owed, with an owner and a next step. It stays open until someone closes it.
The existing system and its legacy records are recomposed on the framework, the records are conformed as they cross, and the result is parity-proved before it ships.
Each step in the order it runs, and where one stops before the next begins.
- 01RUN · toolSCRIBE Reconciles the legacy records, keeping every correction a person makes.Nothing in this run reaches it. Hands on to SAVED CORRECTIONS.
- 02RECORDEXISTING APP A record the run reads, writes or hands on.Nothing in this run reaches it. Hands on to HELM.
- 03RECORDEXISTING APP + LEGACY DATA A record the run reads, writes or hands on.Nothing in this run reaches it. Hands on to HELM.
- 04GOVERN · toolHELM Scopes the migration, hands it to Forge and tracks it.Reached from EXISTING APP, EXISTING APP + LEGACY DATA. Hands on to FORGE (CONVERT).
- 05RECORDSAVED CORRECTIONS A record the run reads, writes or hands on.Reached from SCRIBE. The run parks here.
- 06RUN · toolFORGE (CONVERT) Rebuilds the existing app on Frame.Reached from HELM. Hands on to FRAME, RUN NOTES.
- 07RECORDRUN NOTES A record the run reads, writes or hands on.Reached from FORGE (CONVERT). Hands on to GIMBAL.
- 08SUBSTRATE · toolFRAME The rebuilt app runs on it.Reached from FORGE (CONVERT). Hands on to BUILT APP, MIGRATED APP.
- 09PROPOSE · toolGIMBAL Reads the run notes to tune how the next run is resourced.Reached from RUN NOTES. The run parks here.
- 10RECORDBUILT APP A record the run reads, writes or hands on.Reached from FRAME. Hands on to GAUGE.
- 11PROPOSE · toolGAUGE Proves the rebuilt app matches the old one and flags any difference.Reached from BUILT APP. Hands on to FLAGGED FOR REVIEW, SHIPPED, MIGRATED APP.
- 12RECORDFLAGGED FOR REVIEW A record the run reads, writes or hands on.Reached from GAUGE. The run parks here.
- 13RECORDSHIPPED A record the run reads, writes or hands on.Reached from GAUGE. The run parks here.
- 14RECORDMIGRATED APP A record the run reads, writes or hands on.Reached from FRAME, GAUGE. Hands on to STEWARD.
- 15RUN · toolSTEWARD Hosts the migrated app.Reached from MIGRATED APP. The run parks here.
- 01picked upHELM EXISTING APP.Matter the run starts from. No member of the suite put it there.
- 02sends a scoped jobHELM → FORGE (CONVERT) sends a scoped job.A job sent to the tool that does it, with its limits written in. What comes back is a record of the result.
- 03reads what the other publishesFORGE (CONVERT) → FRAME App config.Nothing is sent. The next tool reads what the one before it has published, at the moment it needs it.
- 04hands onFRAME → GAUGE BUILT APP, BUILT APP.A step following the one before it.
- 05parks hereGAUGE FLAGGED FOR REVIEW.Any difference found.Nothing later in this run reads it, so this is where that branch of the run stops.
- 06parks hereGAUGE SHIPPED.Nothing later in this run reads it, so this is where that branch of the run stops.
- 07adds to a running recordFORGE (CONVERT) → GIMBAL Run notes.A new entry on a record that only grows. Whoever needs it reads it later, and neither side waits.
- 08picked upHELM EXISTING APP + LEGACY DATA.Matter the run starts from. No member of the suite put it there.
- 09parks hereSCRIBE SAVED CORRECTIONS.Corrections.Nothing later in this run reads it, so this is where that branch of the run stops.
- 10hands onFRAME → STEWARD MIGRATED APP, MIGRATED APP.A step following the one before it.
What this work delivers.
A rebuilt system on a maintainable framework, with its existing behaviour checked and its historical data reconciled.
Record the baseline
Inspect the running system, its users, its data and the behaviour people depend on.
Plan the migration
Choose the target framework and map existing constructs to it. Identify gaps and changes that need an owner’s decision.
Rebuild and reconcile
Forge rebuilds the application while Scribe maps legacy data to the target structure.
Check the result
Verify behaviour and data fidelity before the owner approves release.
Migration is appropriate when the software itself needs to change. A system that works well may need only a data mapping or connection.
Explore data mapping insteadWhich tools, in what capacity.
Put this to work in your context.
Tell us what you need to achieve and what you already have.