0

We are maintaining one Sitecore 7.2 installation with

  • Lots of ASCX / Web Form
  • Lots of custom code hooked into Sitecore using configuration / patches
  • SOLR Search

We plan to migrate these system to 9.0. Will the majority of code be broken / completely rewritten or only some fixing is needed ? Is there any guideline that I should be following?

2

I've done the same on two different projects.

From my experience it should be fairly straight forward to update your webforms and normal usage of the Sitecore API. There might be minor changes, but it shouldn't take too long.

All of your hookins into pipelines etc. might still compile. But you will want to check if it's still needed. It may be a fixed bug, or some functionality that has been added to the main product (such as language fallback). Even if it's functionality that's still needed, and does compile, you will want to check if it's still placed the correct place, there are lots of new pipelines and processors.

By far the hardest part of the upgrade is analytics (from DMS to XDB). If you're not using DMS, you're in luck :)

As for migrating the Sitecore CMS data, I had problems with the database upgrade scripts on my first project, and ended up moving the data with a combination of Unicorn (for templates and settings) and Sitecore Sidekick for the content data (or Razl, if you prefer the paid alternative).

| improve this answer | |
  • So it means that WebForm is still supported in 9.0 right? Because I was afraid that I have to rewrite everything into MVC – qkhanhpro May 19 at 7:46
  • 1
    Yes, it's still supported. However if your client is looking to maintain this site for years to come, this might be the right opportunity to convince them to make the switch to a newer frontend tech. – morten.engel May 19 at 7:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.