OYA modernised its technology foundation with a controlled cloud migration
OYA operates in a financial services environment where technology supports users, client communication, business applications, document workflows, Microsoft 365, security controls, backup and day-to-day operational continuity. As the business environment became more cloud-dependent, OYA needed a migration approach that improved platform resilience and supportability without creating unnecessary operational risk. The requirement was not simply to move workloads — it was to modernise the way systems, identity, data protection and support operated after migration.
Inlight IT supported OYA with a controlled cloud migration focused on planning, identity, Microsoft 365, workload readiness, backup, access control, security configuration and post-migration support. The outcome was a more supportable cloud operating model: stronger Microsoft platform alignment, clearer identity and access control, improved resilience, better backup awareness and a more practical foundation for ongoing managed IT.
- Client
- OYA
- Industry
- Financial services
- Environment
- Financial services environment supporting users, client communication, business applications and Microsoft 365
- Starting point
- An increasingly cloud-dependent environment needing stronger resilience and supportability
- Engagement type
- Controlled cloud migration: planning, identity, Microsoft 365, backup, access control, security configuration and post-migration support
- Approach
- Structured transition — assessment, planning, migration execution, validation and post-migration support
- Outcome
- A more supportable cloud operating model with stronger Microsoft alignment, clearer identity and improved resilience
OYA — controlled cloud migration
A migration judged by supportability and control, not just hosting location.
A cloud migration judged by supportability and control
Identity and Microsoft 365 treated as core migration components, not downstream tasks.
Assessment, planning, migration execution, validation and post-migration support — systems moved through a controlled pathway with validation.
Availability, confidentiality, access control and recovery — recovery kept as part of the cloud design, not assumed after cutover.
The migrated environment moved into a supportable, managed operating model after go-live.
For a financial services business, a cloud migration has to reduce operational friction, not create new ambiguity
Cloud migration can be treated too narrowly as a workload movement exercise. That is rarely enough for a financial services environment.
The migration needs to account for identity, access, Microsoft 365 configuration, business applications, data location, backup, recovery, user experience, endpoint access, security controls and post-migration support. If those areas are not considered together, the business may end up with a cloud environment that is technically migrated but operationally harder to manage.
For OYA, Inlight IT's role was to support a controlled migration that improved the operating model around the technology, not only the hosting location.
OYA needed a cloud migration that improved resilience and supportability, not just infrastructure location
Financial services environments carry higher expectations around availability, confidentiality, access control and recovery. A migration needs to reduce operational friction, not create new ambiguity.
Identity and access were central, not incidental
In a financial services environment, who can access what — and how that access is controlled — is a core part of the migration, not a downstream configuration step.
Microsoft 365 had to be configured deliberately
Microsoft 365 configuration, business applications and document workflows needed to be migrated and configured with operational controls in mind, not just moved.
Recovery had to be designed in
Backup, recovery and resilience expectations are higher in financial services. Recovery had to be part of the cloud design rather than assumed after cutover.
Security and compliance evidence mattered
Secure document workflows, access control and the kind of evidence financial services businesses rely on — including for cyber insurance — had to be considered as part of the migration.
The operating model mattered more than the hosting location
The requirement was not simply to move workloads — it was to modernise the way systems, identity, data protection and support operated after migration.
A controlled cloud migration connected to identity, Microsoft 365, backup, security and managed operation
Inlight IT supported OYA by treating cloud migration as a structured transition. The engagement focused on assessment, planning, migration execution, validation and post-migration support.
01Start with the environment, not the destination
The migration started with the environment, not the destination platform — understanding how users work and how systems depend on each other before moving anything.
02Treat identity and Microsoft 365 as core
Identity and Microsoft 365 were treated as core migration components, with access control and security configuration designed deliberately.
03Move through a controlled pathway
Systems were moved through a controlled transition pathway, with validation to protect continuity.
04Keep recovery in the design
Recovery remained part of the cloud design, so backup and restore confidence was built in rather than retrofitted.
05Move into a supportable operating model
The migrated environment moved into a supportable operating model, with managed operation after go-live.
A structured transition from assessment to managed operation
Select a stage to trace how the environment moved through a controlled migration into managed operation.
Financial services cloud environments need resilience, security and control
Financial services organisations increasingly rely on Microsoft 365, cloud applications, remote access, secure document workflows, client communication, backup, compliance expectations and cyber insurance evidence. Cloud migration can support those needs, but only if it is designed with operational controls in mind. For OYA, that meant a migration judged by supportability and control, not just hosting location.
A structured transition in five stages: assessment, planning, migration execution, validation and post-migration support.
The environment came first, not the destination platform — how users work and how systems depend on each other, before moving anything.
Four expectations financial services carries: availability, confidentiality, access control and recovery.
One supportable, managed operating model for the migrated environment after go-live.
OYA gained a more supportable cloud environment for its financial services operating model
The engagement helped OYA move into a more mature cloud operating model. The outcome was not only migrated services — it was improved supportability across Microsoft 365, identity, access, backup, security and managed operation.
Stronger Microsoft alignment
Microsoft 365 configured and aligned to the way the business operates.
Clearer identity and access
Identity and access control made clearer and more consistent across the environment.
Improved resilience
Recovery designed into the cloud environment rather than assumed.
Better backup awareness
Backup posture made visible and part of the operating model.
Supportable managed operation
The environment moved into a practical foundation for ongoing managed IT.
A controlled, validated transition
Systems moved through a controlled transition pathway, with validation to protect continuity.
The outcome was not only migrated services. It was a migration judged by supportability and control, not just hosting location.
Cloud migration as an operating model change, not a hosting change
Financial services operating context
Migration designed around availability, confidentiality, access control and recovery.
Microsoft 365 aligned
Microsoft platform configured deliberately, not just moved.
Identity treated as core
Access control and identity designed as central migration components.
Recovery in the design
Backup and recovery built into the cloud environment.
Controlled transition
Systems migrated through a validated, structured pathway.
Managed after go-live
Environment moved into a supportable managed operating model.
The work connected cloud migration, security and managed cloud operations
Migration and planning
6- Cloud migration
- Environment assessment
- Migration planning
- Workload readiness
- Validation
- Controlled transition pathway
Identity and Microsoft 365
6- Microsoft Entra ID
- Identity and access control
- Conditional Access and MFA
- Microsoft 365 configuration
- Business applications
- Document workflows
Security and resilience
6- Microsoft Defender
- Security configuration
- Secure document workflows
- Backup and recovery design
- Restore confidence
- Cyber insurance evidence
Managed operation
6- Managed cloud operations
- Post-migration support
- Supportable operating model
- Backup awareness
- Ongoing managed IT
- Managed operation after go-live
Planning a cloud migration that needs to strengthen security, resilience and supportability?
We assess where cloud fits your operating model, then plan the migration.
Discuss cloud migration and managed cloud