From bcd87f91ea8bbcc962da76d4728fdbb8182faa48 Mon Sep 17 00:00:00 2001 From: Ralf Koop Date: Sat, 8 Feb 2025 16:46:49 +0100 Subject: [PATCH] SP8: 2025-02-08 16:46:49 --- Technik/Sharepoint MIgration.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 Technik/Sharepoint MIgration.md diff --git a/Technik/Sharepoint MIgration.md b/Technik/Sharepoint MIgration.md new file mode 100644 index 0000000..f206314 --- /dev/null +++ b/Technik/Sharepoint MIgration.md @@ -0,0 +1,29 @@ + +## SharePoint Migration Checklist: 25 quick checklists for SharePoint migration + +1. Get the source site structure inventory; it might have a lot of nested subsites. +2. In modern SharePoint, online subsites are not recommended; Microsoft recommends having each site as a separate site collection (here we don’t call it a site collection, we call it a site). +3. Prepare a mapping in Excel for which source site goes to which target modern site. Including each subsite to a modern SharePoint online site. +4. Create an inventory of all lists or libraries on the source site that have more than 5k items because the threshold issue needs special attention post-migration. +5. Create an inventory of all checked-out files in the source site, because during migration you will get an error for this. +6. Create an inventory of all lookup lists in the source. +7. Make sure, while migrating the list, you migrate the parent lookup list first, then the main list. +8. Create an inventory of all workflows in the source and categorise which are designer workflows, Nintex workflows, or any other workflow. +9. Make sure before migration the user completes all running workflow in the source. +10. Create an inventory of all InfoPath forms in the source and come up with a plan to develop an alternate form for those because, after 2023, Microsoft will no longer support the InfoPath form. +11. If you have a custom WSP solution, prepare an alternate plan to re-develop the solution using modern technology like the SPFx framework; custom WSP cannot be migrated to SharePoint Online. +12. Prepare an inventory of all long file paths in the source and create a mapping sheet in Excel that should be the shortened path after the migration. +13. Create an inventory of supported file types in source and target, so that if some files do not get migrated, you will know the reason. +14. There will be a chance that you will not get all users in the target SharePoint online, so create a dedicated migration user that will be mapped for missing users; otherwise, for missing users, logged-in users will be used, which is not recommended. +15. Try to use any third-party tools like ShareGate or Metalogix. +16. Don’t do the content and structure migrations together. +17. First, let’s do the structure migration, then go for the content migration. +18. For content migration, don’t do all site content at once; go list by list; otherwise, error handling will be messed up. +19. Make sure you set the list default experience to modern in the target before migration; it can be done through the tool. +20. Make sure you lock down the source site during migration; otherwise, you need to have a proper delta or incremental migration plan. +21. Prepare a plan for the hub site and the mega menu structure in SharePoint Online and connect each migrated site to the specific hub site. +22. Prepare a training plan for the end-user because the UI will be completely changed after migration. +23. Identify a dedicated site owner for each migrated site, and do not plan more than two site owners for a single site; otherwise, it will be messed up. +24. After each site migration, get confirmation from the responsible site owner and then mark the site migration status as done. +25. After migration, randomly navigate through the site navigation, mainly the Infopath form and user permissions on the site. +26. Last but not least, don’t forget to have a **rollback** plan for any type of uncertainty and a **Plan B** for the migration; these two are very important. \ No newline at end of file