Lars Fløe Nielsen

As some of you know, the Sitecore 6 database conversion tool has been in beta now for quite a while. The last intensive test report came up with very few issues, - mostly related to cosmetic issues.

I also know that several upgrade projects have been running simultaneously to the Beta, - and I wish to extend a thank you for the constructive and positive feedback.

Some issues have revealed themselves when our partners have been using the system. For example, while Sitecore has always been a product focusing on security, version 6 locks down even harder: Editors in the past with weak passwords would automatically not any longer have access to the system, and the admin must reset their passwords. This is great for security and ultimately for our customers, but what happens if the Administrator is the only user, and has a weak password too?

In this case, we are currently changing the password to the user name: Of course, whoever updates the system will get a post conversion notification to change the password(s).

Most of this stuff is really something we could release the product with now, but as part of our release strategy, we have decided not to release with known issues that would be inconvenient for our partners and customers.

Anyways, - now only 2½ months after the product release, it looks like we’re ready for the official release. These days, we’re passing the conversion tool to yet another test cycle, and if nothing pops up, - release day.

Some of you might read my post last week about the Sitecore upgrade strategy. In this respect, the tool for upgrading your web site to version 6 was released in an Alpha version.

This is already being tested by several developers, and so far responses have been positive. Ivan Shamarok has even blogged about it: http://sitecoregadgets.blogspot.com/2008/07/migrate-from-....

I decided to give it a try with my own little hobby project, which I would consider a fairly standard best practice web site, - with (multiple) data inheritance models and extensive use of standard values/masters. I also use a single proxy item.

As a twist, however, the site is a combination of editing/extranet site where the core and the public site would use the same security database. Another layer of complexity is that the user is allowed to edit their personal profile information. This, - I knew, would have to be addressed specifically (re-coded to Sitecore 6) as user objects would no longer reside in Sitecore, but in the .NET security database. According to documentation, this should be the only possible breaking change that requires recoding.

Before the conversion, I decided not to transfer Archive and Recycle Bin as both were empty, rendering these steps useless.

The database conversion took me 45 minutes; - even with such disturbance only a baby daughter playing on your lap can give you. In the data structure test I did after the conversion, I didn’t find a single conflict or issue. I was especially impressed that roles and users were moved so easily from the older structure to the new structure.

In the evening, I decided to address the issue of recoding the user profile editor. I grabbed the new user object which holds a property bag of all profile information (it wraps the .NET profile bag and simplifies read/write operations). I reckon recoding this took me less than half an hour to code and test (no baby on lap though).

Here’s my evaluation of the tool:

1. So far, - It seems to work without flaws. During my conversion, I didn’t found any issues. Off course, this is an Alpha, and I would love to hear about others experiences with the upgrade tool.
   
2. The process of upgrading your solution is around 10 steps. These steps all, except for two, seems mandatory, - and here comes my only “complaint” (I know this is being considered by the team): Why not create a single “go”-button that executes all steps? Optionally an “advanced” mode that switches into the current step-by-step mode (for those who have made significant customizations to the system). Anyways, - it’s a matter of saving 10-15 minutes.
   
3. The documentation is very comprehensive: It explains each step that you go through, - in detail, with screen-shots. In addition, it explains what you should be aware of, - given your solution is highly customized, - and what you should do to solve it.