SharePoint online interview question - How do you migrate running Out-of-Box (OOTB) workflow using Migration tool Sharegate, Quest Conent Matrix, Ave point.

Both the Quest Content Matrix and Sharegate migration tools can migrate Out-of-Box (OOTB) SP2013 workflows and SharePoint Designer workflows to SharePoint Online.

Quest Content Matrix

Quest Content Matrix does not have the option to migrate running workflows. This is because migrating running workflows can be complex and error-prone. Quest Content Matrix is designed to be a simple and reliable migration tool, and it is not optimized for migrating running workflows.

To migrate OOTB SP2013 workflows and SharePoint Designer workflows using Quest Content Matrix, follow these steps:

1. Create a new migration job and select the "Migrate List Metadata" option.
2. Select the SharePoint list that contains the workflows.
3. Select the "Workflows" option in the "Metadata to Migrate" section.
4. Click the "Next" button to continue.
5. Review the migration summary and click the "Migrate" button to start the migration process.

Quest Content Matrix will copy all of the selected metadata, including workflows, to the destination SharePoint list.

Sharegate

To migrate OOTB SP2013 workflows and SharePoint Designer workflows using Sharegate, follow these steps:

1. Create a new migration job and select the "Migrate SharePoint Workflows" option.
2. Select the SharePoint site that contains the workflows.
3. Click the "Scan" button to scan the site for workflows.
4. Select the workflows that you want to migrate.
5. Click the "Migrate" button to start the migration process.

Sharegate will copy all of the selected workflows to the destination SharePoint site.

It is important to note that migrating workflows can increase the migration time. Therefore, it is important to assess your needs and determine whether or not you need to migrate workflows.

Additional :

there are a few special steps that you need to take to migrate running workflows for both Quest Content Matrix and Sharegate:

Quest Content Matrix

1. Before you start the migration, you need to stop all of the running workflows.
2. After the migration is complete, you need to start the workflows manually.

Sharegate

1. Before you start the migration, you need to take a snapshot of the running workflows.
2. After the migration is complete, you need to restore the snapshot of the running workflows.

Here are the detailed steps for each step:

Quest Content Matrix

1. Go to the SharePoint 2013 site where the running workflows are located.
2. Click Site Actions > Manage site features.
3. Deactivate the Workflows feature.
4. Start the migration process.
5. After the migration is complete, go to the SharePoint Online site where the workflows were migrated.
6. Click Site Actions > Manage site features.
7. Activate the Workflows feature.
8. Manually start the workflows.

Sharegate

1. Open Sharegate.
2. Connect to the SharePoint 2013 site where the running workflows are located.
3. Navigate to the list or library that contains the workflows.
4. Select the workflows that you want to migrate.
5. Click the Migrate button.
6. In the Migrate dialog box, select the Migrate Running Workflows option.
7. Click the Migrate button.
8. Sharegate will take a snapshot of the running workflows and then start the migration process.
9. After the migration is complete, Sharegate will restore the snapshot of the running workflows.

Additional: 

If you need to migrate running workflows, you can use a third-party workflow tool such as Sharegate or AvePoint Migration Accelerator. These tools provide specialized features for migrating running workflows.

Alternatively, you can manually migrate running workflows by following the steps below:

1. Stop all of the running workflows on the source site.
2. Migrate the workflows to the target site.
3. Manually start the workflows on the target site.

Note: It is important to test the workflows thoroughly after the migration is complete to make sure that they are working properly.

Teachers on

SharePoint migration To SharePoint online. How to Migrate the Alerts from Sp2013 to SharePoint online ?

 

Migrating SharePoint alerts from an on-premises environment to SharePoint Online involves several steps. Here's a general procedure you can follow:

Assess the existing alerts: Review the alerts configured in your on-premises SharePoint environment and identify the scope and nature of the alerts. Take note of the types of alerts, the users subscribed to them, and the associated lists, libraries, or sites.

