Catalog Migration to Commercetools
A commerce catalog migration from legacy CMS systems to Commercetools across regions and channels.
Context
Catalog data lived in legacy CMS systems that were inconsistent across regions and channels. The commerce platform migration depended on moving this data into Commercetools with clear contracts and validation.
Problem
We needed a data model on Commercetools that matched real product structure, a migration service that could load it reliably, and enough validation to make the cutover safe across regions and channels.
What I did
- Defined the target data model on Commercetools and the API contracts the storefront and platform would rely on.
- Built a catalog migration service using jOOQ, Netflix DGS, and the Commercetools SDK to transform legacy CMS data and load it into the new platform.
- Built validation and verification checks that gated each region/channel migration step.
- Worked with product and localization teams to handle regional pricing, availability, and content differences.
Result
- Unblocked the broader move to the modern commerce platform.
- Improved catalog consistency across regions and channels.
- Reduced migration risk via validation and staged rollout controls.
Tech
- Java
- Kotlin
- jOOQ
- Netflix DGS
- Commercetools SDK
- PostgreSQL
- GraphQL