There is a very strong possibility that I will be tasked with an awesome project; Migrating SharePoint 2010 Foundation to SharePoint 2013 (Foundation, Standard, Enterprise, who knows). Here’s a little of what the potential client will expects help with; high level write up sent by the client (a few points)
- Analyze existing site collection structure and make design recommendations to improve usability
- Make recommendations for design of architecture/server farm, estimated growth and
security for VMware. - Make recommendations for redundancy / backup to cloud
- Make recommendations for an Enterprise SQL Server DB that would store the SharePoint
content - Outline an approach for migrating to the new platform including recommended tools to assist in this process
There are other items as well but for now I only want to stick with migration. I know there are lots of questions I need to ask the client; What are they??? I would like some feedback from the community on their experiences and resources used to be successful on this venture. I have done migrations in the past wss to 2007 to 2010 internally but this is a different ball game as someone else outside of our company is looking for expertise.
Â
Regarding SharePoint Migration we should ensure some things. We can ask some questions to our SharePoint Migration Consultants are as follows:-
- How stable your SharePoint(any version)?
- What is Min Role?
- Do architectural changes include or not?
- Whats migrated?
- How can we fix bugs?
Hey Jason,
Here is some stuff that I would ask the client:
- Do you have any custom solutions? Do we need to recode it, do you want to keep same code, etc.Â
- Do you want High Availability / Disaster Recovery in your new environment.Â
- Do you want to migrate content as is, or do you want to re-organize content.Â
For analyzing current site collection structure, make sure you check if security is clean or not as well as DB Size. Â Do they have 1 Site Collection with 1000 sub sites that makes only 1 content DB of 1TB, or they split it up well.Â
Server Architecture will depend of # of users as well as HA/DR Requirements. Â SharePoint can (in theory) easily add servers, so shouldn’t be worried about growth.Â
Check this out for DR in the cloud >Â http://azure.microsoft.com/en-us/documentation/infographics/sharepoint-sqlserver-alwayson/Â
Enterprise SQL Server Recommandations > Read this Whitepaper done by me  > http://1drv.ms/1o4JubZ
Either using tools or not will depend if they want to  change content structure . IF they don’t wanna change content, I suggest using a DB Attach. If they want to change and reorganize content, I Suggest using a tool such as ShareGate. (see a list of tools here: http://sharepoint-community.net/page/sp-migration-tools) .
If you are doing DB Attach, here is what I Suggest.
- Migrate 2010 > 2013 , but keep in compatibility mode. Â This will bring you some new 2013 features, and will let you upgrade your code meanwhile if you got any.
- For Every Site Collection, simulate the upgrade to 2013 mode. Â If it works well for you, do the upgrade!
Lastly, check out this session from SPC14:Â The nuts and bolts of upgrading to SharePoint 2013″Â Â http://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC410Â
Hope I helped you a bit and I am sure other members of the community got other stuff to add!
