Stabilising a stalled AD and Microsoft 365 migration
When every migration wave brings new incidents: identify the causes, test each wave in advance and restore the support team's ability to act.
- Banking & financial services
- Public sector
- Industry
You stabilise a stalled AD and Microsoft 365 migration by first evaluating the open incidents and clarifying the dependencies between identities, clients, group policies and applications. After that, further waves run only with a test concept and clear approval. FlixConsulting takes on incident and migration management for this and puts the support processes in order.
Where organisations stand
- The Active Directory changeover and the integration into Microsoft 365 are under way. With each migration wave, the number of incidents rises.
- Clients, group policies and applications behave unexpectedly after the changeover. The causes are hard to pin down.
- Support and the project team work in separate tracks. Tickets pile up and the schedule comes under pressure.
How we work
- 01
Analysis
We evaluate the open incidents and analyse the dependencies between identities, clients, group policies and applications.
- 02
Target architecture
We revise the group policy design and define a configuration and test concept for the further migration waves.
- 03
Delivery
We manage the client migrations with tests before each wave, adapt affected applications including PaaS applications and run structured incident management.
- 04
Handover to operations
We hand over clear support and ticket processes, the documentation and the lessons from retrospectives to business-as-usual operations.
What changes afterwards
- Incidents are traced back to their causes instead of being fixed one by one.
- Further migration waves are tested and run with clear approvals.
- Support and operations work with structured ticket processes, even after the project ends.
Banking sector: incident and migration management during an Active Directory changeover with Microsoft 365 integration and client migrations.
Questions about this use case
Does the migration have to be stopped for stabilisation?
Not necessarily. It is often enough to postpone the next wave until the causes are clear and the tests are defined. We make this decision together with you, based on the incident analysis.
Do you work with the existing project team and service providers?
Yes. We complement the existing team and bring support and project together in a joint incident and migration process. At the end, we hand over the processes to business-as-usual operations.
Let us talk about your project.
No obligation, confidential and with a concrete next step.