Case study
Legacy knowledge base migration to Azure case study
The client is a transportation and logistics company with roughly 200 employees. Name and location withheld — the stack, the approach, and the numbers are real.
The situation
The client's internal knowledge base — the wiki documenting operating procedures, dispatch workflows, and equipment records — ran on IIS 8 on a single on-premises server, backed by a SQL Server 2008 R2 database already past the end of its support window.
The setup had no real disaster recovery: everything lived on one machine in one location. Maintenance cost and risk were both climbing quietly in the background — updates for the underlying wiki software had become rare, and the platform had accumulated the kind of security gaps that don't announce themselves until something goes wrong.
Before and after
The stack, side by side.
| Layer | Before | After |
|---|---|---|
| Server | IIS 8, single on-premises server | Azure Container Instances (managed, containerized) |
| Application | Legacy wiki platform, largely unmaintained | Current, actively maintained wiki platform |
| Database | SQL Server 2008 R2, past end of support | Managed Azure database service |
| Identity | Local, on-premises accounts | Microsoft Entra ID |
The approach
Rather than rehosting the existing wiki platform as-is, or rebuilding custom software around it, the decision was to replace the platform itself. Continuing to build on the old wiki software — regardless of where it was hosted — would have meant inheriting its existing security gaps along with it. Replacing it closed those gaps at the source instead of carrying them forward onto newer infrastructure.
The replacement platform was deployed via Azure Container Instances, with the database migrated to a managed Azure database service and user identity moved to Microsoft Entra ID. Content was migrated from the old platform to the new one, and the cutover happened with zero downtime — the old system stayed available until the new one was verified and the team had fully moved over.
The result
The organization now runs on a platform actively maintained by its vendor, rather than one that had quietly stopped receiving updates. On-premises server maintenance is gone entirely, and because the new environment runs in Azure instead of on a single physical box, disaster recovery is far simpler than hoping one server survives.
Security posture improved by removing the software that carried the risk, not just by moving it to newer hardware. The result is a more reliable, more secure knowledge base on a foundation that can scale as the organization grows.
Your site could be the next write-up.
Every project gets the same fixed-price, tested-before-go-live treatment — whether or not it ends up documented here.
Book a free consultation