Inventory & dependency mapping
Batch schedules, stored procedures, and forgotten FTP drops—documented with owners and failure modes.
Consulting overviewPretoria · On-site & remote
We walk alongside engineering leads who inherit COBOL batches, monolithic Java estates, or vendor-locked ERP extensions—and need a migration path their board will fund and their operators will trust.
Our work sits at the intersection of code archaeology and delivery planning: naming what must keep running, what can be strangled, and what evidence you need before cutover weekend.
Batch schedules, stored procedures, and forgotten FTP drops—documented with owners and failure modes.
Consulting overviewHonest trade-offs between rehost, rewrite-in-place, and phased extraction for your compliance regime.
Read our field notePlaybooks, rollback criteria, and paired hours during dry runs—not a slide deck left at the door.
Migration executionA municipal utilities back-office still posted ledger entries through a 1990s client-server suite. Silicon Relay spent six weeks mapping interfaces to a newer billing hub, then coached two in-house developers through a strangler release that kept nightly balancing intact.
They insisted we record every manual workaround before touching code. That felt slow on week one; by week four it saved us from migrating a report nobody had run since 2018.
— Thabo M., application manager, utilities sector
The Legacy readiness review is a fixed-scope engagement: one primary system, up to three integration points, and a written recommendation you can attach to a funding memo. Most reviews complete in ten working days.
Request availability