If you’re anything like me, the move from Optimizely CMS 11 to CMS 12 probably still gives you a few "migration flashbacks." Moving from the old .NET Framework to .NET Core was a monumental architectural shift, a necessary one, but a heavy lift involving rewritten breaking changes and a complete overhaul of how we handle identity.
I have some good news: CMS 13 is not that.
After diving into the latest updates and seeing how the community is reacting specifically insights from Michal Mitas on the AI-first shift and David-tec’s work on AI-assisted upgrades it’s clear that CMS 13 is about refinement, performance, and finally reaping the benefits of being on a modern stack.
The .NET 10 Jump: Why Versioning Matters
The core of CMS 13 is built on .NET 10. For those of us keeping our tech stacks lean, this is a significant milestone.
However, here is a pragmatic tip: You don’t have to wait for CMS 13 to start using .NET 10. You can actually retarget your CMS 12 solution to .NET 10 today to start taking advantage of the runtime improvements.
That said, CMS 13 is where the platform truly "unlocks" the framework, moving to a more composable Application Model and modernized APIs that feel native to the latest .NET ecosystem.
From "Chatbots" to "AI Orchestration"
CMS 13 isn't just "adding AI" as a plugin; it's an AI-first platform. We are moving away from the era of simple chat-based assistants (the "Opal as a Chatbot" phase) and into agent orchestration. In CMS 13, AI is built to handle chained tasks and structured workflows through the Opal Tools SDK. This means instead of just asking an AI to "write a summary," we can build tools that orchestrate complex tasks across the CMS, Graph, and external data sources. It’s about repeatability and intention, not just flashy one-off prompts.
Why 12 to 13 is the "Easy" Upgrade
Free Performance - By targeting .NET 10, you leverage the latest JIT optimizations and memory management "for free."
Native Graph Maturity - CMS 13 makes Optimizely Graph feel like a core architectural component rather than an add-on.
AI-First Development - With cleaner APIs and assembly scanning for package discovery, the platform is much easier for AI-assisted coding tools to parse and help you maintain.
My Pragmatic Upgrade Strategy
Retarget Early - If you're on CMS 12, try retargeting to .NET 10 now. It’s a great "pre-flight" check to see where your dependencies might complain.
Audit for "Removed" Features - CMS 13 finally strips away the legacy baggage (like Dynamic Properties) that were deprecated in 12.
Think in Agents - Start looking at your manual workflows. With the new AI orchestration capabilities, what tasks could you automate using the Opal Tools SDK?
Final Thoughts
CMS 12 was about making the platform modern. CMS 13 is about making it fast and smart. If you’ve been putting off the upgrade because you’re still tired from the CMS 11 migration, it’s time to jump back in. The water is much warmer this time around.