The situation
Nikon's sites serve customers in many countries and languages, supporting e-commerce, product content and customer engagement. The platform behind them had been customised by multiple providers over the years, and the technology varied from one subsidiary to the next.
More than 40 localised sites ran on outdated CMS components, hosting contracts were expiring, and releases were manual because there were no CI/CD pipelines. Weak access role management had also contributed to data leaks, which made security the first priority of any change.
What we did
We designed a single architecture to current development standards, brought the subsidiaries' stacks onto it, and migrated the platform to AWS for availability and scale. CMS components and integrations were updated to supported versions to clear technical debt, and CI/CD pipelines now automate deployment.
We tightened access role governance to close the route to the earlier data leaks and aligned the platform with CCPA. Delivery ran in agile increments with regular reviews alongside Nikon's team, so progress was visible throughout.
The numbers
- More than 40 localised sites on one architecture.
- 1 platform on AWS in place of stacks that varied by subsidiary.
- Automated deployment through CI/CD, where releases had been manual.
What changed for the client
Every localised site now runs on the same supported architecture, which lowers the cost and complexity of running them and lets Nikon release changes through an automated pipeline. Access is governed by role, and the platform can grow as Nikon adds markets and services.
We would be glad to talk through how your sites could share one architecture.
Our senior consultants can take you through how consolidation would run market by market, and how your team would keep control of each cutover.