Migrate SharePoint 2016 To SharePoint 2019 Environment Using Content Database Migration

Softree Technology Pvt. Ltd
MIGRATE SHAREPOINT 2016 TO SHAREPOINT 2019
ENVIRONMENT USING CONTENT DATABASE
MIGRATION

SharePoint 2019 supports content database
migration from the SharePoint 2016
environment into the SharePoint 2019
environment.

Step – 1
First take a content database backup from
SP 2016. Please follow the steps below.
1.(a) Go to the central admin and click on
“Manage Content Databases”.

1.(b) Select the web application for which you need the content database
backup.

1.(c) Copy the Content Database name. Then select the Content
Database.

1.(d) Open the SQL server management studio. Expand database.
Select the database. Right click on it. Select the Tasks > Back Up.

1.(e) It will navigate to the following window. Select the below location.

1.(f) Remove this path and add the path where you want to keep your back up
(.bak) file.

1.(g) Now click on OK button and wait till the backup completes successfully.

1.(h) Once complete you can see your .bak file in the location which you have set above.

Step-2
Create a new web application on SP 2019
environment. To create a new web application
navigate to central admin and clicks on “Manage
web application”

And now click on “New” ribbon button

And now a modal dialog will appear, Please provide all
necessary information.

Now please wait till the processing to be finished.

Finally, you can see your new web application has been successfully
created on your end.

After creating the web application follow these steps as mentioned below.
2.(a) Select Application Management then Select the Manage Content Database
under the Databases.

2.(b) Select the web application you have created.

2.(c) Then click on the Content Database name (copy the name of the database to
use it later on), it will take you to the Manage Content Database Settings page.
Under the Database Status select the “Offline” option from the dropdown list.

Check the Check Mark in “Remove content
database” check box.

A prompt will come, select OK on that. Now the content database is removed
from the web application.
2.(d) To detach the Content Database from SQL Server Management Studio
please follow the steps: Connect the SQL Server Management Studio =>
Expand the Database. => Select the content database name that you have
copied previously=>Right click on SQL => Tasks= > Detach

Check the check box in the Drop and click Ok.

Step – 3 Restore the 2016 database.
3.(a) Right Click on Database and select Restore.

3.(b) Now select “Device” radio button and
browse the path where you have kept SP2016
backup file.

3.(c) Select the file from the folder.

3.(d) Now you can a similar window as shown
below. Please verify the things and then click on
“Ok” button.

Please wait for it successfully restore the database
on your SP2019 SQL server environment.

Step – 4
Now the time has come to associate and
upgrade this content database to SP2019 newly
created web application. Please use this below
command to mount the database to new web
application.
4.(a) Open the SharePoint 2019 Management Shell as “Run as
Administrator”.
Mount-SPContentDatabase “<DatabaseName>” -DatabaseServer
“<Db server name>” –WebApplication “<webapplication url>”

4.(b) Once the command executes successfully, then you will get message as
shown below.

This command will upgrade the database and attach this content database to the web
application.
If required, upgrade the service applications.
4.(c) If you get any errors while executing the above command then
please refer the log file to get more details. Please click on « Upgrade
and Migration » and then click on « Check Upgrade Status » from
Central Administration.

Get in Touch with Us
www.softreetechnology.com

Migrate SharePoint 2016 To SharePoint 2019 Environment Using Content Database Migration

More Related Content

What's hot

Similar to Migrate SharePoint 2016 To SharePoint 2019 Environment Using Content Database Migration

Recently uploaded

Migrate SharePoint 2016 To SharePoint 2019 Environment Using Content Database Migration