Insights
For organisations running Kentico Xperience 13, the arrival of Xperience by Kentico signals more than just a new version. it’s a shift to a new architecture, a new development model, and a new way of managing content. While the naming might suggest a linear upgrade, the process is more involved. This is best understood as a migration, supported in part by tooling, but requiring redevelopment across key areas of your platform.
This guide outlines what the migration entails, what the Kentico Migration Tool does (and doesn’t) cover, and how to plan and execute the transition effectively, especially if your platform is business-critical or tightly integrated.
It's not just an upgrade
Migrating to Xperience by Kentico is not like moving from version 12 to 13. The underlying platform has been re-architected for the modern web: API-first, modular, and built on .NET Core. As a result, many aspects of your site need to be recreated to fit the new development model.
That said, Kentico has provided a Migration Tool that streamlines some aspects of the transition, particularly data and binary assets. The process broadly includes:
- Setting up your environment and configuring the migration tool
- Migrating content data and binary files
- Adjusting your code and recreating any custom modules or integrations
- Exploring and adopting the full potential of the new platform architecture
So while you’re not starting from scratch, you’re also not simply pressing a button. The reality sits somewhere in between: data can move, but functionality must be audited and modified where needed.
What the Migration Tool covers - and what it doesn’t
The migration tool is designed to give teams a head start by carrying across:
- Structured content (page types, fields, metadata)
- Binary files (media libraries, attachments)
- Basic object data (users, roles, tags, etc.)
However, several elements cannot be migrated automatically, including:
- Templates and page builder widgets (these must be rebuilt using the new development model)
- Custom modules and integrations
- Front-end rendering and layouts
- Automation processes and custom workflows
- Permissions and staging configurations
The migration tool helps with content and object scaffolding, but the experience layer and business logic must be adapted manually.
Planning your migration strategically
Given the scope of redevelopment required, a successful migration starts with structured planning. At Kalago, we treat migrations like this as part replatforming, part transformation — not just technical transition, but strategic modernisation.
Here’s how to break it down:
1) Audit your current platform
- Identify all features, templates, and custom code in Kentico 13
- Prioritise mission-critical functionality vs. redundant or legacy components
- Document integrations and API dependencies
2) Define what to migrate vs. redesign
- Decide which content types and assets will be migrated using the tool
- Identify elements that are best restructured or simplified
- Consider UX improvements as part of the rebuild
3) Redesign around modern architecture
- Embrace separation of concerns: Xperience by Kentico decouples content from delivery
- Plan for clean, scalable front-end applications built on modern frameworks
- Evaluate options for hybrid or headless deployment
4) Plan for parallel running or phased rollout
- Some businesses may benefit from running Kentico 13 and Xperience by Kentico in parallel for a short period
- This allows for staged cutover, stakeholder testing, and rollback strategies
Modern architecture, new capabilities
Xperience by Kentico is built from the ground up with flexibility and performance in mind. It introduces:
- .NET Core-first development with full support for dependency injection and modular design
- Clean separation between content and presentation, enabling headless and hybrid architectures
- Improved CI/CD capabilities and environment portability
- Modern admin UI with more extensibility
- SaaS-ready delivery models with optional hosting
These shifts mean that once migrated, your platform will be better suited for integration, scaling, and continuous improvement.
Common pitfalls to avoid
While the documentation and tooling provide clear guidance, there are common challenges that can derail migrations:
- Underestimating manual redevelopment effort — especially for templates, widgets, and integrations
- Trying to match existing functionality 1:1, rather than embracing improved design and UX
- Delaying architectural decisions until too late in the process
- Neglecting performance, accessibility or security improvements during the rebuild window
This is not a job for a patch-and-port approach. It requires engagement across development, UX, operations, and business stakeholders to get right.
Benefits of migrating when done properly
Handled well, this migration provides significant long-term value:
- Lower technical debt with a modern, maintainable codebase
- Improved developer experience and deployment pipelines
- Greater design flexibility and faster time-to-market
- Enhanced performance, SEO, and accessibility
- Better integration with modern tools and marketing stacks
Ultimately, it prepares your organisation for future evolution, rather than tying you to a legacy monolith.
A Platform migration is a business opportunity
- It’s easy to view migrations like this as costly overhead. But done right, they’re a catalyst to rethink how your digital platform supports your business:
- Can your content model be streamlined?
- Can workflows be improved?
- Are there UX pain points that can finally be resolved?
- Are you ready to move to cloud-native or SaaS delivery?
Approach the migration not just as a technical step, but as a strategic opportunity to modernise how your organisation works online.
Conclusion: moving forward with confidence
Xperience by Kentico represents a clear step forward in architecture, capability, and long-term value. While the migration requires effort, it also unlocks significant benefits. These range from performance and security to UX and integration flexibility.
The key is planning, stakeholder alignment, and technical depth. For organisations that rely on Kentico as a central platform, the time to start preparing is now.
If you’re ready to begin exploring your migration path, the best first step is an audit: know what you’ve got, what you need, and where the gaps are. From there, you can shape a roadmap that avoids surprises and creates long-term value.