Create a migration plan: Based on the assessment, create a migration plan that outlines the steps, timeline, and resources required for the migration. Consider factors such as the number of alerts, complexity, and any dependencies.

Set up SharePoint Online: Configure and set up your SharePoint Online environment. Ensure that the necessary permissions, site collections, and sites are created to accommodate the migrated alerts.

Prepare the target environment: Create the lists, libraries, or sites in SharePoint Online that will host the migrated alerts. Ensure that the necessary columns, views, and settings are configured to match the source environment.

Export the alerts: Use SharePoint migration tools or custom scripts to export the alert configurations from the on-premises environment. The specific method may vary depending on the tools and techniques you choose. This step involves extracting the alert settings, including the subscribed users, alert types, and associated lists or libraries.

Transform the exported data: Depending on the export format, you may need to transform the exported alert data to match the format expected by SharePoint Online. This step involves mapping and adjusting any differences in alert configuration between the source and target environments.

Import the alerts: Use SharePoint Online migration or management tools to import the transformed alert data into SharePoint Online. Ensure that the alert configurations are correctly applied to the target lists, libraries, or sites.

Verify and test the alerts: Once the alerts are imported, verify their functionality by testing various scenarios. Subscribe to the alerts using different user accounts and ensure that the notifications are delivered as expected.

Communicate the migration: Inform the users about the migration and any changes or actions they need to take. Provide instructions on how to re-subscribe to the alerts if necessary.

Decommission the on-premises alerts: Once you have confirmed the successful migration and tested the alerts in the SharePoint Online environment, you can decommission the on-premises alerts and disable the associated configurations.

Remember, this procedure provides a general guideline, and the specific steps may vary based on your organization's requirements, tooling, and migration approach. It is recommended to thoroughly plan and test the migration process before executing it in a production environment

Deva

SharePoint online Modern page, how to hide the New page Title in carousel layout ?

SharePoint Modern Page cusotmization.

Pre-requisites.

You need to add the script editor, web part and you need to enable customization true for the site collection using PowerShell script.

Please use the below CSS:

<style type="text/css">

[data-automation-id="newsItemTitle"] {

  Display: none! Important;

}

</style>

Before applying the CSS.

After applying the CSS.

 Thanks

Enjoy.

SharePoint Online List - How to get basic properties uisng Powershell

 

1. function RetrieveList(){  
2.     $list = Get-SPOList "PnPList"  
3.     Write-Host "Title : " $list.Title  
4.     Write-Host "Description : " $list.Description  
5.     Write-Host "BaseTemplate ID : " $list.BaseTemplate  
6.     Write-Host "Created Date : " $list.Created  
7.     Write-Host "List ID : " $list.Id  
8.     Write-Host "ImageUrl : " $list.ImageUrl  
9.     Write-Host "ItemCount : " $list.ItemCount  
10.     Write-Host "OnQuickLaunch : " $list.OnQuickLaunch  
11.       
12. }  
13. RetrieveList #Retrieves list using list name 

How to enable verionsioning in SharePoint site through powershell script.

 Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue

$site = Get-SPSite($siteURL)
foreach($web in $site.AllWebs) {
    Write-Host "Inspecting " $web.Title
    foreach ($list in $web.Lists) {
        if($list.BaseType -eq "DocumentLibrary")

 # if($list.BaseType -eq "GenericList")  for List calenar task.

      {
            Write-Host "Versioning enabled: " $list.EnableVersioning
            Write-Host "MinorVersioning Enabled: " $list.EnableMinorVersions
            Write-Host "EnableModeration: " $list.EnableModeration
            Write-Host "Major Versions: " $list.MajorVersionLimit
            Write-Host "Minor Versions: " $list.MajorWithMinorVersionsLimit
            $list.EnableVersioning = $true
            $list.EnableMinorVersions = $true
            $list.MajorVersionLimit = 2
            $list.MajorWithMinorVersionsLimit = 5
            $list.Update()
            Write-Host $list.Title " is updated with MajorVersionLimit 2 and MajorwithMinorVersionsLimit = 5"
        }
    }
}