Migration from SharePoint 2007 to SharePoint 2013 challenges tips to know


In this post, we will discuss What is migration challenges or need to know or requirement for migration from SharePoint 2007 to SharePoint 2013.


Before migration from SharePoint 2007 to SharePoint 2013, we should have some clarification from the client side.

Also, read some SharePoint tutorials below:

SharePoint Online branding Creating Tabbed Menu using Bootstrap and HTML in SharePoint 2016/2013

Hub Sites SharePoint Online Office 365 Tutorial Download PDF Free

Creating Business Data Connectivity Service using SharePoint Designer 2013 in SharePoint 2013

These are the following’s point you know before start migration –

1. What is the current state of your SharePoint 2007 environment?

2. Do you have any customization’s that have been implemented that are business critical or need to be taken into major consideration?

3. What is the current state of your SharePoint infrastructure?
a. Do you have SQL Server 2008 implemented?
b. Is your organization ready for virtualization of 64-bit server farms?

4. How much content and what types of content do you have in your SharePoint 2007 environment?

5. Do you have major “team site sprawl” or multiple sites with the same content?

6. Have you identified the owners of this content and\or Site Owners?
a. More than likely some original site owners may no longer work in that department or others have taken on that responsibility

7. Has your organization broken “the SharePoint Golden Rule” by storing content in multiple locations (i.e. Rather than the SharePoint “one version of the truth” concept)
a. 80% of organizations have broken this rule so you are not alone, it’s time to get a handle of content sprawl and “surface” a piece of content in multiple locations instead of storing it in multiple locations

8. Do you have Microsoft Office 2010 installed within your organization?

9. Is there going to be any issues training users and do you have internal training strategies in place and\or what has worked in the past for training your organization’s team members?

10. Are users already comfortable with the “ribbon”

11. What is your licensing situation? Can you opt to go right to SharePoint 2013 with your licensing agreement or is SharePoint 2010 you’re only licensing option?

12. Infopath form and workflow will be the pain points

13. You will not be able to migrate the service application (SSP)

14. The hard part of your migration from 2007 to 2010 or 2013 is the evaluation of your 2007 customizations.

15. You must look at code-based customization’s, whether custom-built, in-house code or third-party tools, add-ins, or web parts.

16. It’s going to be important to understand exactly what type of workflows they have in place to see if they will need to be re-architected during the upgrade\migration.

17. Important to determine what has been done with the sites that were customized with SharePoint Designer so those need to be identified (URLs as well as the site owners).

18. Workflows and InfoPath or Web-based forms



19. Windows Server 2012 upgrades to the servers or they are going to need to upgrade to SQL Server 2008 or rather install a new SQL Server 2012 instance they can dedicate to whichever SharePoint version is implemented.

Check out Best Alternative to InfoPath -> Try Now

You May Also like the Following SharePoint Online Tutorials:

About Navneet Singh

I am Navneet Singh, Working at C3it software solutions pvt. ltd. in Pune. My core skills are SharePoint 2013, Office 365, SharePoint 2010, SharePoint Designer, SharePoint Designer Workflow, Nintex Workflow, Infopath, Webpart, CSOM/SSOM, Power-shell, C#, ASP.NET and SQL Server.

View all posts by Navneet Singh →