Engagement
The business problem and technical context
Situation
A SaaS company expected significant business growth, but its applications were hosted in a local data center. The estate included Windows Services, a website and blog, and a very large shared database that constrained scaling.
Business constraint
The company needed cloud capacity without taking every legacy system offline at once, and the new operating model still had to make financial sense.
Why this approach fit
A phased migration reduced cutover risk. A VPN between the data center and Azure allowed cloud applications to feed the existing warehouse while dependent legacy systems remained online.
Data and systems involved
Windows Services, a website and blog, a large on-premises data warehouse, Microsoft Azure WebJobs, Azure App Service, Azure SQL, application-specific databases, and a VPN connection.
Transcendent's role
Transcendent Software assessed the application estate, designed the hybrid transition, converted workloads, separated databases, and migrated the system one application at a time.
Delivery
Approach
- 01
Establish secure connectivity between the data center and Azure
- 02
Convert Windows Services to Azure WebJobs and move the website to App Service
- 03
Create dedicated Azure SQL databases while continuing to supply the legacy warehouse
- 04
Move dependent systems incrementally, then use reserved Azure instances to control cost
Outcome
The system moved to Azure through staged transitions, and reserved cloud capacity helped reduce ongoing hosting costs.
What this engagement demonstrates
Cloud modernization can improve scalability and lower hosting cost while preserving operational continuity through an intentionally hybrid migration period.