Why CMOs and CTOs are moving away from Kentico

With the Kentico Xperience 13 end-of-support deadline (December 2026) on the horizon, existing users are exploring their next steps. While plenty of Kentico customers value its DXP capabilities and are planning to upgrade to Xperience by Kentico (the “versionless” solution of the platform), others are actively considering alternative CMSs like WordPress.

At rtCamp, we specialize in CMS migrations (including Kentico-to-WordPress migrations), and we’re seeing several questions around how WordPress compares to Kentico as a CMS and how a modern DXP stack can work with the WordPress CMS at its core (and how it would compare to Xperience by Kentico). 

During these conversations, we’re also learning some of the top reasons the C-suite is reassessing Kentico and looking at options for their future digital roadmap.

Platform evolution challenges

Let’s start here: Kentico itself now calls Kentico Xperience 13 a “legacy” platform which means the upgrade is a necessary one. In fact, in one blog post, Kentico lists 10 strong reasons to upgrade to Xperience by Kentico, and we agree that many of them are compelling.

For example, new features like a centralized Content Hub, advanced headless capabilities, and AI assistance look promising. DXP enhancements (like marketing automation, email builders, and customer journey insights) also add significant value for teams who want more out of their digital experience stack.

This is all great. But the problem is that this is not just another version upgrade. It means rebuilding a lot of the instance, changing how the application is structured, retraining developers, and updating the tech stack. If you go with the hosted solution, this would look even more different. Such an upgrade means adjusting budgets and timelines to match what is, in reality, a full platform shift. Many technology leaders have found themselves caught off guard. 

Even though Kentico provides good documentation, the decisions are not always straightforward. The complexity of migration often requires expert help, turning even minor upgrades into costly projects. And this one is going to be no minor upgrade. 

For many teams, this means asking: If staying with Kentico requires rebuilding anyway, does it make sense to pause and see if the same investment could deliver better outcomes on a more flexible platform? 

In fact, this is often when organizations begin to evaluate Kentico alternatives that offer easier upgrade paths, broader talent availability, and a lower long-term maintenance burden. And that’s why even we’re raising this now. With the 2026 deadline approaching, the decision is no longer hypothetical. CTOs and CMOs are running out of time to decide whether to rebuild on Kentico’s newer stack or switch to something more future-ready. And this is the stage where platforms like WordPress often enter the conversation, offering open-source flexibility and a more adaptable long-term foundation.

Limited developer availability slows things down

Upgrading to a major new Kentico version (like moving to Xperience by Kentico) needs significant development resources. In fact, even beyond big upgrades, working with Kentico means requiring a “Kentico” team. Many capabilities require experienced developers to use effectively. Teams without deep in-house expertise can struggle even with routine updates. Over time, this creates a dependency on a small pool of specialists, which can stretch delivery timelines when resources are limited.

Think about it: Kentico is used by less than 0.1% of websites (according to W3Techs), the number of developers familiar with it is relatively low. WordPress, in contrast, is used by over 40% of all websites, which has led to a much broader developer ecosystem.

This difference becomes clear when teams need to scale development, onboard new vendors, or respond to such change.

Kentico does offer 24×7 support on higher-tier plans. Most of it is handled through email or chat. If you contrast this with WordPress, again, you’ll see that WordPress support works differently. Managed services like WordPress VIP provide one-on-one support, along with tools for security, automated backups, and performance monitoring. There is also a large base of documentation and public resources, which helps teams find answers or resolve issues without relying solely on external support.

This is one reason why some teams are moving toward platforms where it’s easier to access support and find skilled developers when needed. With the 2026 end-of-support deadline approaching fast, teams know they need to act, whether that means upgrading or migrating. But for many, a major upgrade demands just as much specialized development capacity as a migration. And when skilled Kentico resources are already limited, switching to a platform with broader talent availability often turns out to be the more practical path forward.

Upgrading Kentico takes time and effort

Historically, upgrading has always been a friction point with Kentico. Limited backward compatibility between versions has often forced CMOs and CTOs to question whether staying on the platform is worth the time and cost. But this time, it’s not just an upgrade: it’s effectively a complete replatforming to move from Kentico Xperience 13 to Xperience by Kentico.

