How can we help
Cloud migration success
Telco pulls off hassle-free cloud migration in 6.5 hours
Outdated infrastructure in a digitally first environment
An Ireland-based telco, which first launched in 2012, had since lost its luster in a digitally driven mobile market and eventually struggled to scale its applications. The telco was due for a major overhaul of their its digital infrastructure, which was impeding overall network availability and driving up infrastructure and license costs. Scalability issues also affected the company’s capability to respond to customer queries during peak hours.
Our approach to cloud migration
Our Migration Process
Due Diligence
Due diligence phase ensures the availability of all the pre-migration checklist items so that we ensure the readiness to start the analysis work.
Impact Assessment
Keeping the target state as a reference, this step is performed to assess customer journey compatibility, data compatibility, User Interface compatibility, External Interfaces compatibility and Data Integration compatibility. The impact should be documented and will involve different teams within your enterprise to be consulted over a series of deep-dive workshop sessions.
Migration and Rollback Solution Design
Based on the impact analysis, the technical solution is created and documented. This contains information such as criteria for selection of customer data subset, sequence, user journeys, etc; and the logic for migration in the forms of flow charts and sequence diagrams. Sanity testing approach and rollback approach is identified and documented. The scope extends to User Interface channels. Integration layer and Source/Target systems.
Migration Sandbox Environment Setup
One of the challenges faced by most enterprises is lack of “playground” area with production-like data to develop and test any migration solutions. In most cases, the combination and variety of data in development and test environments of legacy apps. This step is to build a sandbox environment along with data setup. In alignment with your IT Governance and regulatory restrictions, data from production can be loaded in the sandbox after de-sensitization and anonymization. Similarly, a sandbox on the target cloud system should be made available.
Migration Prototyping
Once the data in sandboxes in source and target systems are ready, key assumptions and high-risk scenarios are validated by creating series of prototypes. Based on the result of the prototype, the design/approach/steps/etc are updated. Prototyping phase should include validating the rollback strategies as well.
Migration Script Development and Prelim Testing
Based on the results of the prototype, migration scripts are developed and tested iteratively in the sandbox environment. This includes simultaneous changes to the channels to create the environment as close as possible to the target Blue-Green deployment strategy. The rollback strategy should extend to the channels as well. Once the migration/parallel run is simulated in the Sandbox environment, a dry run is conducted in the production environment with limited scope to detect any surprises.
Failure Simulation and Rollback Dry Run
Based on the dry run, failure scenarios are identified and addressed in the migration scripts, Channels and Integration flows. Errors are simulated and rollback is tested in the Sandbox. Once working in the sandbox, a dry run of rollback is conducted on Production.
Iterative Migration Execution
Based on all the previous steps, the migration solution is industrialized and integrated in the production environment to kick start the phase-by-phase migration. Any further surprises (should be minimal at this stage) are addressed and fixed in the migration solution.
Decommissioning
After extended period of parallel run, and after migration of all user data, processes, etc. the legacy system is decommissioned. The integration layer is simplified and all calls to legacy are removed. The new Cloud system functions as the master. The channel specific routing changes are retained to support Blue/green deployment strategy for future enhancements.
 |
What cloud migration services do you need? |
- Monolith legacy application to cloud-native migration
- SaaS enablement of your digital offering
- Cloud-to-cloud migration
- Establishing multi-cloud architecture
- Migrating a non-premise application to a hybrid cloud model
- Migrating your legacy applications to serverless architecture
- Application study, identify code seams, and decompose into microservices
- Design and develop the microservice components progressively by gradually reducing the dependency on the monolith
- Setup a cloud-native architecture to containerize and scale using Docker and Kubernetes
- Manage, control and monitor the use of these microservices using a Service Mesh
- Deploy in a public or private cloud that best fits your enterprise and operational needs
- Establish DevOps and CI/CD pipelines
- Cloud migration assessment questionnaire and workbook
- Legacy to cloud-native kit
- Sentinel – our in-house cloud cost optimization and unified monitoring solution
- Third-party tools like Infra-as-a-Code solutions such as Ansible, Terraform, etc.
- THIS DevOps Reference Framework
