Lessons from Replacing Oracle ATG/BCC with a Headless CMS

Context: Why Change Was Needed

At the premium beauty retailer I was contracted with, the legacy stack relied heavily on Oracle ATG Web Commerce (ATG) and Oracle Endeca/Business Control Center (BCC) to power its e-commerce site. ATG provided a robust (if monolithic) commerce engine, while BCC offered content targeting and merchandising tools. These platforms were powerful but notoriously heavy—customization took time, deployments were brittle, and content authors often struggled with rigid workflows.

By 2022, it was clear that the pace of digital retail demanded something faster and more flexible. That’s why we led the move to Contentful, a headless CMS designed around APIs, modular content, and omnichannel publishing. Contentful promised not just new tools for editors but an entirely new way to scale personalization and digital experience delivery.

One of the most complex examples came from the homepage. With atomic content, each banner, promo, and slot could have multiple children (images, CTAs, text variants). By the time producers finished assembling the holiday homepage, the CMS showed 496 entries tied to that single page—illustrating both the power and complexity of atomic modeling at enterprise scale.

Launch Success

The migration went live just before the holiday season—a bold but necessary move that landed smoothly thanks to strong cross-functional teamwork. The site handled peak traffic, editors onboarded quickly, and producers embraced Contentful’s faster workflows. Automation made an immediate impact: DAM integration reduced repetitive asset work, a custom migration utility collapsed hundreds of hours into two, and a Bulk Editor app further accelerated production.

Challenges

Timelines and communication needed to be clearer from the start, and business users should have been included earlier in content modeling. DAM and RWS (Translation) integrations felt rushed, change management came late, and preview validation remained unstable. Launching personalization at the same time stretched resources, while post-launch SaaS support lacked defined ownership (read: product manager does it all!).

Recommendations for the Future

Future programs must budget for stronger change management and involve PMs and production teams earlier. PODs need clearer alignment and dependency tracking. Preview should stabilize quickly, then evolve into user-friendly tooling. Workstreams should run in parallel to avoid bottlenecks, SaaS ownership should be clarified, and personalization should follow its own dedicated roadmap.

Takeaways

Replacing Oracle ATG/BCC with a headless CMS like Contentful wasn’t just a tech swap—it was a culture shift. Editors went from waiting on engineering to directly managing omnichannel content. Developers moved from maintaining monoliths to enabling composable services. Business teams learned that content modeling is not a side project—it’s the backbone of personalization and scalability. The homepage’s 496 entries proved the scalability of atomic models but also underscored the need for governance and discipline.

The biggest lesson? Go-lives are about more than technology. Success depends on governance, training, and the human side of change management.