In the source farm, determine the content database used by the Bonzai Intranet site collection. This can be done in Central Administration or PowerShell.

Central Administration

1. Navigate to Application Management, View all site collections.
2. Select the web application and site collection.
3. In the table on the right the Database Name row will contain the database name.

PowerShell

1. Log in to one of the SharePoint servers in the farm as a farm administrator.
2. Open an elevated SharePoint Management Shell.
3. Run the following Powershell. (<url> is the URL of the Bonzai Intranet site collection)

$site = Get-SPSite -Identity <url>

$site.ContentDatabase

For example:

$site = Get-SPSite -Identity https://bankgroup.bonzai-intranet.com

$site.ContentDatabase

Getting the database name in PowerShell

In this example, the database name is BONZAIDEMO_Content_Bankgroup

How you achieve this depends on your requirements, environment, and available tools (e.g. backup/restore, detach/reattach, 3rd party migration, copy database wizard, etc).

The details for moving a SQL Server database between instances is out of scope for this guide.

To summarize, you have to copy the content database from the source environment to the destination environment and make it available in the destination SQL Server.

At the end of this step the source content database containing Bonzai Intranet should be online in the destination SQL Server instance.

Usually, the production and non-production environments do not share the same service accounts. Once the database is online in SQL Server it is necessary to grant permissions for the destination farm service accounts to the content database.

Grant database role permissions to the attached content database for the following accounts:

• Farm service account (i.e. the account running the SharePoint Timer Service) - db_owner
• Farm administrator who attachs the database to SharePoint (i.e. the account you are logged into the SharePoint server with) - db_owner
• Web application pool account - SPDataAccess

Open the destination instance in SQL Server Management Studio. And perform the following steps:

1. Navigate to Security > Logins.
2. Select one of the accounts listed above, right click, click Properties.
3. Navigate to the User Mapping page.
4. Check the Map check box for the attached content database and select the db_owner database role permission (SPDataAccess for the web application pool account).
5. Click OK.

Repeat for the other accounts.

Attaching the database can only be performed in PowerShell. In the destination farm:

1. Log in to one of the SharePoint servers in the farm as a farm administrator.
2. Open an elevated SharePoint Management Shell
3. Run the following Powershell, where:

• <databasename> is the name of the attached database
• <BonzaiWebApplication> is the GUID, Name, URL, or SPWebApplication object for the destination web application

Mount-SPContentDatabase -Name <databasename> -WebApplication <BonzaiWebApplication>

For example:

Mount-SPContentDatabase -Name "BONZAIDEMO_Content_Bankgroup" -WebApplication "BankGroup"

The output contains many blocking errors and non-blocking errors and warnings which must be resolved.

Watch for any errors related to Bonzai Intranet solutions (e.g. missing solutions) and resolve before proceeding.

Attaching the migrated content database

Once the database is attached it appears in the list of databases for the Web Application. This can be verified in either Central Administration or PowerShell.

Verify in Central Administration

Navigate to Application Management > Manage content databases and select the web application.

Verifying in PowerShell

1. Log in to one of the SharePoint servers in the farm as a farm administrator.
2. Open an elevated SharePoint Management Shell
3. Run the following in Powershell, where:

• <BonzaiWebApplication> is the GUID, Name, URL, or SPWebApplication object for the web application where the database was just attached

$wa = Get-SPWebApplication -Identity <BonzaiWebApplication>

$wa.ContentDatabases

For example:

$wa = Get-SPWebApplication -Identity "BankGroup"

$wa.ContentDatabases

Verifying the migrated content database in PowerShell

Continue to the post-migration steps to configure Bonzai Intranet in the destination environment.