This article is for you if you want to back up the whole site collection with ShortPoint content (Theme, Generators, Connections and Integration Settings) and restore it as a new site collection or you want to migrate the site collection between different farms or web applications (under same farm).

Prerequisites

1. You have a SharePoint On-premise installation 
2. You have a valid ShortPoint license activated at both source and destination farm (Incase you are doing migration to same farm, you will need license of one farm only)
3. You have a site collection with ShortPoint theme configured
4. You are the central administrator of your farm 
5. You have the URL of new site collection where you want to restore the site

Step 1: Open SharePoint Management Shell

Go to your farm server where you have central administrator. Open SharePoint 2013 Management  Shell / SharePoint 2016 Management Shell;

Step 2: Backup

Run following command;

Backup-SPSite <SITE URL you want to backup> -Path <Path of the file with bak entension example d:\site.bak>

Example: 

Above step will backup the site collection at the given path with bak extension with content. There are few parameters to above command which can be found here.

Step 3: Restore

Run following command to restore the backup;

Restore-SPSite <New Site collection URL> -Path <Path of bak file generated in step 2 above> -DatabaseServer <The SQL server name of content database> -DatabaseName <The name of SQL database where you would want to restore the site collection>

Example: 

That's it!

Above command will create a new site collection with the content and ShorPoint theme configuration.

Notes:

•  Not specifying the database might sometime result in following error (if there are NO unused database available). To avoid this error, you should specify the databaseServer and DatabaseName while restoring in step 3 above.

Error => Restore-SPSite : The operation that you are attempting to perform cannot be completed successfully.  No content databases in the web application were available to store your site collection.  The

existing content databases may have reached the maximum number of site collections, or be set to read-only, or be offline, or may already contain a copy of this site collection.  Create another

content database for the Web application and then try the operation again.

• If the destination site collection (where you want to restore) already exist, you should use -force parameter to force the restore and overwrite the database.