Background Over the past few months I have met with a large number of clients with SharePoint 2007 implementations who are asking the SharePoint million dollar question , “Should we migrate our SharePoint 2007 environment to SharePoint 2010 or should we just go right to SharePoint 2013?
In fact the migration of a simple SharePoint installation should be pretty straight forward but in the case where there have been customizations been made to the SharePoint applications which is more often than not the case then a customized SharePoint migration solution needs to be implemented
We have approximately 800 users and 2 data centers and would like to achieve a “big bang” migration by moving everything over all at once
Use a Migration Solution If you happen to be in one of those camps where you either have a real messy SharePoint data environment or you want to move from an older version of SharePoint, then using a migration tool may be your best option. Migration tools can allow you to clean your content as you move it over
I particularly loved asking the two questions during the thrilling and meteoric rise of SharePoint 2007, mostly because no one really had a clue and that allowed me to ask another question, “So do you think you’re aware of all the sites and all the content you have in SharePoint within your organization?
Or am I wasting my time with my SharePoint 2010 deployment or upgrade from MOSS 2007?
We have SharePoint 2007 > What do we do?...If you are on SharePoint 2007, should you skip 2010 and go to SharePoint 2013?
no search term matches found in comments.
Oleson & Wagner’s template on MOSS 2007 includes two sections on policies: operational and application usage
Using other information as a guide, this means that just like O365 will not be renamed as features are added, a proposed SharePoint 2015 major release will be the last new 'name' and full development cycle that we have been used to since the release of 2007
If SharePoint 2015 is truly Microsoft's final on-premises release, how many organizations that typically lag behind the adoption curve will even end up going through the effort to upgrade when they probably should seriously consider a migration to the cloud instead?