Is it possible to move a project from Kentico 7 to kentico 12?

Every new version of Kentico always has some changes that impact development. Whether it’s a new feature or the realignment of an API, there is no doubt there is going to be some updates that have to be made within your application. While this can be a daunting task for some, Kentico offers a great tool to help you through the process. In this article, I’ll show you how the Kentico Upgrade Tool can simplify your upgrades, and save you a lot of headaches.

Deciding to upgrade a core component of your business is not always an easy choice. There’s downtime to consider, the development effort to apply the upgrade, and the impact a new feature or interface will have on end-users. Other factors to consider are whether or not the upgrade includes important security fixes, performance enhancements, and key features that will streamline your business processes. Without a doubt, deciding when and how to apply an upgrade to your CMS is not a decision taken lightly.

So what are companies to do? In this article, I’ll attempt to walk you through both the benefits and the drawbacks of each side of the dilemma that, sooner or later, faces every CMS customer.

It's Thursday somewhere right?  Take advantage of this throwback Thursday tip when upgrading your Kentico 7 (or even 6) instance to newer versions.  

Kentico provides some great documentation and directions on upgrading major versions.  Unfortunately, they can't perform their tests on every website scenario..  What I'm going to provide to you today is one very large tip when upgrading those older instances of Kentico.

Over the last couple of weeks we have worked on several upgrades of our existing sites to Kentico 9, which was released last month. While the upgrade process overall went pretty smooth, one issue popped up in almost all of our cases. In our projects we tend to leverage page related views (View_[ClassName]_Joined) in repeaters/univiews with custom queries which are removed during the upgrade process. This post will give you insights on how we handled this.

Kentico 9 was officially released to the public on Tuesday 24 November 2015, at the annual Kentico Connection conference in Kentico's home town of Brno, Czech Republic. I was lucky enough to be at the conference, including the official launch party!

There's been a huge buzz around this release, especially among solution partners such as Get Started, as it represents a huge leap forward for the platform. In addition to a slew of tweaks, improvements and optimisations, Kentico has really stepped up its game with some modern enterprise-level features such as class-leading Continuous Integration (CI) tools, ASP.NET MVC development support, and brand new Integrated Campaign Management which allows marketers to harness the huge volume of data behind Kentico EMS.

Upgrading Kentico and feeling lost? Are you unsure about upgrading Kentico because of your customizations? Is there a possibility to customize Kentico while having a simple upgrade? Get answers to these questions and assure yourself that there is an easier way to upgrade to the newest version.

Hello Team,We are facing a some issues after upgrading our site to 8.2 version.We were having site in 8.0.21 version , so we upgraded it to 8.1 first , then we did not find much difference, but onc...

This article describes how to resolve “The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.View_CMS_Tree_Joined_Regular' and the index name 'IX_View_CMS_Tree_Joined_Regular_NodeSiteID_DocumentCulture_NodeID'. The duplicate key value is (3, en-US, 87091).” error.

When upgrading your CMS from version 6 to version 7, you may experience the error: Must declare the scalar variable exception in CMS Desk and also within the Event log.