What We Migrate
Legacy PHP, Ruby, or .NET monoliths to Node.js or Python microservices. On-premise infrastructure to AWS (ECS Fargate, RDS Aurora, ElastiCache, CloudFront). Single-server deployments to Kubernetes-orchestrated container infrastructure. Manual deployments to GitHub Actions CI/CD pipelines. Unmonitored production to full APM (Application Performance Monitoring), alerting, and runbooks.
Strangler-Fig Migration Pattern
The strangler-fig pattern incrementally extracts services from the monolith — one at a time — behind a proxy layer. Traffic is gradually shifted from the old service to the new microservice. The monolith shrinks incrementally until it is fully replaced. This approach eliminates the risk of big-bang rewrites and allows continuous deployment throughout the migration.
FinTech & Regulated Systems
Cloud migration for regulated financial systems (FCA-regulated, DFSA-regulated, PDPL-compliant) requires specific controls: data residency documentation, change management records, audit logs, penetration testing, and SOC 2 audit readiness. Brantum has executed cloud migrations for 6 FinTech companies with full regulatory compliance.
DevOps & CI/CD
Every Brantum cloud migration includes a full DevOps setup: GitHub Actions CI/CD pipelines with automated testing, staging environment, and production deployment gates. Infrastructure-as-code (Terraform or AWS CDK). Monitoring and alerting (CloudWatch, Datadog, or Grafana). On-call runbooks. Incident response playbooks.
Pricing
Architecture Audit (before migration): £7,500 fixed, 2 weeks — produces a detailed migration plan and fixed-price quote. Monolith-to-microservices migration: £40,000–£150,000 depending on codebase size and complexity. Typical engagement: 4–9 months. Ongoing cloud management retainer: from £5,000/month after migration complete.
Relevant Case Studies
Frequently Asked Questions
How do you migrate without downtime?
We use the strangler-fig pattern: we extract services incrementally from the monolith and route traffic to the new services progressively. This means the monolith continues running in production throughout the migration — there is no moment where everything is switched over at once. Each extraction is a separate, testable, reversible step.
How long does a cloud migration take?
A focused cloud migration (a medium-sized monolith to AWS microservices) typically takes 4–6 months. A complex enterprise platform migration takes 6–12 months. We start with a 2-week Architecture Audit (£7,500) that produces a detailed migration plan with timeline and fixed-price quote.
Do you handle the SOC 2 audit?
We prepare your infrastructure for SOC 2 compliance — implementing the technical controls required (access logging, encryption at rest and in transit, backup policies, disaster recovery, change management). We work alongside your SOC 2 auditor (or recommend one) to ensure your infrastructure passes Type II audit.
What about data migration?
Data migration is part of every cloud migration project. We design and execute the data migration strategy: schema migration, data transformation, dual-write periods (writing to both old and new systems during transition), and data integrity validation. For FinTech and regulated systems, we maintain a full audit trail of every data migration step.
Can you migrate a live production system?
Yes — and we specialise in it. All Brantum cloud migrations are designed for zero-downtime. We never ask you to take your system offline for a migration window. Every migration step is designed to be reversible, with a rollback plan in place before any change is made to production.
