System 06 · Commerce infrastructure
Magento Commerce Consolidation
Four fragmented storefronts consolidated onto one Magento Open Source backend - ~1,570 products migrated in 2022-2023 with no revenue downtime.
Problem
Four storefronts, four times the maintenance
The business operated four separate storefronts on separate domains, each with its own catalog, content and maintenance burden. Every product change, price update and content edit happened multiple times - and the storefronts drifted apart.
This consolidation is the historical infrastructure experience behind the later International Commerce Transformation.
Architecture
One backend, many storefronts
- Input
- Orchestrator
- Output
Migration
Rebuilt in staging, cut over in hours
The first two storefronts migrated in 2022; two further storefronts followed in early 2023. Each new storefront was built and tested in staging while the previous one stayed live. Large portions of products and content were rebuilt rather than blindly transferred - migration treated as an opportunity to fix the catalog, not just move it. Final migrations occurred within hours, with no revenue downtime.
Data integrity was managed carefully but is not claimed to be perfect; the claim that matters is that revenue never stopped.
Ownership
Who owned what
I owned
- Business-side product ownership
- Project lead
- External agency through Jira and UAT
- Delegation across the migration work
- Product rebuilding & product descriptions
- Navigation architecture & landing pages
- Page Builder implementation & implementation assistance
External agency
- Implementation support
- Backend & migration engineering
Related