Where it started
A telecommunications and internet group had to vacate its existing data centre. The reason was legal (end of life, compliance audit), and the date was fixed. The entire system landscape was to move into a hybrid target architecture of co-location and public cloud. At the same time, an old database platform was to be replaced.
Several teams, internal business units and a hyperscaler were involved.
How the bottleneck showed
Nobody could say for sure what could move when. Every system depended on other systems, and how strongly was often known only to individual people. Without that view, neither a migration plan nor an order could be set, and the date came closer.
Where it came from
Everyone involved planned on their own: the teams for their systems, the business units for their requirements, the hyperscaler for its platform. There was no shared view of systems, dependencies and the maturity of the teams. The planning was as scattered as the organisation.
What we did
Process
We fully mapped the current and the target system landscape and assessed the maturity of every team. We made gaps in systems and workflows visible with GAP analyses and system audits. We collected the technical requirements and turned them into decision papers for management.
IT
We defined the target architecture. Legacy systems were deliberately moved into modern, scalable architectures instead of just being shifted. For the old database platform there was a readiness check and a concept for replacing it. We coordinated the technical implementation, from the initial inventory to operation in the new environment.
What stays
The shared view led to migration blueprints and release plans. With them, the teams could plan and steer the move themselves.
