A quick tip on upgrading Sitecore fast and easy

Today my colleague @alinulms and I had the “fun” task of updating an old Sitecore 6.5 to version 7.2.

Actually we really want to upgrade the solution to Sitecore 7.5 but we are still waiting for Sitecore. I really hope 7.5 will be officially released any time real soon.

I’ve upgraded Sitecore installations at least a trillion times before (or so it feels) and depending on the version, build environment etc. I’ve used a number of different approaches. The approach we used today was extremely effective so I thought that it deserves a blog post.

The tip is simply, don’t upgrade the actual solution, instead point a clean Sitecore on the solution databases, upgrade this solution, then fix your code and configuration afterwards.

Back when migrating content to a new installation was the way to go

When I’ve upgraded from Sitecore 5.3 – 6.3 to a version 6.4 or higher I would almost always simply move the content to a new version and then upgrade my codebase.

I’ve simply setup a new Sitecore with databases and everything. Then I moved all the production content into the clean new Sitecore using either Sitecore packages or later serialization.

When the content was in the new Sitecore then I’ve merged the code and configuration in as well. How this can be done depends on the solution setup. Here at Pentia we simply use our buildlibrary and subversion to do this for us which makes this task a real no-brainer so we can focus on getting the code updated to fit the upgraded API.

Last step was then to get the new databases out into production again and maybe sync any minor content changes if the upgrade had been slow.

The reason for not following the normal Sitecore upgrade path found on sdn is the amount of packages, sql scripts, configuration changes and other steps along the way. There is a lot of pitfalls when following the steps one by one.

Moving content does not work well on large solutions, it becomes too time consuming compared with installing the upgrade packages.

Some great tools such as TDS and Razl from Hedgehog or Unicorn can help restoring the content into clean databases. These tools are not always available to you as a developer and again the amount of especially media data can become an obstacle.

Migrating content to a new solution can be a bit reckless since the moved items are not updated and new versions of the UpdateInstallationWizard performs some post installation steps which fixes some field values on standard fields.

Luckily Sitecore made the upgrades a tiny bit easier in the later versions, a bit more stable. Now it is simply installing the initial releases one by one and then finally the latest version.

Upgrading an out-of-the-box Sitecore webroot with a database full of content

This was the approach we went for today and wow it was actually fast.

The solution we were upgrading is relative big, the master database is about 20 GB and we do not use neither TDS nor Unicorn on this solution. Moving the content via packages is not an option due to the huge amount of data. Instead we followed the upgrade path found on SDN but with a small twist that made it go quick and easy since we could ignore most of the instructions.

Here is a quick recipe based on what we did today.

  1. Copy databases – Make a copy of all the solution Sitecore databases preferably using detach/attach. Include webforms databases etc.
  2. Install a temporary clean Sitecore – Take a clean Sitecore webroot, same version as the solution, point the connection strings to the copied databases and setup the site in IIS.
  3. Install upgrade packages – Download the required packages from sdn. Log into Sitecore and go to the <new site>/sitecore/admin/UpdateInstallationWizard.aspx page. Install the .upgrade packages from SDN one-by-one and run SQL scripts as needed. Also update config if needed. This can be done by simply copying in the new config files.
  4. Drink a lot of coffee – while waiting.. Each upgrade package takes a few minutes to install
  5. Install module upgrades – When the solution is upgraded to the desired Sitecore version then install all module  updates if any (webforms, ecm) again using the UpdateInstallationWizard.
  6. Delete the temporary site – Delete the temporary webroot
  7. Merge your code in – Get a clean webroot of the new Sitecore version and move your code into this. This step depends on how you are working with Sitecore and cannot really be described. Just get all your code and markup back where it belongs. Rebuild indexes and link database.
  8. Fix code errors – some tips
    1. The major API change between 6 and 7 is of course Sitecore.Search. This can be a big task depending on the solution.
    2. Remember to remove any old Sitecore support patches etc. which is no longer valid.
    3. All Visual Studio projects which are dependent on the Sitecore kernel need to be updated to target framework 4.5 or later when upgrading from 6 to 7.x
    4. Remember the Sitecore AntiCsrf module and that Text fields are suddenly output-escaped. This can sometime cause trouble when upgrading.
  9. Rinse Repeat – Repeat step 1 – 6 in other environments (preprod, production)
  10. Deploy – Deploy the upgraded website in other environments

