Hi There
Just thought to seek some guidance on choosing between In-Place (IE, SP 2007 to SP 2010 to SP 2013) and Tool-base migration. Which is a better option and what is the trade-off or points to consider between both methods?
Many thanks in advance! Have a great weekend ahead!
Hello again,
If it’s painfull to go from 2007-2013 depends on the amount of customizations. If you have many then of course to rewrite your code is painfull, also you have all the references to wsp files, assemblies and so on. But will you create new farm solutions (wsp) files for SharePoint 2013? OR will you use the app model, because that is also questions you have to ask yourself.
You have a great tool for checking this:Â http://www.spcaf.com/analyzers/migrationassessment/
But sometimes you will save alot of time and efforts to recreate everything in 2013 instead of trying to do the upgrade path. As I mentioned all the tools mentioned are very good, I have used both Metalogix, Sharegate and AvePoint with great results. But what I would do is to download a trial, and compare them. And of course I would also get a quote about prices to compare them as well. you can always email me or call me if you want to have a chat about this. I have done this several times, both the inplace way, and the migration way. So would be happy to assist you on planning this. Any migration/upgrade project need to be planned to have success.
My email is: knutrelbemoe@outlook.com
Hi Ben, Knut and Gemma
Many thanks for all the good advice and pointers!
Totally agreed with Ben on the pain of going from SP 2007-2010-2013, it is just to stressful, I suppose.
To Knut, my environment is like any typical SP 2007 farm, a single content DB with many customization built so, have decided to break into Informational (All OOTB content) and Transactional (All Custom Built Web Application). For Informational, I am looking at using Tool to move but not sure what to look out if taking this route.
With all the pointers thus far, am so much clearer of what needs to be done and greatly appreciate all of you.
Have a great Friday and weekend!!
Cheers!
Hey Ivan,
You’ll have way too many issues to work out just going from 2007 to 2010 and then again from 2010 to 2013 that it is almost not worth going that way.
If you need help on building an inventory of what you have and planning migration, I wrote a post that may help:
http://en.share-gate.com/blog/how-to-build-an-inventory-before-sharepoint-migration
And did a short video to explain it http://en.share-gate.com/blog/build-sharepoint-inventory-for-migration-b2f
In that last link with the video, I also added a few links to migration series I wrote as well as reasons why a migration can fail. Hopefully those tips and how-to’s can help you get going.
As a note, I do work for Sharegate (one of those migration tools mentioned) and I encourage you to check out all the tools to see which fits your needs best. http://en.share-gate.com/  and well it’s Friday so why not a little humour  http://en.share-gate.com/funny
If you have any questions, don’t hesitate 🙂
Hello Ivan, actually you need to ask yourself first what shall be migrated, only content, or sites. Also need to analyze the 2007 environment. Is it just out-of the box functionallity there, or is it some custom code.
You have many great 3rd party tools, Metalogix, Metavis, ShareGate, AvePoint. all that could do this migration process. Metalogix has a 25gb free version I think.
I have also successfully runned a in-place upgrade, but then you first have to go to 2010, and then to 2013. But if you know what you are doing this is also a possible way to go. Let me know if I can assist you on this matter.
Definitely, different timezone is never a hassle … Good day!
