How do you keep a 20-year-old legacy platform running while rebuilding it from scratch?
Members of the Elemental Concept team began working with this client in the early 2000s, initially offering ad hoc consultancy around open-source technologies. Over time, we helped replace their e-commerce system with a modular platform built in Java, running on a JBoss Application Server with an Oracle relational database, all integrated with multiple legacy ERP systems, whilst they undertook a cloud transformation journey to modernise their technology stack.
The challenge:
Fast forward to today, and the client is in the midst of a major re-platforming effort, shifting to a modern, cloud-native e-commerce stack. While the new platform already handles a high volume of customer interactions, the original Java-based platform hasn’t been retired. In fact, it still underpins key parts of the ecommerce experience, particularly for larger customers who depend on its complex, tailored functionality. That functionality hasn’t yet been replicated in the cloud.
We needed to support and extend a 20-year-old Java monolith with significant technical debt, while the in-house team focused on building out the new cloud-native stack.
Our approach:
Elemental Concept was re-engaged to augment the client’s internal development capability. We took ownership of the legacy Java platform, continuing to implement critical features while also contributing to its gradual, carefully managed decommissioning. We’ve helped to stabilise, support, and evolve the monolith where needed, while enabling the client’s team to move forward with the cloud platform without interruption.
The result:
- Reduced pressure on internal development team – they’re now free to focus on the future platform.
- Legacy value preserved – key functionality used by major customers continues to operate reliably.
- Strategic handover underway – the old platform is being wound down in an orderly fashion, with new capabilities transitioned cleanly to the cloud.
Working with a legacy platform that can’t simply be switched off?
Most cloud migrations don’t fail because the new platform isn’t ready. They stall because nobody has a plan for what happens to the system it’s replacing. If that tension sounds familiar, our legacy systems services and platform management work are worth a look.
