25 Things to Document before You Start SharePoint Migration

So you are ready for SharePoint Migration? Before starting with Migration process, You must document things on the current environment, which includes, but not limited to:

  1. Document Existing SharePoint Server’s Topology (preferably in Visio format), Roles, Hardware/Software Specifications, Installed Updates, Software installed, Language Packs, etc
  2. Prepare a List of SharePoint Web Applications, Site collections, Host headers, Content – Service Application Databases, etc
  3. Document Central Administration Settings like User Policies, Quota Templates, Data connections, Zones,  AAM, Quota Templates, Blocked File Types, etc
  4. Document All Third-party Software installed on top of SharePoint (Like Nintex workflows, Axceler control Point
  5. Document Inventories & customizations like Solutions, workflows, Event Handlers, Web Parts, Features, Assemblies, Site Templates, Site Definitions, Custom Timer jobs, etc. (stsadm -o enumallwebs -includewebparts -includefeatures)
  6. Document Active directory Domains/Forest details. This will help in configuring User Profile Import connection sources, People Picker configurations.
  7. Document Current environment Out of the box Features enabled (Such as Publishing), Enterprise feature Enabled (such as InfoPath Farm Services)
  8. Document Outgoing, Incoming E-mail settings of the SharePoint server  
  9. Document all IIS customizations made manually, like Web.config modifications, Add-ons installed in IIS (like Compression, URL Rewrite, HTTPHandlers etc)
  10. Document SQL Server configurations, Content DB sizes, Mirroring, Clustering configuration details
  11. Document any custom solutions deployed in Layout’s folder or BIN folder.
  12. Prepare a report on User base with Total no. of users, avg concurrent users, etc
  13. Document custom scripts, automation tools you are running from SharePoint servers (like Monthly storage report generation script, scheduled with windows task scheduler)
  14. Make a note of the current environment’s Information Architecture, including Managed Paths, Top navigation, etc.
  15. Document existing Farm’s service accounts. Kerberos applied?
  16. Document Search Settings, including content sources, schedules, Keywords, Best-bets.
  17. Document Email Enabled Lists and Libraries
  18. What is the current Disaster recovery plan? How often backups are taken? Third-party software integrated with SharePoint (Like AvePoint, DPM, etc)
  19. Document Infrastructure details such as Load balancer, DNS, IPs, SSL Certificates, Publishing configurations (Like F5, TMG, ISA Server, etc)
  20. Document 12/14 hive Layout folder customizations, File system changes if any
  21. Make a note of all InfoPath Form libraries. You have to update the Form Template URL and You may have to change the data connections, etc.
  22. Existing Branding Artifacts like Master pages, Themes, CSS Files, Logos, etc.
  23. Document the custom authentication providers (Forms, LDAP, etc) if any
  24. Document the current Monitoring setups like SCOM.
  25. Last but not least – Make sure you have the version control system (like CVS, SVN, TFS, etc) which has all the artifacts including source code, installers, deployment guides.

Salaudeen Rajack

Salaudeen Rajack is a SharePoint Architect with Two decades of SharePoint Experience. He loves sharing his knowledge and experiences with the SharePoint community, through his real-world articles!

4 thoughts on “25 Things to Document before You Start SharePoint Migration

  • February 20, 2018 at 6:54 PM

    hello, some one help me to get migration document please.

    [email protected]

    sp2013 to sharepoint 2016
    sp2013/2010 to O365 sharepoint online

    Reply
  • July 11, 2017 at 8:56 AM

    Hi @Akshay,

    Please share the documents to [email protected] or possible publish it on blg as it will help others in our community

    Reply
  • October 5, 2016 at 11:07 AM

    Nice Article.
    Currently I’m migrating from SharePoint 2013 to SharePoint 2016.

    Reply

Leave a Reply