Brian, "Migration" is a big word, and so is sharepoint. What you want to migrate and what you don't is the question and the problem. Remember that sharepoint is a platform, not a product. MS allows you to build custom solutions on that platform, so depending on what you build the migration will be different:
1. Want to migrate changes to look and feel you made with sharepoint designer? Use corasworks design migratory 2. Want to migrate code and customizations made on the file system? Use solutions packages and features 3. Want to migrate content? Use tzunami, or metalogics or avepoint or the like See? You have options, but the question is too big and depends on the scenario. That is why I am saying there are no best practices to your question - because the question was too broad. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian H. Madsen Sent: Friday, 16 November 2007 11:12 AM To: [email protected] Subject: RE: [OzMOSS] RE: Best practises Thanks guys, seems the list is getting busy again. A bit of traffic happening this week. I'll send one email with a reply to everybody that's responded instead of flooding the mail server with replies from me. Ishai: I'm assuming that the reason for this is that each job is pretty much a custom job. Still, as migrations go, i'm just surprised that nobody seems to have a "general" path that needs to be taken. Dave: you mention a feature/solution...you mean a third party tool/application? you have a preference? Aaron: I agree with you on the term - unfortunately it's a Buzzword/Buzzsomething that everybody seems to be able to relate to. Thanks for the tips on Bill English - will check out what he has to say. Sezai: thanks for the link, will read through that as well..looks like the best way to proceed from here is really just to start from scratch and do a trial/error approach, padded with the info i can find from Bill English's articles and the link you provided. General: Why is it there's such a large "gap" in terms of doing a MOSS migration? Seriously, the application isn't completely ad-hoc and does have some standards across the board. Anyways, will take the advise on board and work from there..cheers! ________________________________ From: [EMAIL PROTECTED] on behalf of Sezai KOMUR Sent: Fri 11/16/2007 8:44 AM To: [email protected] Subject: [OzMOSS] RE: Best practises Yes, each migration job will most likely be custom and migrations vary between different implementations of systems. Even migrating from something like MCMS can vary quite a bit between implementations, a lot of MCMS sites have components built differently, with strange implementations of subsystems using CMS PAPI. If your organisation is likely to do many of the same type of system migration to MOSS, you can reuse your migration process and refine it and get some reuse of any custom code you may have developed. As for best practice? I guess you can apply the best practice of any migration project - http://www.esj.com/news/article.aspx?EditorialsID=1918 Sezai Kömür Senior Developer - Microsoft Certified Technology Specialist - http://www.moss2007.com.au/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ishai Sagi Sent: Friday, 16 November 2007 7:49 AM To: [email protected] Subject: [OzMOSS] RE: Best practises Nope. There are no best practices and everyone makes up his own depending on what you want to migrate. Ishai Sagi Solution Architect Information Management MVP Microsoft Office SharePoint Server Direct: 02 8001 7717 Fax: 02 8001 7778 Mobile: 0423 791 728 Email: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> Web: www.uniqueworld.net<http://www.uniqueworld.net/> Blog: www.sharepoint-tips.com<http://www.sharepoint-tips.com/> innovative business solutions that make a difference From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian H. Madsen Sent: Friday, 16 November 2007 9:41 AM To: [email protected] Subject: [OzMOSS] Best practises Hi Guys, Lately i've been wondering if there's such as thing as MOSS to MOSS Migration Best Practises? It seems that everybody has a solution/suggestion on how it's best done but insofar as i can see there's no "connect" between suggestions. As i'm sure i'll be doing a lot of migration work in the near future i was wondering if anybody has any further info lying around on the topic? oh, that they're willing to share that is :) Regards Brian H. Madsen Microsoft MVP Visual Developer ASP.Net ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