This makes the upcoming shift a much bigger project than a typical version upgrade; it’s not just a simple lift-and-shift. That’s why many teams are now considering a move to WordPress instead, especially since WordPress is built to handle upgrades far more seamlessly.

Even older WordPress instances continue to work reliably and securely, and because most updates are backward compatible, you don’t need to rebuild your entire site every time something changes. For many teams, that level of flexibility and continuity makes a migration feel less disruptive and more practical than a complex Kentico replatforming.

Ongoing costs are higher than they look

For teams planning this next upgrade, it’s important to note: Kentico’s newer versions come with higher licensing costs. That means when you upgrade, you need to pay more for your Kentico license, even before any development work begins.

And the upgrade itself isn’t simple. That means more developer hours, more QA effort, greater migration risk, and ultimately, more budget pressure.

Even with an in-house team, those hours come at a cost. And when external vendors are involved, expenses rise quickly, especially when faster fixes or priority support come with additional charges.

When you add up licensing fees, rebuild cycles, and ongoing support, the total cost of ownership often ends up much higher than expected. Over time, Kentico could become harder to justify, especially when more flexible platforms like WordPress offer smoother upgrades, lower long-term costs, and more operational flexibility.

Planning your Xperience by Kentico upgrade: key questions

Before you commit to the next Kentico upgrade, it’s worth stepping back. 

For CTOs, Kentico’s niche developer pool can make it harder and more expensive to find the right skills when you need them. On top of that, major Kentico upgrades often feel like starting over, with significant redevelopment, custom integrations, and heavy testing every few years. While the latest version promises to be a truly future-proof solution, many teams still see the upgrade path as a big lift. For technology teams already balancing tight budgets and evolving tech stacks, that level of effort can feel misaligned with the need to innovate faster, modernize the tech stack, and scale without rebuilding the foundations each time.

For CMOs, long upgrade cycles that feel like ground-up rebuilds can stall campaigns, limit agility, and hold back the marketing momentum your team works so hard to build. 

Together, these realities raise an honest question: does this platform still match where you want to take your business next?

Key concerns:

• Will we get a clear ROI from replatforming to Xperience by Kentico? Or is that budget better spent modernizing on a more flexible stack?
• How much vendor lock-in will we have if we upgrade, and how easily can we adapt if business needs change?
• Do we have resources to run our Kentico instance? 
• Will upgrading unlock genuinely new capabilities or mostly recreate what we have with a new learning curve?
• How future-proof is this choice? Does it support headless, multichannel, and integrations with the best-of-breed tools we already rely on? (Yes, while Kentico does offer headless and multichannel capabilities, many integrations still need custom development or vendor support, adding to costs and complexity down the line.)
• Do we want a DXP that connects best-of-breed tools or one that relies mostly on native, all-in-one features (Xperience by Kentico!)?
• And… If we wait, are we risking higher costs, bigger technical debt, or limited support closer to the 2026 deadline?

These technical considerations shape how fast your business can move and how much flexibility your teams have.

Many businesses are realizing that the upcoming Kentico upgrade isn’t just a version bump, it’s a major replatforming effort that demands significant time, budget, and skilled developer capacity. For some, that investment makes sense. For others, it’s the perfect moment to step back and choose a platform that’s more flexible, easier to resource, and designed to grow with them.

Rethinking Kentico?

Kentico has powered digital experiences for hundreds of companies and definitely has its place.

That said, when upgrades start to feel like full rebuilds, skilled developers are hard to find, and small changes take too long, it’s only natural to ask whether it’s still the right fit for your long-term goals. For some teams, the answer just isn’t a clear yes anymore.

That’s why they’re considering moving to platforms like WordPress. It’s open, easy to manage, and gives teams more control without the usual complexity. If you’re thinking about what’s next for your website, this might be a good time to explore better options. 

Still unsure whether Kentico or WordPress is the better fit? You can explore our detailed Kentico vs. WordPress handbook for more clarity.Let’s connect and map out your Kentico to WordPress migration together. We’ll help you evaluate whether migrating to a CMS like WordPress is the right move for your business. If it is, we’ll plan every step with you and build a modern WordPress stack that supports your workflows, integrations, and long-term growth.