22 Jan 2007
01 Mar 2011
Link to this post
Unfortunately, compared to John's situation, our 3.7SP4 company web is about 500 pages.
Steve, you were absolutely right. I felt really sad the other day when I teased myself into trying the migration tool. Excited after a million steps of presumably accurate preparation, the tool hangs, probably close to the final steps, and the pages that were generated just displays errors referring to the old SF assemblies. I was able to grab some of the log output in the conversion page, and among other things it does not like that I have English pages (?)
I understand that there are lots of things that are far from ready with version 4. Still, I think I could live with those issues for a while. And this week we can't delay any further, the addition of a considerable amount of material to the web. (including some controls, or whatever it is called in version 4)
What makes me really disappointed is that Telerik released version 4 without having an official migration tool, which was supposed to be available at that moment.
And to top it off, I felt that we had been very cautious not to complicate the 3.7 project, just to make sure we would be on the fast track when arriving at the gate of migration.
We need to convert pages (with templates) and libraries (images/documents/etc). Would like to have generic content and lists converted (to something similar?), but we can also move those items (70-80) manually if we have to. We can do without blogs, news and forums. (not too much here)
We can also recreate, users, roles and page rights if needed. And of course, nice with a marker where our user controls used to be.
In my search results there are no indication that anyone has ever come out with anything useful from the migration tool. Anyone?
And it seems Telerik has been very quiet about details for any future migration plans. After my unsuccessful migration attempt the skeptical part of me would like to know:
- Is version 4 stable for production, even with simple projects? I case I would expect the migration tool to be considered a core function, provided in the package, not open source. (sorry, don't have time, I choose to pay for products with such options)
- Or, is the plan more or less to have the need for migration fade away as time goes by?
In that case I would really like to know right away, to be able to find the best point in time to start manual conversion.
Well, I could understand, if the structure of v4 is even more radically different from v3.7, than what I've heard.
In case the SF4SP1 (to come in the next hours I read) would bring an updated migration tool, or someone can help me point out a simple fix by reading my migration log (using a ticket?):
Since I know little of the v4 structure, and the 3.7 doesn't really fit the new environment, is there a risk that we would bring over stuff or structures that later will turn out to be a problem? I'd hate to have a haunted project..
Honestly, even with 500 pages and lots of libraries, do anyone still think it is better to convert manually?