Kentico Xperience 13 to Xperience by Kentico Migration Guide
Summarize the article:
ChatGPT
Perplexity
This guide explains why, when, and how to migrate from Kentico Xperience 13 to Xperience by Kentico, with a focus on technical risk, architecture changes, and real migration effort.
Top takeaways:
Kentico Xperience 13 reaches end of support on December 31, 2026.
Migrating to Xperience by Kentico is not a version upgrade but a controlled replatforming that affects content modeling, custom code, integrations, and editorial workflows.
Most effort goes into content restructuring, API rewrites, and custom functionality, not data transfer itself.
Early planning reduces security, compliance, and long-term maintenance risks.
Using Kentico Xperience 13 (KX13) and planning your digital platform strategy for the next few years? This guide is just for you. Whether you’re aiming for long-term content operations or evaluating technical risk, the migration path ahead is inevitable and more time-sensitive than it may seem.
But why now? Official support for KX13 ends on December 31, 2026. And while the platform won’t suddenly stop working after that date, it’ll no longer receive security patches and technical updates. You can keep using it, but entirely at your own risk. For most organizations, that’s not a sustainable option.
Xperience by Kentico (XbyK) is the modern answer: a cloud-ready, .NET 8-based digital experience platform built around a centralized Content Hub, structured Content Items, flexible Taxonomies, and reliable Content Sync. This guide will show you what migration really involves and how to approach it strategically.
Planning a move from Kentico Xperience 13?
Our CMS migration experts provide a migration audit to clarify complexity, dependencies, and next steps before you commit to a new platform.
Administration gets an overhaul as well:
KX13 admin is a Web Forms-based interface.
XbyK admin is a .NET backend paired with a React-based UI and a completely new extension model.
Cost Efficiency and Long-Term ROI
Staying on a familiar KX13 may seem cheaper. However, the long-term costs can grow quickly:
Maintaining unsupported software.
Patching security issues caused by outdated frameworks.
Building custom “band-aid fixes” or workarounds for outdated integrations.
Xperience by Kentico upgrade reduces these hidden expenses:
Built-in capabilities (Content Hub, Content Sync, better APIs) replace many custom hacks.
DevOps workflows become easier with a modern stack (cloud-ready, containers, CI/CD).
This means fewer “large rebuild” cycles ahead. XbyK is designed for incremental upgrades, not full replatforms every few years.
Before exploring Xperience by Kentico in greater detail, check out our blog on Kentico 12 to 13 migration. If you’re moving through multiple versions, this earlier guide offers helpful background.
What are the main differences between KX13 and XbyK?
XbyK is a full platform rewrite, not an incremental upgrade. It replaces legacy Web Forms admin, Page API querying, and monolithic patterns with a modern backend and React-based admin UI.
To frame your migration planning, you must first recognize what will actually change. Here is Xperience by Kentico vs Kentico 13 compared side-by-side:
1.Technology Stack
The most noticeable difference is how Kentico has evolved. XbyK is a complete rewrite, while KX13 carries technical debt from its long history on the .NET Framework.
Kentico Xperience 13 (KX13) | Xperience by Kentico (XbyK) | |
Architecture | Monolithic DXP | Cloud-native, composable DXP |
Primary Framework | .NET Framework 4.8, ASP.NET MVC 5 | .NET 8 |
Frontend | Mix of legacy JS frameworks, some outdated | Modern React-based frontend |
Database | SQL Server | SQL Server with cloud-native flexibility |
2.Licensing and Deployment Models
Kentico Xperience 13 typically uses perpetual licenses and on-premise deployments. Xperience by Kentico, in turn, moves toward a more modern and predictable model:
Subscription-based licensing, meaning predictable, recurring costs.
Cloud-native fit, available as Kentico’s SaaS option or your own private cloud in Azure, AWS, and other environments.
3.New Digital Experience Features
Xperience by Kentico introduces a completely modernized content model and tooling that solves many of the limitations of KX13:
Content Hub, a centralized, structured repository for all content, far more flexible than a page tree.
Content Items, reusable pieces of content built from field schemas.
Taxonomies and tagging instead of deep folder structures.
Modern admin interface with better UX that editors actually enjoy working in.
4.Migration of KX13 eCommerce
Many organizations using Kentico Xperience 13 rely on the built-in eCommerce feature. Historically, this was one of the reasons teams chose to migrate from KX12 to KX13 first, instead of moving directly to Xperience by Kentico, as earlier versions of XbyK did not provide an equivalent capability.
Today, Xperience by Kentico includes the new Digital Commerce Platform, which enables rebuilding commerce functionality on a modern and extensible architecture. However, there is no direct migration path from KX13 eCommerce to Digital Commerce Platform — the transition requires a planned redevelopment effort with defined scope and roadmap.
This approach allows teams to replace legacy implementation constraints, modernize their commerce stack, and align features with current business needs rather than carrying over historical limitations.
Not sure how these differences affect your Kentico setup?
Architecture differences between KX13 and XbyK affect custom code, integrations, and content models differently in each project. Our Kentico experts at Bits Orchestra can assess your setup through a focused migration audit.
5.Developer and Editor Experience Improvements
Migrating to XbyK significantly improves both developer and editor workflows.
Developers get:
.NET and GraphQL APIs for consistent data access.
Modern ASP.NET Core architecture for reliable performance.
Built-in CI/CD pipelines for smooth DevOps.
NuGet-based extensibility, customizable admin UI, and other solutions for flexibility.
Editors get:
More intuitive content structures via Content Hub + Taxonomies.
Reusable content snippets such as authors, promo blocks, or CTAs.
Cleaner workflows with smart folders, tagging, and automated categorization.
Easier management of multi-site or multi-channel content via GraphQL APIs.
How to Upgrade From Kentico Xperience 13 to Xperience by Kentico?
So, how do you handle a Kentico upgrade? Think of this process as a complete replatforming that touches your architecture, content model, integrations, and dev workflows.
1.Evaluating Your Current Website Setup
Handle a full inventory of everything in your current KX13 instance. Aim to check the following boxes:
Page types, custom widgets, custom modules, custom tables.
Workflows, roles, permissions, scheduled tasks.
All third-party integrations, such as CRM, ERP, eCommerce, search, ID providers.
Every location where DocumentQuery, TreeProvider, Page API, or Media Libraries are used.
2.Reviewing and Redefining Content Modeling in Xperience by Kentico
Since XbyK’s architecture differs from the one in KX13, content modeling is a critical part of migration. Your goal is to modernize the structure.
Think through how existing content should translate:
Map existing page types to new page types in XbyK or reusable Content Items.
Transform files and Media Library assets into XbyK Content Assets.
Define reusable field schemas for elements that appear across multiple content types (SEO, author block).
Folder-based content in the page tree should move into the Content Hub, and deep hierarchical structures should be flattened and categorized using Taxonomies instead of directories.
Important! Media Libraries are sunset. Their APIs are deprecated and will be entirely removed after July 24, 2026. Use Kentico’s Media Library Migration tool to convert libraries into Content Items with GUIDs and metadata preserved. Media URLs (/getmedia/) redirect automatically, but direct file-path links will not.
3.Setting Migration Goals and KPIs
Opting for Kentico migration services means more than having a rebuild. You’re doing it for the benefit of your business. Define success upfront with clear, measurable KPIs, such as:
Reduce duplicate content types by 30–50%.
Decrease content publishing time from hours to minutes.
Improve page load speed or Lighthouse scores.
Consolidate or simplify external integrations.
4.Design and Architecture Planning
At this point, you decide how your new XbyK experience should be structured and delivered. Key activities include:
Mapping legacy ASP.NET templates into Razor components and modern Page Builder widgets.
Reevaluating URL architecture and planning redirects for SEO continuity.
Building a scalable content model around Content Hub and Taxonomies.
Deciding whether to maintain design parity or take the opportunity to refresh UX/UI.
5.Development and Replatforming
With architecture confirmed, development can begin. This is where the old and new systems connect. Core dev tasks are:
Using the Kentico Migration Tool to move initial data, then manually adjusting custom code for new APIs.
Replacing legacy querying with Content Item APIs.
Converting custom tables to custom objects or external DB patterns.
Rebuilding custom Page Builder widgets and forms.
Updating authentication and identity integrations.
6.Testing and QA
Testing should happen continuously throughout the migration process. Your teams should validate:
Content rendering correctness across templates.
User permissions, workflows, roles.
Integrations and external services.
Performance, caching, and load behavior.
7.Content Migration
Once the structure is ready, you can migrate content in stages. Here’s the suggested order:
Structured content (articles, events, products) migrates via the Migration Toolkit.
Media moves to Content Hub or Content Assets using the official Media Migration tools.
Fields are mapped from old to new schemas.
Relationships, Taxonomies, and Content Types are validated post-import.
8.Launch and Validation
After you make sure that everything works stably, go live. Your final checklist is:
Confirming redirects and SEO metadata.
Validating performance and caching.
Moving final content using Content Sync if needed.
Deploying to production and monitoring logs for errors immediately after launch.
9.Post-Migration Support
Launch is certainly the milestone, but not the finish line. Prioritize regular post-go-live improvements, such as:
Continuous training for editors and developers on the new model.
Fixing edge cases or overlooked mappings.
Refining content types, Taxonomies, and workflows.
Tracking KPIs to measure improvement over time.
Get guidance from a certified Kentico partner!
Bits Orchestra’s certified Kentico experts help teams plan upgrades based on their real implementation.
What challenges occur during KX13 → XbyK migration?
Even a well-planned Kentico 13 upgrade can face roadblocks. Here are the most common ones to watch out for:
1. Legacy Content and Data Migration Issues
Older platforms naturally accumulate clutter. Teams often discover:
Inconsistent page types built over many years.
Content duplicated across different sections or languages.
Media referenced via direct file URLs instead of ~/getmedia/ paths.
Old custom objects that have no one-to-one equivalent in XbyK.
The result of the above is extra cleanup work before migration.
2. Complex Custom Workflows and Functionality
Some KX13 implementations rely on platform-specific features that don’t translate directly. Examples include:
Custom approval workflows tied to the old KX13 features.
Marketing automation processes that must be fully re-implemented.
Business logic embedded in code using legacy APIs.
These components require a complete architectural redesign.
3. Third-Party Integration Compatibility
Integrations, such as CRM, ERP, payment, and marketing tools, make digital platforms more efficient and feature-rich. But they’re often one of the biggest migration risks. If these connections depend on legacy APIs or direct DB access, they must be rewritten for the new architecture.
4. SEO, Redirects, and URL Structure Management
SEO is where even great migrations can go wrong. A new content model demands new URL patterns, and without proper redirects, rankings can drop. Common pitfalls are:
URL changes without 301 redirects.
Broken media links from legacy paths.
Missing sitemap or canonical updates.
Treat SEO migrations as a dedicated stream of work, not an afterthought.
5. Limited Resources, Budget, and Timelines
Replatforming is a significant investment, both technical and organizational. It’s not a two-week task, and rushing leads to rework. A phased approach often works best:
Start with critical sites, features, or content types.
Expand gradually as the new platform stabilizes.
Use early phases to validate assumptions and refine architecture.
6. User Training and Team Adoption
Even a perfectly executed migration fails if teams don’t adopt the new platform. XbyK introduces plenty of new concepts, such as Content Hub and Taxonomies, so editors will need time to adjust. Training helps onboard users and accustom them to new workflows and UI.
How Bits Orchestra Can Help
Kentico version upgrade services are our specialty, and we can help you make the transition smooth. In particular, we:
Assess your current KX13 setup.
Design new content models (Content Hub, Taxonomies, reusable fields).
Rebuild custom widgets and integrations.
Set up Content Sync and a deployment pipeline.
Provide training for your team.
In a public-sector project, Bits Orchestra led a multi-version Kentico upgrade, moving a state agency from Kentico 12 Portal Engine to Kentico Xperience 13 Core. The project involved legacy architecture, custom functionality, and strict performance requirements. As a result of the upgrade, the platform achieved faster load times, improved performance, and a more maintainable codebase, while preserving critical business workflows.
If you’re planning your migration, our Kentico development services provide end-to-end support for setup evaluation, content modeling, architecture design, and beyond.
Table of contents
Share
FAQ
What are the risks of not upgrading from Kentico Xperience 13?
Since support for Kentico Xperience 13 ends on December 31, 2026, the platform will no longer receive security patches, hotfixes, and technical updates. This can lead to compliance risks, security vulnerabilities, and compatibility issues with modern integrations and hosting options.
How much time does it typically take to migrate to Xperience by Kentico?
The migration timeline for most small-to-medium Kentico projects is three to six months. And it largely depends on the content complexity as well as the number of custom modules and integrations. Larger, highly customized solutions’ timelines are often six to twelve months, especially when there’s a need to rebuild widgets, content models, and legacy APIs.
If you’d like a realistic estimate for your project, reach out to our Kentico experts for a focused migration assessment.
What is the estimated cost of migrating to Xperience by Kentico?
For a small, lightly customized website, migration typically costs between $10,000 and $25,000. A mid-size solution with custom widgets and integrations usually falls in the $25,000 to $50,000 range. Large or enterprise implementations with complex custom code, eCommerce, and multiple integrations commonly cost $50,000 to $150,000 or more. Kentico licensing is not included in these figures. Talk to Bits Orchestra for an expert migration estimate based on your actual setup.
Is it possible to move to a different CMS instead of upgrading?
Yes. Some teams choose alternatives like Sitecore or Adobe(enterprise DXP), Umbraco (companies looking for more flexibility), or headless CMS platforms such as Contentful, Strapi, or Sanity(good choice for SMBs). These options usually require a full rebuild rather than a direct migration. If you’re weighing upgrade vs replatforming, Bits Orchestra can help you evaluate the best path before you commit.
What happens to eCommerce when migrating from KX13?
There is no direct migration path from KX13 eCommerce to Xperience by Kentico’s Digital Commerce Platform. eCommerce functionality must be rebuilt with a defined scope and roadmap.
Check other articles
Contact us
Before we proceed, please help us understand your needs better. We will review your application and schedule a free estimate call
You can also send us your request
CEO & Co-founder
Our CEO, Roman, will personally review your message and help you get started.
