Enterprise SaaS platform migration — UK market
Led end-to-end transformation of a legacy monolith into a multi-tenant SaaS platform. Coordinated 12 engineers across 3 time zones, on-time and under budget.
The problem
A legacy PHP monolith was limiting scalability, increasing infrastructure costs, and slowing feature delivery to under one release per month. The UK-based SaaS firm needed to modernise without disrupting 500+ active enterprise tenants.
The role and approach
Designed a phased migration strategy, decomposing the monolith into domain-bounded microservices over 12 months. Introduced CI/CD pipelines, containerised deployments on AWS ECS, and ran both systems in parallel during cutover. Coordinated 12 engineers across 3 time zones with two-week sprints and async standups.
The outcome
Achieved 40% infrastructure cost reduction through right-sized containers and auto-scaling. Deployment frequency increased from monthly to multiple times per day. Zero downtime during the full migration, delivered on schedule and under budget.
Hard decisions
- 01Chose shared-schema multi-tenancy with row-level isolation over schema-per-tenant — lower operational cost at their tenant scale while meeting enterprise data-isolation requirements.
- 02Phased cutover with dual-running systems instead of big-bang migration, reducing risk for 500+ live tenants.
- 03Standardised on AWS ECS + CI/CD so deployment frequency could move from monthly to multiple times per day.
Lesson for future clients
For multi-tenant migrations, the tenancy model and cutover strategy matter more than the framework choice. Shared-schema + strong isolation + dual-running reduced both cost and risk.