Heroku in Maintenance Mode: It’s Not a Migration. It’s a Rewrite.
Beyond the Marketing Pitch: Why Heroku’s Maintenance Mode is a High-Stakes Architectural Re-Write, Not a Simple Move.
Heroku announced on Feb 6, 2026 that they are transitioning into “sustaining engineering”, a million things were running in my mind, thinking about the engineering teams that have to go through this transition. Wade Wegner (Chief Ecosystem and Growth Officer, DigitalOcean) had some great thoughts but one line stayed with me:
“Migrate is easy to say. Harder to do.”
True. But in most real engineering organizations, it’s not even a migration. It’s a rewrite. And rewrites are where strategy meets friction.
Heroku isn’t going dark tomorrow. That’s not the issue. The real signal is the absence of a forward roadmap. When a platform stops investing, the risk isn’t sudden failure; it’s slow stagnation while the rest of the ecosystem evolves. That’s when teams begin the painful process of reassessing.
The Myth of Portability
On the surface, migration feels simple. Move the app. Move the database. Cut over DNS. But production systems are never just apps. They are layered assumptions: build pipelines, background workers, release phases, network boundaries, secrets management and on-call playbooks.
Code portability is often high. Operational portability rarely is. What looks portable at the code layer becomes deeply entangled at the operational layer. Moving from Heroku isn’t just swapping a “dyno” for a “droplet”; it’s re-establishing a working architecture in a world where your networking topology and data layer must be rebuilt from scratch.
The Triple-Front War
Migrations don’t happen in a vacuum. Engineering teams are not sitting idle waiting for a platform decision. They are currently fighting a three-front war:
Maintaining the Legacy: Keeping the current Heroku setup stable so the business doesn’t crash.
The Re-Write: Rebuilding pipelines, monitoring and databases on a new platform like DigitalOcean.
The AI Mandate: Accelerating AI POCs, standing up inference endpoints and experimenting with agents, the work many orgs are pushing for right now.
Asking already stretched senior engineers to context-switch between modernization and maintenance while shipping AI features isn’t a “lift-and-shift” exercise. It’s controlled reconstruction mid-flight.
Why the Destination Matters
If we are forced into this “controlled reconstruction,” the destination has to offer more than just a place to park old code. It needs an active roadmap.
DigitalOcean’s App Platform is built on the same Cloud Native Buildpack model that made Heroku successful, which helps reduce the “surface area” of the change. But more importantly, they are shipping the things Heroku stopped prioritizing: native Bun support, VPC integration and AI-assisted migration tooling.
The Reality Check
Responsible migration requires something many organizations underestimate: deliberate capacity. Not optimism. Not marketing. Capacity.
It requires an inventory of the architecture and a protection of the engineers doing the work. Sometimes, a migration is a forcing function to modernize everything deferred for years - turning a “migration budget” conversation into a full platform transformation program.
The real question isn’t whether teams can migrate. It’s whether they can transform without destabilizing everything else they’re already responsible for. In 2026, engineering leaders are balancing platform shifts, AI mandates and security hardening all at once. Adding a platform rewrite to that mix demands adult tradeoff conversations.
Migration is easy to say. Rewriting reality is not.
The organizations that navigate this well won’t be the fastest to react. They’ll be the ones that understand the full blast radius before they move.
Social Media Blurb (LinkedIn/X)
“Migrate” is easy to say. Harder to do. Actually, for most teams, it’s not a migration - it’s a complete rewrite. As Heroku enters “maintenance mode,” the real risk is slow stagnation while your team fights a triple-front war: maintaining the old, building the new, and shipping the AI POCs the business is screaming for. Don’t ask for “Migration Heroes” plan for platform reality.
Read my take:
This breakdown of the Heroku sunsetting news provides additional context on what “sustaining engineering” actually means for enterprise customers in 2026.
If this resonated, I’ll be writing more about engineering leadership, AI-assisted development, and building sustainable systems. Subscribe if you want future posts in your inbox.
— Suren