Legacy Decommissioning and ETL Integration for Healthcare Education
Architectural planning, ETL data integration, and operational design supporting decommissioning of legacy training systems in favour of a unified Java 8 web-based workforce platform.
Multiple legacy systems holding national workforce data that needed to come into one platform without breaking operational use.
A national healthcare education body was running its trainee, administrator, and training provider workflows across multiple legacy systems. The replacement programme could not afford a hard cut-over: regional operations had to continue running while data was migrated, ETL integrations rebuilt, and operational teams transitioned to a new way of working.
The architectural and integration work needed someone who could hold legacy decommissioning planning alongside live programme delivery, working with engineering, data, and service teams to keep both sides moving.
Architectural planning, ETL integration design, and operational continuity.
We supported the architecture and integration workstream while also leading BA delivery on the core platform, working in Jira, Confluence, and GitHub.
- Supported architectural planning for legacy system decommissioning and cut-over
- Designed ETL data flows, ERDs, and integration logic feeding the new Java 8 platform
- Worked with the service team to resolve operational issues identified during cut-over
- Coordinated UX, data, and development teams around shared dependencies in GitHub
- Documented integration points in Confluence to support ongoing maintenance after handover
- Embedded ways of working including ScrumBan ceremonies that the permanent team could continue using
Integration-first, service-aware, continuity-led.
Delivery used ScrumBan with Jira, Confluence, Slack, and GitHub, supported by Tableau and Metabase reporting. ETL flows used the organisation's standard data tooling. Integration and decommissioning planning assumed regional operations had to continue throughout.
Clean legacy decommissioning path with operational continuity preserved.
- Architectural plan for legacy decommissioning, signed off by engineering and service teams
- ETL data flows and ERDs documented in Confluence for ongoing platform maintenance
- Service-side issues identified during cut-over resolved without disruption
- Integration points documented and handed over to the permanent team