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:
- Document Existing SharePoint Server's Topology (preferably in Visio format), Roles, Hardware/Software Specifications, Installed Updates, Software installed, Language Packs, etc
- Prepare a List of SharePoint Web Applications, Site collections, Host headers, Content - Service Application Databases, etc
- Document Central Administration Settings like User Policies, Quota Templates, Data connections, Zones, AAM, Quota Templates, Blocked File Types, etc
- Document All Third-party Software installed on top of SharePoint (Like Nintex workflows, Axceler control Point
- 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)
- Document Active directory Domains/Forest details. This will help in configuring User Profile Import connection sources, People Picker configurations.
- Document Current environment Out of the box Features enabled (Such as Publishing), Enterprise feature Enabled (such as InfoPath Farm Services)
- Document Outgoing, Incoming E-mail settings of the SharePoint server
- Document all IIS customizations made manually, like Web.config modifications, Add-ons installed in IIS (like Compression, URL Rewrite, HTTPHandlers etc)
- Document SQL Server configurations, Content DB sizes, Mirroring, Clustering configuration details
- Document any custom solutions deployed in Layout's folder or BIN folder.
- Prepare a report on User base with Total no. of users, avg concurrent users, etc
- Document custom scripts, automation tools you are running from SharePoint servers (like Monthly storage report generation script, scheduled with windows task scheduler)
- Make a Note of current environment's Information Architecture, including Managed Paths, Top navigation, etc.
- Document existing Farm's service accounts. Kerberos applied?
- Document Search Settings, including content sources, schedules, Keywords, Best-bets.
- Document Email Enabled Lists and Libraries
- What is the current Disaster recover plan? How often backups are taken? Third party software integrated with SharePoint (Like AvePoint, DPM, etc)
- Document Infrastructure details such as Load balancer, DNS, IPs, SSL Certificates, Publishing configurations (Like F5, TMG, ISA Server, etc)
- Document 12/14 hive Layout folder customizations, File system changes if any
- 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.
- Existing Branding Artifacts like Master pages, Themes, CSS Files, Logos, etc.
- Document the custom authentication providers (Forms, LDAP, etc) if any
- Document the current Monitoring setups like SCOM.
- 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.
You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.