62,031 total views, 7 views today
SharePoint Migration project – sometimes while we do the SharePoint content database migration thru the detach and attach method – we may encounter errors. However, if we open the migrated site still it does open and work. Here, I will explain how we can reduce the possibility of getting errors and some basic tips and tricks in the migration project.
Key-Highlights: Basic tips and tricks in SharePoint migration project
End of this article we will learn the below:
- SharePoint migration project plan
- Best Practices for a Successful SharePoint Migration or Upgrade
- Quick Tips for a Successful SharePoint Migration Plan
- SharePoint server migration steps
- Step by Step Guide to Migrate from SharePoint 2013 to SharePoint 2016
- SharePoint migration steps
- SharePoint migration tool troubleshooting
- SharePoint content database migration checklist
- How to see all running workflow instances in SharePoint 2013.
- Find All InfoPath Form Libraries and lists in SharePoint
- PowerShell script for running Test-SPContentDatabase
- PowerShell script to remove features by ID
- SQL query for the listing setup file information
- PowerShell script to remove the web part by ID
- SQL query to list down web part information
- SQL query to get event receiver information
- PowerShell script to remove event receiver
Descriptions: SharePoint migration project
Even though we get some errors during the database upgrade we may ignore them, as this is a generally common behavior in a migration project.
Even I had also faced a similar kind of issue and figured this out by doing the proper analysis in the source system. One of the key parameters for succeeding in the migration project is proper planning and analyzing the source environment.
Try to get an inventory from your source system about all custom solutions and where (in which sites) these custom features are activated, I am sure from the inventory report you will find there are many features that are not really being used in the source system. So you can clean those unwanted features from the target environment – after running the Test-SPContentDatabase command.
For cleaning up the features you may use the below PowerShell script(available in the below link):
Sample PowerShell script for running Test-SPContentDatabase:
PowerShell script to remove features by ID:
SQL sample for listing setup file information:
PowerShell script to remove setup files by ID:
SQL query to list down web part information:
PowerShell script to remove the web part by ID:
SQL query to get event receiver information:
PowerShell script to remove event receiver:
Above code reference URL:
Basic tips and tricks in migration project
For planning and preparing the checklist for content DB migration – you may refer to the below content:
The basic steps are as below:
- Prepare a detailed inventory of the environment
Clean up the old environment
- Test content
- Prepare destination environment and analyze new environment configurations
Communicate with users
- Start migration
- Read-only mode until migration completes
- Post-migration, third-party tools, and resources
Top 28 Keys in SharePoint Migration: SharePoint content database migration – SharePoint migration steps:
Here based on my personal experience, I have listed out the SharePoint content database migration steps at a high level:
- Create a new SQL server with SQL high availability group and configure SQL listener.
- Create a new SharePoint farm.
- Configure the service application that you had on the previous farm.
- Try to migrate the service application data like Manage metadata service, search service, etc..otherwise create these services and get those service application data thru database migration.
- Create an all-new web application on the target farm as many you had on the previous farm.
- Deploy all custom solutions if you have one, from the previous environment to the new environment.
- Configure the alternate access mapping for all the web applications on the new farm.
- Verify the central administration settings for all pages from CA – by comparing old CA and new CA.
- Verify each web application settings from the new CA – by comparing the old CA and new CA.
- Verify web config files for each web application from the new environment – by comparing the old web.config file and the new web.config file.
- Verify the IIS settings of each web application by comparing old IIS settings.
- Prepare an inventory for all running workflows.
- Good to complete all running workflows.
- Prepare an inventory for all InfoPath forms in source SharePoint.
- Prepare an inventory for all data connections used in the InfoPath forms.
- Plan the migration over the weekend.
- Announce to the users about the downtime of SharePoint.
- While declaring downtime estimate at least 20 percent buffer time for any uncertainty.
- Plan for any other dependent teams like – SQL, networking for their availability.
- Make old farm read-only ( all web applications).
- Take all content database backup from the old database server and restore in new SQL server thru backup restore or detach and attach process.
- Once confident with all these verifications – start the mounting of the content database in the new application.
- During mounting the database we might get some errors some we might ignore, but some errors we might fix.
- After migrating to a new SharePoint environment immediately change the InfoPath data connection URL to the new URL(target SharePoint data connection URL).
- Then open all the InfoPath forms which we have generated from source SharePoint.
- Access the sites – and perform all basic testing – do not forget to test permissions.
- If all is well – finally change the DNS for all the URLs from the new environment – so that it will continue to work with the old same URLs only – in the backend just we need to map the DNS to the new server that we have created.
- Declare go live – I have followed the same steps and it was successful.
- Sometimes, even though we change the data connection correctly from the new SharePoint environment, still we will get the data connection error. Then we need to disable the loopback in the registry. And also we need to verify the layout path in the target SharePoint data connection because the layout path in source and target are different. Example: SharePoint 2013 and SharePoint 2016.
- Need to be calm and cool: If we face some uncertain issue that is a show-stopper for the migration, we should not be tense. Generally, when we do the migration within the given downtime, people get tensed to deal with troubleshooting. So need to relax and work. 🙂
How to get all InfoPath forms and workflows from the SharePoint web application?
Using the below PowerShell script, we can get all InfoPath forms and workflows from the SharePoint web application:
Issues in SharePoint migration
Various types of issues and their descriptions with fixes during running the Test-SPContentDatabase :
- You may ignore the error or exception from the Test-SPContentDatabase command, still, your Mount-SPContentDatabase will work.
- While running the Mount-SPContentDatabase for a certain content database – if you get an exception or up to some extent some errors, you can ignore those and continue in further migration, still, your migrated site will work fine, and in these scenarios, if you see database upgrade status from central admin, we can see upgrade completed with errors status but we can live with this.
Key takeaways from this article: SharePoint Migration project
From this article we have learned the below:
- SharePoint migration project plan.
- Best Practices for a Successful SharePoint Migration or Upgrade.
- Quick Tips for a Successful SharePoint Migration Plan.
- SharePoint server migration steps.
- Step by Step Guide to Migrate from SharePoint 2013 to SharePoint 2016.
- SharePoint migration steps.
- SharePoint migration tool troubleshooting.
- SharePoint content database migration checklist.
- How to see all running workflow instances in SharePoint 2013.
- Find All InfoPath Form Libraries and lists in SharePoint.
- PowerShell script for running Test-SPContentDatabase.
- PowerShell script to remove features by ID.
- SQL query to list down the setup files information.
- PowerShell script to remove the web part by ID.
- SQL query to list down web part information.
- SQL query to get event receiver information.
- PowerShell script to remove the event receiver.
See Also: SharePoint Online PowerShell
You may also like the below SharePoint Online PowerShell tutorials:
- Office 365: Getting started with SharePoint PnP PowerShell – installation
- In 2 steps convert a classic SharePoint page to modern using PnP
- Office 365: Retrieve hub sites and associated sites using PnP Powershell
- Create a modern team site using PnP PowerShell in SharePoint
- In 4 steps access SharePoint online data using postman tool
- SharePoint admin center: Learn SharePoint online administration in an hour – step by step
- SharePoint REST API: GET vs POST vs PUT vs DELETE vs PATCH
- Office 365: Understanding the hub site in SharePoint online
- Post Upgrade Cleanup – Missing Server Side Dependencies