Cloud migration with zero downtime, and the DevOps to run it.
We move production systems to AWS, Azure or Google Cloud one service at a time, with old and new running side by side until the numbers match. A published payments migration moved $14M a month with zero downtime and cut infrastructure cost 35%.
What good cloud migration services look like.
A migration should be boring for your customers. Gigabit migrates with the strangler fig pattern: build the target platform in code first, move one service at a time, run old and new in parallel with shadow traffic, and move the riskiest component last behind a tested rollback.
In the published engagement a Series B payments platform left Heroku for AWS while processing $14M a month. The work cost $74,000 over 14 weeks, after a $6,000 assessment. There was no downtime. Deploys went from 38 minutes to 2.5, releases from twice a week to 18 times, payment p99 latency from 340ms to 145ms, and infrastructure cost from $14,200 to $9,230 a month.
What a migration includes.
The DevOps foundation goes in before the first service moves, so every cutover can be watched and reversed.
Assessment and plan
A review of code, schema and traffic that ranks what moves first by risk, with a cost model for the target cloud.
Infrastructure as code
Every resource in Terraform, with environments you can rebuild from scratch and review in a pull request.
CI/CD and deploys
Pipelines with tests, security scanning and blue-green or rolling deploys, so releasing becomes routine.
Observability
Metrics, logs, traces and alerts in place before the first cutover, so a discrepancy shows up in seconds.
Database moves
Replication, read replicas and verified cutovers for large tables, with reconciliation reports you can sign off.
Cost control
Right-sized instances, reserved capacity and tagging, so the bill after the move is lower than before it.
Four phases, no big bang.
Assess
Two weeks to map the system, rank the risks and price the migration.
Build the foundation
Infrastructure as code, CI/CD and observability, before any traffic moves.
Move service by service
Low-risk services first, each run in parallel until old and new agree, the core last.
Hand over
Runbooks, knowledge transfer and a failure-injection game day with your team.
Published prices, mapped to the job.
Every price here is the same one on the pricing page. Work with no published price gets a fixed price in writing before it starts.
Figures in the notes are what past clients paid, from the published case studies; they show the range, not a rate card. Work with no natural end, such as ongoing development, is priced per engineer per month with no lock-in.
When to hire us for this, and when not to.
- Hosting cost or limits are eating margin or reliability.
- Deploys are slow or risky, and nobody ships on Fridays.
- A customer, auditor or investor wants infrastructure you can document.
- The move has to happen without downtime.
- The app is small and stable where it runs. Moving it adds cost with no return.
- You want a lift-and-shift with no tests. We decline those, because the first incident lands on you.
- The system is being replaced within a year. Migrate the replacement instead.
Heroku to AWS at $14M a month, with zero downtime.
The full engagement: assessment, foundation, service-by-service migration and the payment core last.
A 14-week strangler-fig migration off Heroku with zero downtime: -35% infra cost, -93% deploy time, +800% deploy frequency.
These are past engagements at the prices those clients paid. For build price, monthly cost and payback side by side, see what ten client projects cost.
Cloud migration, answered
How much do cloud migration services cost?
Our published migration cost $74,000 over 14 weeks, after a $6,000 assessment: an 85,000-line Rails application with a 47-table database moved from Heroku to AWS. Smaller systems cost less. The assessment ends with a fixed price for the migration itself.
Can you migrate without downtime?
Yes. Services move one at a time and run in parallel with the old ones. In the published migration the payment core ran 48 hours of shadow traffic across 12,000 transactions at a 0.00% discrepancy rate, then traffic shifted from 1% to 100% over 10 days with a tested rollback at every step.
Which clouds do you migrate to?
AWS, Microsoft Azure and Google Cloud, from Heroku, other platform hosts, virtual servers or on-premise systems. The assessment recommends a target based on your stack, your team and the cost model.
Do you offer DevOps consulting after the migration?
Yes. DevOps engineers can join your team as an embedded pod at $3,000–$7,500 per engineer per month, or we hand over with runbooks and a game day so your own team runs it.
Will the migration lower our cloud bill?
It should, and you see the cost model before you commit. The published migration cut infrastructure cost 35%, from $14,200 to $9,230 a month.
Often scoped alongside.
Legacy modernization
Old systems replaced piece by piece, without a big-bang rewrite.
Legacy modernizationData engineering
Pipelines, a warehouse and dashboards people trust.
Data engineeringFintech software development
Payments, migrations and audit trails for fintech teams.
Fintech software development
Planning a move to the cloud?
Tell us where the system runs today and what hurts. We reply with how the migration would run and what the assessment covers.