Case study
IIS migration case study: coming soon
Every completed rescue gets documented in the same structured format — no vague testimonials, just the starting stack, the path chosen, and the measured result. The first write-up will appear here.
The situation
What the business runs on the site, how old the stack is, and what prompted the call — end-of-support server, departed developer, or a hosting notice with a deadline on it.
Before and after
The stack, side by side. Filled in with the real environment once the project ships.
| Layer | Before | After |
|---|---|---|
| Server | e.g. Windows Server 2012, on-premises | e.g. Azure App Service |
| Application | e.g. Classic ASP | e.g. ASP.NET Core / static site |
| Database | e.g. SQL Server Express 2014 | e.g. Azure SQL Database |
| TLS / patching | Manual, overdue | Managed by platform |
The approach
Which of the three paths was chosen and why, what was preserved deliberately, and how the parallel build and staging review ran before the owner signed off.
The result
Cutover downtime, page-speed change, hosting cost change, and what was in the documentation handover. Numbers, not adjectives.
Your site could be the first write-up.
Early projects get extra attention — the work here has to be worth documenting.
Book a free consultation