How we migrated a production platform from its on-premises data center to AWS - on a deadline we didn't choose, with almost no internal knowledge to lean on, and without users noticing a thing.
Our client's entire platform - around 40 microservices and four databases - ran in a single on-premises data center. Then the operator terminated the contract. The deadline wasn't negotiable: take your infrastructure and leave.
The harder problem was what wasn't there. More than 90% of the engineers who had built and operated these systems had already left the company, taking most of the internal knowledge with them. Documentation was thin, and the business data living in those systems - spread across MySQL, PostgreSQL, Cassandra, and MongoDB - was an asset the company could not afford to lose.
We started where every migration should: understanding what actually existed, and - most importantly - where the data lived.
From there, we moved the platform to AWS service by service, planning each cutover so even a worst-case failure would touch as few users as possible.
Two months in, all 40 microservices were out of the on-premises data center, and the databases and backups were running on AWS - including managed RDS and DocumentDB. There was no downtime beyond DNS propagation, no revenue impact, and no support tickets asking what happened - because from the users' perspective, nothing did. The business data that couldn't be lost, wasn't.
"We lost our data center and most of the team that built it. Lodemark got us onto AWS in two months, and our users never knew it happened."
Tell us about your infrastructure - we'll reply within one business day.