The client
Abbott is a global healthcare company with a digital estate that supports both brand websites and a business-critical HENS eCommerce platform. Their nutrition brands in Australia and New Zealand include Pediasure, Ensure, Elecare and Glucerna.
Just After Midnight has supported Abbott since 2018, providing cloud hosting, website support, and ongoing eCommerce platform enhancement.
Over time, that relationship expanded from day-to-day support into major transformation work. In 2025, Abbott and Just After Midnight delivered a significant migration project to move the HENS platform onto AWS and away from legacy infrastructure.
The challenge
Abbott’s HENS platform supports nutrition ordering for patients in care settings, with orders often placed by healthcare professionals, carers, or the patients themselves. That made the platform both niche and highly business-critical, with very little tolerance for disruption.
In 2025, Abbott needed to move away from its legacy fulfillment and hosting setup by a fixed deadline. The project also needed to accommodate a mid-stream change in scope, including additional payment gateway work, which meant the original scalability refactor had to be deferred into a later phase.
The solution
Just After Midnight supported a large-scale rehosting and application change programme, coordinating with Abbott’s internal IT and DNS teams, external delivery partners, and the new fulfillment provider. The platform was rehosted on AWS, and the application was refactored to integrate with SAP.
To support a safe cutover, the team used a planned blackout window and migrated data during a tightly controlled weekend change period. Maintenance pages were placed on both sides of the transition, and the switch from the legacy environment to AWS was completed successfully on 1 November 2025.
The results
The migration was delivered to the fixed deadline, and the platform achieved 99.9% uptime on the main portal in the post-migration period, with an average response time of 565ms. A small number of post-go-live performance issues were identified and resolved quickly, including database scaling and query optimisation.
One month after go-live, we committed to reservations for the production instances and database, delivering a 21.2% reduction in infrastructure costs over 12 months. We also introduced AWS Systems Manager (SSM) for secure administrative access, replacing traditional bastion servers and removing the need for teams to wait for a bastion to be switched on before working on the environment.
As of 2026, response times improved further, with homepage and account home performance dropping from roughly 525ms to 228ms, and the platform maintained 99.99% AWS uptime during the February reporting period. In the same period, ticket volume remained active but manageable, with support requests focused on operational items, user journeys, and a small number of infrastructure and email-related issues.
