Azure
Hybrid Cloud

Azure Cloud Migration cases

Migrate to cloud and get an integrated data structure

An infrastructure of siloed on-prem servers severely challenges data utilization and maintenance and presents a serious obstacle for big data and self-service analytics. Dispersed data typically becomes too complex to support and the source of truth becomes impossible to identify.   

An ideal solution

By migrating your servers – or parts of your data – into one data foundation you will achieve an integrated, trusted and accessible data infrastructure. The point, of course is to transform your data into business-critical support. Event dormant servers hold information – old as it may be – and by bringing you achieved data to the cloud and connecting it with the rest of your infrastructure, you can include them in your reporting and analytics.

Case Study - Pharmaceutical Company

A major (+25.000 employees) European pharmaceutical company has thousands of external healthcare professionals who continuously perform medical trials worldwide. This process is timely, complicated, and prone to human errors while providing barriers to up-scaling due to lack of capacity.

In November 2018, NNIT initiated a project supporting the company in developing a clinical trial management system (CTMS) that was run in Azure, rather than on-prem at the application vendor. The trial management system provides health care professionals with all the necessary information they need to conduct the trials, and it prompts them to sign when trial instructions have been received, written, and understood. In other words, the system provides process support from initialization to submission.

Bringing the CTMS into Azure-Cloud, the company significantly increased productivity, reduced costs associated with clinical trials, and experienced added possibilities of innovation. Additionally, the company was able to scale up as needed using NNIT managed and pre-qualified GxP servers ready for automated deployment.

In sum, the move to the cloud enabled scalability and ensured stability while maintaining to secure GxP compliance.

The solution is a .NET based application on top of SharePoint Server integrating to NEO4J graph databases and Adlib pdf rendering, and run in 4 separate environments.

Migration Strategy

The strategy combined Re-hosting and Re-architecting using PaaS services where possible such as Key Vault, Web Applications Firewall, Azure DNS, and more.

First step in the project was a stabilization moving the solution to servers and services in Azure. Next step was a stepwise upgrade from SharePoint 2010 to 2013 to 2016 and finally to SharePoint 2019. The final step set to 1H 2021 will be to convert the application to go serverless.

Win Results:

  • Improved stability by 7 operations and NNIT Managed Services
  • Easier capacity management and improved availability by leveraging Azure virtual machines and multiple PaaS services
  • Capacity improvement on +300% by using Azure
  • Enhanced security providing multiple security controls and better continuity, disaster & recovery. ER improved by using inter-regional scenarios.

 

Azure Geography: West Europe (Amsterdam) with backup in EU East (Dublin). 

Life Sciences Industry 16.9

Case Study - Life Science company

The Latin American subsidiary (+1.500 employees) of a global drug company needed to align with HQ's strategy to migrate servers from on-prem to Azure. In 2020, the subsidiary turned to NNIT for assistance, starting with migration of a QlikSense server application.

With most hardware close to running out of warranty, the subsidiary decided to migrate all on-prem workloads to Cloud without heavy HW investments and project cost. The second phase was application modernization. The project included  every step from migration design to post configuration on Azure.

The migration strategy

The strategy was an architecture design and setup using Azure native tools. The migration approach used for migrating servers and databases was a Re-hosting method ensuring service validation, using a structured migration wave approach. 

First step in the process was to assess tenant connectivity network and security requirements. Next step was to define migration strategy and plan the migration waves grouping the workloads. The final step was to execute the migration wave and ensure stable operation. 

Azure Geography: Brazil Southeast

 

Win Results: 

  • Reduce yearly operational cost by 0.5 million by migrating workload from on-prem to Azure
  • Project lead time reduced from a couple of months to 6 weeks
  • The customer got a full overview on application dependency by using AMSA
  • The business interruption was minimized by using Azure native migration tools ASR and DSA