Kentico 13 EOS: Support ends Dec 31, 2026 - 218d 17h 56m left.

Kentico 13 End-of-Support Checklist: 25 Essential Tasks Before Upgrading to Xperience by Kentico

PA
Pawan
Jul 13, 2026
Kentico 13 End-of-Support Checklist: 25 Essential Tasks Before Upgrading to Xperience by Kentico

Every enterprise running Kentico Xperience 13 is approaching an important milestone. As the platform reaches its End-of-Support (EOS), organizations need to move beyond simply acknowledging the deadline and begin preparing for a successful migration.

Waiting until the last minute often leads to rushed planning, unexpected costs, compatibility issues, security concerns, and unnecessary downtime. On the other hand, organizations that prepare well in advance experience smoother migrations, improved website performance, stronger security, and access to the latest digital experience capabilities.

Whether you're planning to migrate to Xperience by Kentico or evaluating your future digital experience strategy, preparation is everything.

This comprehensive checklist covers 25 critical activities every enterprise should complete before upgrading.

Why the Kentico 13 End-of-Support Matters

Kentico Xperience 13 has served thousands of businesses with powerful content management, digital marketing, personalization, and eCommerce capabilities.

However, after the End-of-Support date:

  • No new product updates
  • Limited or no security patches
  • No official support
  • Increased compliance risks
  • Growing compatibility issues with modern technologies
  • Higher maintenance costs

For enterprise organizations, remaining on unsupported software introduces operational and cybersecurity risks that continue to grow over time.

Rather than viewing migration as a technical project, it should be treated as a strategic modernization initiative.

Why Enterprises Need a Migration Checklist

Enterprise websites are significantly more complex than standard CMS implementations.

They often include:

  • Multiple websites
  • Multiple environments
  • Third-party integrations
  • Marketing automation
  • Personalization rules
  • Custom modules
  • Customer portals
  • Internal applications
  • APIs
  • Authentication systems

Without a structured checklist, important dependencies can easily be overlooked.

The Ultimate Kentico 13 End-of-Support Checklist

1. Confirm Your Current Kentico Version

Before planning anything else, verify:

  • Kentico version
  • Hotfix version
  • Installed modules
  • Licensing information

Many organizations assume they are on the latest Kentico 13 version when they are actually several hotfixes behind.

2. Review Microsoft's Technology Compatibility

Review your:

  • .NET version
  • ASP.NET framework
  • IIS configuration
  • SQL Server version
  • Azure resources
  • Hosting environment

Ensure every dependency is compatible with your future platform.

3. Inventory Every Website

Document every digital property including:

  • Corporate websites
  • Regional sites
  • Microsites
  • Landing pages
  • Customer portals
  • Internal portals

Many forgotten websites become migration blockers later.

4. Document Custom Development

List every customization including:

  • Custom Modules
  • Employee directories
  • Product catalogs
  • Forms
  • Search modules
  • Custom Widgets
  • Hero banners
  • Sliders
  • Landing page widgets
  • Custom Page Types
  • Industry pages
  • Blog pages
  • Product pages
  • Scheduled Tasks

Document every scheduled automation.

5. Audit Third-Party Integrations

Review integrations such as:

  • CRM
  • ERP
  • Marketing Automation
  • Salesforce
  • Microsoft Dynamics
  • HubSpot
  • Stripe
  • Payment gateways
  • Azure services
  • APIs
  • Authentication providers

Determine whether each integration requires redevelopment.

6. Analyze Your Content Structure

Review:

  • Page types
  • Taxonomies
  • Categories
  • Metadata
  • Media libraries
  • Document relationships

This is the perfect opportunity to eliminate years of accumulated content clutter.

7. Remove Unused Content

Archive or delete:

  • Expired campaigns
  • Old landing pages
  • Duplicate blogs
  • Obsolete media
  • Outdated products
  • Unused forms

Migrating unnecessary content increases project complexity.

8. Audit User Permissions

Review:

  • Roles
  • Editors
  • Administrators
  • Department permissions
  • Security policies

Remove inactive accounts before migration.

9. Review Security Configuration

Perform a complete security assessment including:

  • HTTPS
  • SSL certificates
  • Authentication
  • MFA
  • Password policies
  • API security
  • Server hardening

10. Evaluate Performance Bottlenecks