Step 9 and 10 is of course dependent on the specific customer setup. If possible then make a copy of the production databases , tell the editors to stop working for some hours, run the upgrades, drink a lot of coffee, deploy all the new code to a new folder on the different servers. Finally make a clean switch by simply changing the website root path in IIS on all servers to the new folder. No downtime at all, just a site restart. This approach requires that you can freeze the content while upgrading though so it need to be done fast.

Using this approach you will never really leave the UpdateInstallationWizard.aspx so you don’t always have to mind all the other steps that Sitecore instruct you to do such as  deleting temporary files etc. a lot of these steps can be skipped. Updating config can be done by copying in the new config files instead of manually merging in the changes.



The main point is simply to upgrade an empty Sitecore so you do not have to fix your code each and every step on the way to the desired version.

If you have any experience in upgrading Sitecore, good or bad please share in the comments below.

A sneak-peak on Sitecore 8

I just checked my Sitecore 8 Tech preview and the UpdateInstallationWizard has not been updated.. Or at least it looks the same. Perhaps Sitecore will do some magic before the final release, I sure hope that they at least will get rid of the very long checklists on sdn. These manual tasks should almost all be automated.

Anders Laub

Anders Laub Christoffersen

Anders has been working with Sitecore for over a decade and has in this time been the lead developer and architect on several large scale enterprise solutions all around the world. Anders was appointed the title of Sitecore Technical MVP in 2014 and has been re-appointed the title every year since then.

4 thoughts on “A quick tip on upgrading Sitecore fast and easy

  1. Nice post.
    I agree that the package transfer used before is no longer an option…
    1. for the size of the content database
    2. for the upgrades to content items themselves (http://www.seanholmesby.com/sitecore-upgrade-post-step-scripts/)

    I’d be very careful with straying from Sitecore’s notes though.
    For instance,
    “Using this approach you never really leave the UpdateInstallationWizard.aspx so never mind all the other steps that Sitecore instruct you.”

    That won’t work with one of the Sitecore 7 upgrades because the UpdateInstallationWizard itself was updated through one of these other steps in a Sitecore package (not the .update package).

    But maybe this example falls into the ‘upgrade other modules’ step though.


    …and to go the other way…. there is also a bug in the regular Sitecore 7.1 upgrade process, which may mean broken Rules fields for content editors.

    – Sean

    • Hi Sean, thanks for your comment.

      You’re right, you do actually have to leave the UpdateInstallationWizard shortly and install a new version of UpdateInstallationWizard via the Package Importer twice whilst upgrading 7. This poses no issue at all since the package importer works fine as do most of the Sitecore client except for custom stuff. Maybe I should mention this in my post.

      I think I will update the post with a disclaimer text as well 🙂 Always read through Sitecores notes and determine if they are critical.

      The types of steps you can skip until you are on the final version and the code has been merged is:

      – analyze package (you are running on a copy database anyway)
      – Update your configuration files (done when merging code into new webroot)
      – Clear browser cache (you dont need to do this until all packages has been installed)
      – Rebuild indexes (done when merging code into new webroot)
      – Rebuild link database (do this after installing the last package)
      – Delete various temp files (done when merging code into new webroot)

      My point is that these steps does not have to be performed after installing each package. Except for rebuilding the link database they are done implicitly when merging your code into a new Sitecore webroot.

      • Hi Anders,
        I think you make a good point about skipping the unnecessary steps. Analyze package and browser cache definitely don’t need to be done.
        Although a couple of those points maybe shouldn’t be deemed unnecessary, and shouldn’t be skipped.

        In particular, these two:-
        – Update your configuration files
        – Rebuild link database

        The reason why I say this is because these two (in some upgrades) are crucial in determining how the items in the database are updated.

        The link to my post about the Post Install Steps mentions that Sitecore will upgrade some items at the end of the package install. The 7.1-upgrade fix blog post mentions that it tries to do this using the LinkDatabase, which knows what to do based off the FieldTypes.config.

        So therefore, the config needs to be correct (as up-to-date as possible) in order for the LinkDatabase to know the correct links…..in order for the Post Install Step to run correctly and update the items in the database.

        Other Post Install Steps also perform Sitecore Queries…. Where, if you don’t change the config setting ‘Query.MaxItems’, it’ll only return a limited set, and you could have a partially-updated database.

        Just some things I’ve come across in our Sitecore Upgrade work…


        • Hi Sean,

          Thanks, we did not run into these issues on that specific solution since it does not use any rules (it is one we inherited from another Sitecore partner).

          I’ve updated the post a bit.


Leave a Reply

Your email address will not be published. Required fields are marked *