SharePoint on-premise migration refers to the process of moving data, content, and settings from a SharePoint on-premise environment to a different environment, such as another on-premise environment, SharePoint Online, or a hybrid environment.

This migration process is necessary when organizations need to upgrade their existing SharePoint environment, move to a different hosting solution, or consolidate multiple on-premise SharePoint farms into a single environment.

Steps Involved in a SharePoint on-premise Migration

The steps involved in a SharePoint on-premise migration include:

1. Planning: Define the scope of the migration, determine the content to be migrated, and plan the migration timeline.
2. Preparation: Check the compatibility of the source and destination environments, set up the destination environment, and test the migration process.
3. Data Migration: Copy the content, data, and settings from the source environment to the destination environment.
4. Validation: Verify that the data has been successfully migrated and that the destination environment is functioning correctly.
5. Post-migration activities: Finalize the migration, update the URLs, and configure the environment as needed.

The process of SharePoint on-premise migration can be complex, especially when migrating a large amount of data, so it’s recommended to use a migration tool or engage a professional migration services provider to ensure a smooth migration process.

The post SharePoint On-Premise Migrations appeared first on MS Technology Talk.

SharePoint Migration is the process of transferring content, data, and configurations from one SharePoint environment to another. The migration process can involve moving from one version of SharePoint to another, from an on-premises environment to the cloud, or from one SharePoint tenant to another. The main goal of SharePoint Migration is to ensure that the content and data remains accessible and usable after the migration.

I am going to write a series of blogs on SharePoint migrations and differences on SharePoint On-Premise and SharePoint online migrations.

Important Migration Factors

There are several factors to consider when planning a SharePoint Migration, including:

• Source and destination environment compatibility: Ensure that the source and destination environments are compatible and can support the content, data, and configurations being migrated.
• Content scope: Determine which content, data, and configurations will be migrated, and which will be excluded.
• Timeline: Establish a timeline for the migration, including planning, preparation, data collection, data migration, testing, and go-live.
• Tools and methods: Choose the right migration tool and method based on the size of the migration and the complexity of the content and data being migrated.
• Security and compliance: Ensure that the migration process complies with security and data protection regulations, and that the migrated content and data remains secure in the destination environment.
• User experience: Consider the impact of the migration on end-users, and plan for training, communication, and support to minimize disruption to the user experience.

The SharePoint Migration process can be complex, so it’s recommended to plan and test the migration thoroughly before executing it. The use of a migration tool can help simplify the process and minimize the risk of data loss or disruption to the user experience.

Different Ways of SharePoint Migrations

There are several different ways to perform SharePoint migrations, depending on the size, complexity, and specific requirements of your migration. Here are some common methods for SharePoint migrations:

Manual Migration:

Manually copying and pasting content and data from one SharePoint environment to another. This method is typically used for small migrations and requires manual configuration of the destination environment.

Third-party Migration Tools:

Using commercial or open-source tools to automate the migration process. These tools can handle complex migrations, manage large amounts of data, and provide detailed reporting and tracking.

SharePoint Migration API:

Using Microsoft’s SharePoint Migration API to automate the migration process. The API provides a set of APIs that can be used to migrate content, data, and configurations from one SharePoint environment to another.

SharePoint Content Deployment:

Using the content deployment feature in SharePoint to move content from one site collection to another. This method is typically used for moving content between site collections within the same SharePoint environment.

SharePoint Backup and Restore:

Using the backup and restore feature in SharePoint to move content, data, and configurations from one environment to another. This method is typically used for moving content, data, and configurations between SharePoint versions or between on-premises and cloud environments. It’s important to choose the right method for your migration based on the size and complexity of your content, data, and configurations, as well as your specific requirements and constraints. It’s also recommended to carefully plan and test your migration process before executing it, to minimize the risk of data loss or disruption to the user experience.

The post SharePoint Migration detail overview appeared first on MS Technology Talk.

## Export Root Certificate
$rootCert = (Get-SPCertificateAuthority).RootCertificate
$rootCert.Export("Cert") | Set-Content "C:\SendingFarmRoot.cer" -Encoding byte
 
## Export Signing Certificate
$stsCert = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate
$stsCert.Export("Cert") | Set-Content "C:\SendingFarmSTS.cer" -Encoding byte
 
## Get the STS Issuer Name
$issuerName = (Get-SPSecurityTokenServiceConfig).NameIdentifier

## Read SendingFarm Signing certificate
$stsCert = Get-PfxCertificate "C:\Install\Certs\SendingFarmSTS.cer"
## Read SendingFarm root certificate
$rootCert = Get-PfxCertificate "C:\Install\Certs\SendingFarmRoot.cer"
# Create a trusted security token issuer
$i = New-SPTrustedSecurityTokenIssuer -Name "SendingFarm" `
                                      -Certificate $stsCert `
                                      -IsTrustBroker:$false `
                                      -RegisteredIssuerName "<SendingFarm IssuerName>"
 
# Configure trust of the token-signing certificate'
# by adding the trust used to sign oAuth tokens'
# to the list of trusted root authorities'
# in ReceivingFarm
New-SPTrustedRootAuthority -Name "SendingFarm" `
                           -Certificate $rootCert

$sprp = Get-AdfsRelyingPartyTrust -Name "<SharePointRP_Name>"
$sprp.IssuanceTransformRules | Out-File "C:\IssuanceTransformRules.txt"

@RuleTemplate = "PassThroughClaims"
@RuleName = "Pass Primary Group SID"
c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/primarygroupsid"]
 => issue(claim = c);
 
@RuleTemplate = "PassThroughClaims"
@RuleName = "Pass Primary SID"
c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid"]
 => issue(claim = c);

Set-AdfsRelyingPartyTrust -TargetName "<SharePointRP_Name>"`
 -IssuanceTransformRulesFile "C:\IssuanceTransformRules.txt"

Add-PSSnapin *SH*
 
$sts = Get-SPTrustedIdentityTokenIssuer
 
$sts.ClaimTypes.Add("http://schemas.microsoft.com/ws/2008/06/identity/claims/primarygroupsid")
$sts.ClaimTypes.Add("http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid")
 
$sts.Update()
 
$map = New-SPClaimTypeMapping `
-IncomingClaimType  "http://schemas.microsoft.com/ws/2008/06/identity/claims/primarygroupsid" `
-IncomingClaimTypeDisplayName  "Primary group SID" -SameAsIncoming
$map2 = New-SPClaimTypeMapping `
-IncomingClaimType "http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid" `
-IncomingClaimTypeDisplayName "Primary SID" -SameAsIncoming
 
Add-SPClaimTypeMapping -Identity $map -TrustedIdentityTokenIssuer $sts
Add-SPClaimTypeMapping -Identity $map2 -TrustedIdentityTokenIssuer $sts