Measure:

  • Page speed
  • Database performance
  • Cache configuration
  • Search indexing
  • Image optimization
  • Server response time

Migration is an ideal opportunity to improve performance.

11. Review SEO Assets

Protect your SEO investment by documenting:

  • Meta titles
  • Meta descriptions
  • Canonical URLs
  • XML sitemaps
  • Robots.txt
  • Redirects
  • Structured data

SEO should never be an afterthought.

12. Document URL Structures

Create a complete inventory of:

  • Friendly URLs
  • Redirects
  • Landing pages
  • Campaign URLs

Changing URLs without planning can significantly impact search rankings.

13. Audit Forms

Review:

  • Contact forms
  • Lead forms
  • Quote forms
  • Newsletter forms
  • Event registrations

Ensure all submissions continue functioning after migration.

14. Review Marketing Automation

Document:

  • Email workflows
  • Automation journeys
  • Segmentation
  • Lead scoring
  • Trigger rules

Marketing processes often require redesign when upgrading.

15. Audit Personalization Rules

List:

  • Audience segments
  • Dynamic content
  • Personalization widgets
  • Customer journeys

Not every personalization feature migrates identically.

16. Review Search Functionality

Document:

  • Smart Search
  • Azure Search
  • Filters
  • Faceted search
  • Product search

Ensure search remains fast and accurate after migration.

17. Analyze Analytics Setup

Review integrations including:

  • Google Analytics
  • Google Tag Manager
  • Microsoft Clarity
  • Adobe Analytics
  • Cookie management

Migration often changes tracking implementations.

18. Review Media Libraries

Analyze:

  • Images
  • Videos
  • PDFs
  • Documents
  • Downloads

Optimize file sizes before migration.

19. Create a Backup Strategy

Before any upgrade:

  • Database backups
  • Media backups
  • Configuration backups
  • Source code backups
  • Azure backups

Test restoration procedures.

20. Plan Your Testing Strategy

Testing should include:

  • Functional Testing (Navigation, Forms, Search, Login)
  • Performance Testing (Load testing, Stress testing)
  • Security Testing (Authentication, Authorization, Vulnerability scanning)
  • User Acceptance Testing

Allow business users to validate the new platform.

21. Identify Legacy Features

Some legacy features may:

  • No longer exist
  • Require redevelopment
  • Need replacement
  • Offer better modern alternatives

Avoid rebuilding outdated functionality unnecessarily.

22. Review Infrastructure

Evaluate:

  • Cloud hosting
  • Azure architecture
  • CDN
  • Storage
  • Backup systems
  • Disaster recovery

Migration provides an excellent opportunity to modernize infrastructure.

23. Build a Rollback Plan

Every migration should include:

  • Recovery procedures
  • Backup validation
  • Rollback scripts
  • Emergency contacts

Hope for success but prepare for contingencies.

24. Train Your Content Editors

Introduce teams to:

  • New content workflows
  • Updated page builders
  • Administration interface
  • Publishing processes

Training accelerates adoption and reduces post-launch support requests.

25. Partner with an Experienced Kentico Migration Team

Perhaps the most important checklist item is selecting the right migration partner.

A specialized Kentico partner can help with:

  • Discovery workshops
  • Technical assessments
  • Migration planning
  • Custom development
  • Content migration
  • QA testing
  • Performance optimization
  • Security reviews
  • Post-launch support

An experienced team reduces risk while accelerating project delivery.

Common Mistakes Enterprises Make Before Upgrading

Many organizations underestimate the complexity of enterprise CMS migrations. Some of the most common mistakes include:

Treating the Upgrade Like a Simple Software Update

Moving from Kentico 13 to Xperience by Kentico is not a routine patch. It often requires architectural changes, redevelopment of custom functionality, and rethinking content models.

Ignoring Technical Debt

Years of accumulated custom code, outdated integrations, and unused modules can significantly slow migration efforts if not addressed beforehand.

Overlooking Business Stakeholders

Successful migrations require collaboration between IT, marketing, content editors, security teams, and executive stakeholders. Keeping migration as an IT-only initiative often leads to missed business requirements.

Delaying Content Cleanup

Migrating every piece of historical content increases project timelines and costs. Cleaning up content before migration reduces complexity and improves long-term governance.

Skipping Comprehensive Testing

Insufficient testing can result in broken forms, SEO issues, accessibility problems, and performance degradation after launch.

