Brief understanding of ccreating winform + ASP.NET software

See more:

cloud

Hi everyone,

This is not a questions on code but a brief understanding from the developers community.

I have a software that uses .net stack. It is build in legacy code and uses winforms and asp.net. Winform solution builds exe tools (Webbuilder, DBConnectionsTool, IntegrationTool) that are used by site admin/configuration managers to update/modify website. Asp.net project crates asp.net website and wsapi with classic asp pages.

The design and implementation chosen in the past was based on the logic that website will be configurable by configuration admins by the help of tools for their requirements as all business logic returns from building the website dynamically from SP and business logic build in SQL db.
Website will be easily deployable to different client and can be modified as per client needs and UI needs.

Now as time has progressed, we are in need to think of modernizing the software. The current sofrtware is very convenient to deploy, easy to configure and easy for modifying the web pages with the help of tools and do not need to modify any c# and works well with just modifying SQL objects/SPs, which makes this very convenient product to market it.

I am open to get community thoughts and inputs on modernizing approaches i can plan and see if this really will the effectiveness the software brings with it.

What I have tried:

I have looked at Modernizing using Azure Cloud migration solutions.
I have analyzed dependencies in libraries and integrations web services that are needed to develop.
I have anlayzed scope of migrating to microservices but this is very tedious and time consuming and would not result in effecient deployment of the software as it creates dependency on various factors of api management etc.