Tag: Migration

After building the strategy and planning for it, next step is Data Migration from SharePoint 2013 to Office 365. We are going to look into native import / data migration service provided in Office 365, you need to be an Office 365 Administrator or at least have someone to help with initial set up.

Before we start actual migration we need to do some set up. Login to Office 365 and go to menu Users –> Migration.

Once there scroll to see Onboarding and migration guidance, click on SharePoint and new window will open.

This will guide to Onboard you and create migration jobs, I am just capturing relevant steps here

Step 1 is just some text about SharePoint online

Step 2 is very important as you need to define what kind of deployment you will have, in our case we will select on premise to cloud.

Step 3 explains PowerShell option we have selected On-premise to cloud migration

Step 4 is to prepare for PowerShell, first it download and install SharePoint Online Management Shell, download it from here SharePoint Online Management Shell.

Second is to create Azure Storage account if you don’t have already one.

Go to https://portal.azure.com and create a storage account

Also get your location and details

Step 5 is creation of Content package, we need to use classic Export Web command in SharePoint onpremise server to create an export package

Export-SPWeb [-Identity] -Path [-ItemUrl ] [-NoFileCompression ]

Step 6 is coversion of package so that it can be imported

ConvertTo-SPOMigrationTargetedPackage -SourceFilesPath $sourceFiles -SourcePackagePath $sourcePackage -OutputPackagePath $targetPackage -TargetWebUrl $targetWeb -TargetDocumentLibraryPath $targetDocLib -Credentials $creds

To read more about ConvetTo-SPOMigrationTargetedPackage you can read here Click here

Step 7 is creating Azure Containers and uploading content package

$al = Set-SPOMigrationPackageAzureSource -SourceFilesPath $sourceFiles -SourcePackagePath $targetPackage -AzureQueueName $azureQueueName -AccountName $azureAccountName -AccountKey $azureAccountKey

$al|$al|fl

Step 8 is submitting a migration job, sample code is here

Submit-SPOMigrationJob -TargetWebUrl $targetWeb -MigrationPackageAzureLocations $al -Credentials $creds

Note that some parameters variables were created in earlier steps and needs to be used here

Step 9 is to check Migration Job Status which can be done Azure account storage queue

Sample source code

# Example file share packaging, conversion, upload and job submission script
# Queue is only container specified as new containers are automatically generated
# All container URIs get populated into $al variable output from Set-SPOMigrationPackageAzureSource cmdlet
$creds = (Get-Credential admin@contoso.com)
$sourceFiles = ‘\\fileshare\users\charles’
$sourcePackage = ‘C:\migration\CharlesDocumentsPackage_source’
$targetPackage = ‘C:\migration\CharlesDocumentsPackage_target’
$targetWeb = ‘https://contoso-my.sharepoint.com/personal/charles_contoso_com’
$targetDocLib = ‘Documents’
$azureAccountName = ‘contosomigration’
$azureAccountKey = ‘Insert Azure Account Key string Here’
$azureQueueName = ‘migrationqueue’
# Create new package from file share without security (faster)
New-SPOMigrationPackage -SourceFilesPath $sourceFiles -OutputPackagePath $sourcePackage
# Convert package to a targeted one by looking up data in target site collection
ConvertTo-SPOMigrationTargetedPackage -SourceFilesPath $sourceFiles -SourcePackagePath $sourcePackage -OutputPackagePath $targetPackage -TargetWebUrl $targetWeb -TargetDocumentLibraryPath $targetDocLib -Credentials $creds
# Create azure containers and upload package into them, finally snapshotting all files
$al = Set-SPOMigrationPackageAzureSource -SourceFilesPath $sourceFiles -SourcePackagePath $targetPackage -AzureQueueName $azureQueueName -AccountName $azureAccountName -AccountKey $azureAccountKey
# This displays the return Azure location
$al|$al|Format-List
# Submit package data to site collection to create new migration job
Submit-SPOMigrationJob -TargetWebUrl $targetWeb -MigrationPackageAzureLocations $al -Credentials $creds

So this completes all steps for data migration. Next we will look into Hybrid scenarios which will come in next post

To check earlier two posts click below

SharePoint 2013 migration to Office 365 step by step – Planning #SharePoint #Office365

SharePoint 2013 migration to Office 365 step by step – Strategy #SharePoint #Office365

This post is written as step 1 that is planning.

When SharePoint 2010 was launched Microsoft wanted to move everyone to cloud and they were trying to convince everybody that cloud is the future but they soon realized everything cannot be moved to cloud due to local data regulations and customers apprehensions about data security. Now Hybrid architecture is promoted quite a lot which makes sense and also more practical.

In this post I will try to outline how to prepare for Migration from SharePoint 2010 / 2013 to Office 365. We also discuss Hybrid architecture later in other posts.

We will discuss different aspects of migration, in this post we will understand SMAT tool provided by Microsoft and also excel template created by me to analyze customizations.

Microsoft has introduced a SharePoint Migration assessment Tool called SMAT, you can download it from here SMAT.

The zip file downloaded needs to be run on a SharePoint server, file contains below files, some of them are important to understand

File SiteSkipList.csv is important as you can mention which sites needs to be skipped during assessment, like you can mention MySite to be skipped as in general they don’t have any customizations and many sites under it.

SMAT Read me have more instructions but to run it you need run the exe file via command prompt

SMAT.exe -0 D:\Outputlog

where D:\Outputlog is the destination where logs will be created, do not out the log destination as SMAT folder as it tries to clean up and will end up deleting files.

While its running you can see what it will be scanning, below is a screenshot while it runs. You can see it’s analyzing FullTrustSolutions, LargeExcelFiles, Wokflows etc.

Since we know that no server side code is allowed in Office365 it’s important to have this kind of analysis to understand what things needs to reimplemented.

Once the assessment tool finished it will generate reports for each topic in detail and list down all site details, issues about it like below

Each report has very detailed information, if you want to understand meaning of each report you can refer to this link SMAT Report Definitions. Although I think names are self-explanatory.

These reports will help you understand what issues you will face if you need to migrate but for planning I have created excel template where you can list all customizations and also strategize around it. This is needed because I believe that no one understands your farm better.

You can download the excel template from here, each column has some explaination.There are two sheets. First sheet is for listing all customizations and categorized them. Second sheet is to write down solution details of each category. This way you can have common solutions for each category and it can define how your developers should approach re-implementation

SharePoint 2013 to Office 365 Migration Template

So the migration assessment tool and excel template will help you analyze your farm in great detail and plan for the migration.

Tech Tip : Are you in search of a remote working technology? Access your online private workspace on any device(PC/android/iOS) with remotely accessible citrix vdi from CloudDesktopOnline with enterprise Add-Ons like Hosted SharePoint and Exchange. If you`re a MS Azure user looking for managed azure services visit Apps4Rent.

You can read the part 2 here SharePoint 2013 migration to Office 365 step by step – Strategy #SharePoint #Office365