Benefits of Completing This Checklist

Organizations that complete this preparation typically experience:

Faster Project Delivery

Well-documented environments reduce unexpected development work.

Lower Migration Costs

Identifying unnecessary features and content early helps control budgets.

Reduced Business Risk

Proper planning minimizes downtime and avoids disruptions to customer experiences.

Improved Security

Security reviews ensure your new environment follows modern best practices.

Better Website Performance

Migration is an ideal opportunity to optimize code, infrastructure, and content delivery.

Stronger SEO Protection

Careful URL mapping and metadata preservation help maintain search engine visibility during the transition.

Improved User Experience

Modern page-building capabilities, streamlined workflows, and enhanced personalization create a better experience for both visitors and content teams.

Recommended Migration Timeline

Although every enterprise has different requirements, the following timeline provides a practical framework:

6–12 Months Before Migration

  • Conduct discovery workshops
  • Perform technical assessments
  • Inventory content and integrations
  • Review custom development
  • Estimate project scope

3–6 Months Before Migration

  • Finalize architecture
  • Begin redevelopment
  • Clean up content
  • Prepare infrastructure
  • Plan testing

1–3 Months Before Launch

  • Complete data migration
  • Perform quality assurance
  • Validate SEO
  • Conduct user acceptance testing
  • Train editors

Launch Phase

  • Execute migration
  • Monitor performance
  • Validate integrations
  • Verify analytics
  • Resolve any post-launch issues promptly

Final Thoughts

The approaching Kentico 13 End-of-Support represents more than a deadline—it is an opportunity to modernize your digital experience platform, improve operational efficiency, and future-proof your organization.

By following this 25-point Kentico 13 End-of-Support Checklist, enterprises can significantly reduce migration risks, preserve valuable digital assets, maintain SEO performance, and ensure a smooth transition to the next generation of digital experiences.

A successful migration is built on preparation, collaboration, and a clear understanding of your existing environment. The earlier you begin planning, the greater your flexibility to optimize architecture, streamline content, modernize integrations, and deliver a better experience for both your business users and customers.

Rather than viewing the upgrade as a technical necessity, consider it an investment in your organization's long-term digital strategy. With the right planning and an experienced migration partner, your transition to Xperience by Kentico can become a catalyst for innovation, improved performance, stronger security, and scalable growth.

Frequently Asked Questions (FAQs)

Is Kentico 13 reaching End-of-Support?

Yes. Organizations should begin planning their migration well in advance to avoid the risks associated with unsupported software, including security vulnerabilities and compatibility challenges.

How long does a Kentico 13 migration take?

The duration depends on the size and complexity of the implementation. Small websites may take a few months, while enterprise environments with multiple sites, custom modules, and integrations often require six months or longer.

Can all custom modules be migrated directly?

Not always. Many custom components require redevelopment or modernization to align with the architecture of Xperience by Kentico. A technical assessment is recommended before starting the project.

Will migrating affect my SEO rankings?

A well-planned migration should preserve SEO performance. Maintaining URL structures, implementing proper redirects, retaining metadata, and validating technical SEO before launch are essential best practices.

What is the biggest risk of delaying a Kentico 13 upgrade?

Delaying increases exposure to security vulnerabilities, unsupported software, rising maintenance costs, compliance issues, and reduced compatibility with modern technologies. Planning early gives organizations greater control over timelines, budgets, and business continuity.

Ready to Upgrade from Kentico 13?

If your organization is preparing for the Kentico 13 End-of-Support, now is the ideal time to assess your environment, identify migration challenges, and build a roadmap tailored to your business goals. A structured approach backed by Kentico experts can help ensure a secure, efficient, and future-ready migration with minimal disruption.

Pawan
About the Author Pawan

With over 15 years of experience in software development and technology leadership, Pawan Sharma specializes in designing and delivering scalable, high-performance digital solutions. With expertise in modern web technologies, cloud platforms, AI-driven applications, and enterprise software development, Pawan has successfully led cross-functional teams through the complete software development lifecycle. Passionate about innovation, clean architecture, and emerging technologies, Pawan is dedicated to building robust solutions that enhance user experiences and help businesses achieve their digital transformation goals.

Follow on LinkedIn
Share this article: Share on LinkedIn Copy Link
TAGS: CMS