How we migrate the platform from Webforms to Azure
Is it possible to move a platform written on Webforms in 2009 to the cloud with only slight changes?
Our case study outlines our recent encounter with a similar job at hand. We’ll share deeper insights from our trusted experts to help guide you through the process.
Our client is a scalable database registry storing sensitive healthcare data. They help healthcare organizations and clinics preserve data privacy, and establish access control, authentication, and encryption.
Their web application is a biometric system that authorizes and tracks users, a database to store the records, and a custom solution for clinics to assign new user roles and check if specific permissions are available for the user role.
A business can't operate at its full potential when its operations are slowed by outdated technology that is not optimized for today's computing environment. The more efficient a company is, the more competitive it will be. But as you probably already know, the path to this isn’t easy, especially if we talk about moving the legacy system to the cloud.
System environment parameters
The whole system environment parameters were designed to work on particular hardware, so moving it to the cloud as it was could break down the entire system and threaten the security.
Database compatibility
The MS SQL database used in the solution wasn’t compatible with Azure SQL and had to be upgraded and fixed.
Unsupported parts
Azure Firewall was incompatible with the current solution, as it viewed several harmless requests as potential threats that could stop the whole system work.
Let’s start from the very beginning, when our team familiarized with the project for the first time. Although the task seemed easy, we knew that migrating Webforms to Azure would require additional work. So, we decided to map out what should be done first.
Delving into the project
First of all, the system was built for a particular hardware, and our experts couldn't confirm that it would work properly, fast and efficiently on virtual machines. Secondly, the system uses third-party tools including biometrics recording, so we couldn’t predict if they would work in the same way in the cloud. Thirdly, Azure works with specific tools and products that might have been incompatible with the system..
Validating the idea
Before we deployed ASP.NET Webforms application on Azure, our team decided to build a development environment in the cloud and validate it with test datasets. It was the only way to identify all possible issues without violating the production.
A development environment is a set of tools and services that can be used to build, test and deploy an application
In our case, the original system consisted of the MS SQL database, a web server that hosted the web portal through the IIS connection, and the biometric service server. All these applications were designed to be hosted on-premise, so we had to carefully prepare cloud environment before migration and rewrite some app parts.
We started with acquiring and configuring Azure Virtual Machines (VM) with Visual Studio.
Then we copied the system's APIs to VMs, but the biometric matching service didn’t work.
We refactored it and switched the biometric API to use load balancing.
In the end, we made a few more modifications to adjust it to the Azure environment.
After we tested Azure Dev with Azure App Service, we were able to find and resolve more issues we. But for now, check out how the system looked in Azure for that moment.
AZURE
MS SQL
Portal (Web Hosting) App Service
Azure Load Balancer
VM 1 API
VM 2 API
Cloud migration costs can be sky-high because of various factors. How to calculate them all? Explore these proven approaches to estimate every dollar of your migration.
Learn more
Want to know more about all benefits, risks, and different approaches to cloud migration? We prepared a comprehensive checklist.
Learn moreBlog Posts
While building the dev environment we figured out the existing MS SQL database is not compatible with Azure MS SQL due to exotic stored procs. Azure cloud only uses a UTC time zone format, while the client's system used EST. This caused a total mess in making records. Our engineers managed to ASP.NET app to insert to Azure SQL database. They rewrote 140 stored procs in DB and restructured source code of the website to use the EST time format. As a result the system began creating records correctly.
IMPORTANT:
Identify all the limitations of the cloud environment and compare them with your current system. Also, don't forget to compare your system capacity with the tiers you acquire in Azure to avoid slowing down the system after the migration.When we moved on to ASP.NET Webforms to Microsoft Azure migration and activated Azure Firewall we found out that it blocked specific types of harmless requests, while their proceeding is a part of the system work. We replaced it with Cloudflare Firewall - it wasn't the best match, but it allowed the needed requests and protected the system from hacking attempts.
Finally, the test environment started working properly, so we moved production to the cloud – the easiest part of the process.
Unfortunately, this was not the end of the story.
In most cases, moving Webforms to Azure is just
the beginning of many technical and organizational improvements.
The hidden pitfalls
Due to specific business needs, company’s employees track end-to-end data evolving recordings for the last 10 years.
When they launched the report building on Azure after migration, trying to get the data for the period of 10 years, it hadn’t proceeded because of Azure time limitation (504 error).
By the default, Azure waits 120 seconds till the webpage’s response, but what about a 10-year report?
Our team rewrote reports to launch report building as a background process that could be accessed
through the link. However, after the migration of ASP.NET Webform to Azure, the execution time of
report building feature was unsatisfactory. We found out that due to poor coding practices used in the system's creation, the
system performed spare computing, so virtual machines couldn’t proceed as fast as the hardware server
did. Our engineers refactored the report building part and made it 200 times faster. By
now, it's easy to see why code quality matters.REMEMBER
Common cloud services may not always work for heavy computation, as virtual machines capacity is limited. Choose on-premises platforms if you work with large workloads.
200 times faster
99,99% guaranteed 
297 code issues We cannot underestimate the importance of honesty in this case study. So, you may think it’s not worth of migration efforts. Actually, it’s worth it.
Continuity is an essential requirement for the client’s system - a major reason for them to step into Webforms to Azure migration.
As for now, the system is not dependent on particular employees or unpredictable occasions like power outages
We also updated all parts of the system and third-party tools.
Results
Calculate all your moves beforehand. You should know your budgets for the migration project as well as for system maintenance in the cloud, tier level to keep performance on the same level. Identify if all the elements of your current app are compatible with the cloud.
Cloud environment limitations may hit you unexpectedly. Keep in mind things like request size, web page load speed, and (oh God) time zones. By the way, in Azure HTTP requests should be less than 128 kilobytes, page response speed < 120 seconds, and the time format GTM.
We performed many external and internal projects and can say for sure, that every project (product) should have an owner who will be the main point of decision making and responsibility. You can hire a professional or involve a current employee for this role.
This project wasn’t easy. We faced many issues for the first time, but I’m proud that we managed to resolve them all and deliver a high-quality cloud solution. I’m also grateful to our client for this valuable experience and patience in the most critical moments.
Actions speak louder than words! Take a look at our legacy app modernization
services in essence.
Porting a Large Enterprise System to .NET Core 3.2 to Expand Its Capabilities
Read More
How we moved a complex cloud-based eligibility verification platform
Read More
How we moved a complex cloud-based eligibility verification platform
Read MoreLearn how to integrate a desktop system into the modern web-based platform fully.
Read More
Seamless Integration of Cloud-Based Eligibility Verification Platform with EMR
Contact our legacy software modernization company to start your successful cloud migration story.
You have successfully subscribed to our newsletter. News is coming soon!
Please, provide the email address so that we can send the whitepaper to you.
Please, provide the email address so that we can send the checklist to you.
