How to Switch List experience view in SharePoint Online

Introduction

In this article, you will learn, how to change the list or library experience in SharePoint Online.

New experience
Classic experience

New Experience set as default experience in SharePoint online, Site owner can easily switch with Classic experience.

How to Change the List Experience

Navigate to SharePoint Online site
Navigate to SharePoint Site List or Library for which you want to change the experience or view.

New Experience (Click List Settings)

In General Settings -> Select Advance Settings

In the List experience section, select the experience you want to use for the list

Classic Experience

Summary: Thus, in this article, you have seen how to change the list or library experience in SharePoint Online.

SharePoint Online Manual Migration

I worked with a couple of SharePoint Migration Project i.e. On-Premises to On-Premises & On-Premises to Online using

Manual Approach ( Content DB Attach)

ShareGate Tool

ShareGate Tool based PowerShell scripts.

Manual Approach

In this article, I am going to articulate approach and scenario, where we used SharePoint Online Manual Migration approach.

Scenario: -

Migrate small size of content i.e. List & Library ~ 4-5 GB to SharePoint Online.

Why I chose manual approach?

Tool is really required if we have >25GB of content and another factor like:-

changes in Application Architecture (Restructure the Content DB).
Changes in Information Architecture or Schema.
Version History needs to maintain.
Metadata need to maintain i.e. Created By, Created, Modified and Modified
Easy to get Pre & Post Migration reports & Verification.
Incremental is just configuration away etc.
Content Size is huge, Easy to schedule a day-night jobs.

Note: - Migration Tool use Content Migration API, which need cloud storage account. It also come up with extra cost along with Tool.

IF all above factors are not so important, we can easily use manual migration instead of tools.

How Manual Migration Done

Save Site as Template is not really possible using below factors:-

· Publishing Site Template.

· Publishing Feature activated in the site.

· Sometime Managed Metadata Column and weightage of list column

2. Save List as Template

This is one of easiest way to backup and restore the content. Even it support lookup column,

If List backup and restoration configured in proper order i.e. First Parent then Child list.

Browse the List -> List Settings -> Save as Template. It will create and store the .STP file in the catalog library.

Another approach to create the STP file is PowerShell.

Both way, we can create the .STP file using Content or without Content.

Copy Data via Access:-

In some case, you have to use Access to move the content to Cloud.

Select Open with Access

Specify the Path with filename or List Name, which create the access database (.accdb)

Two option available:-

Link to Data on the SharePoint Site
Export a copy of data

Once you download access database, Open the Database and select the list and Select SharePoint under Move Data Ribbon group. It prompts for destination list.

Once you complete above activity, you content will reside in the SharePoint Online List. It successfully support lookup column also.

Limitation: - If you have lots of view, It doesn’t maintain the sequence of column. Need to do again manually or using PowerShell script.

Copy Data via Excel:-

Use Export to excel, It export all list data into excel.

Below is the example of exports data.

Navigate to SharePoint Online List and click Quick Edit – It allow to copy paste the data from excel to list.

After copy the content, Its look like, At the one time, you can copy paste 500+ items also.

Click on Done and Job Finished.

Library Files:-

File Explorer View or Drag & Drop. But it doesn’t allow more than 100 files at the same time.

Access allows you to copy list over to the cloud. But you can't use it for Libraries.
To copy files, use "Open with Explorer"

You still can copy these files by dragging and dropping directly in the document library:

When Manual Approach doesn’t suit (i.e. .STP file)

It doesn’t support two level below i.e. Moss2007 or SP2010 to O365. It is possible from SP2013 to O365.

How to set read-only

Once you transferred the data from source to destination, you must make sure that source data will not change. Manual Migration is tedious job and do the incremental is more tedious.

This can be achieved using Break permission inheritance and change to Read. Prioritize the list & library which are not updated frequently also help to avoid incremental for all.

Note:- Version History, All minor version should be published as major or discard.

Summary

If you have customization, you need to think, Can we convert to JS-Framework using REST or Search API, List form level customization using JS-Link.

If left behind customization, up to 4-5 GB content migration, we achieved in 8-12 hours jobs to avoid the incremental approach. To analyze and prepare the scripts and order of list took 2 weeks of time.

Know Your SharePoint Multi Server FARM Network Structure

This article describes the SharePoint Multi Server communication within the SharePoint farm.

Physical architecture relates to capacity planning and sizing depends on the multiple factors. I took a very simple example and try to explain, Is SharePoint Farm follow the Network Layer Architecture or Not.

Physical Network Layer Architecture (Normal Flow)

How to know the actual Server Communication within the SharePoint Farm

Browse the Central Administration

Central Administration -> System Settings -> Manage Server in FARM

Microsoft SharePoint Foundation Web Application Service is responsible to communicate with Database Server.

IF Microsoft SharePoint Foundation Web Application Service activated on Web Server, Then Web Server by-pass the network layer architecture and directly communicate with Database Server.

As depict above farm information, Now SharePoint FARM Network layer architecture look like

How WSP deploy to Multi Server FARM

Microsoft SharePoint Foundation Web Application Service is responsible to move the WSP solution to another server, wherever Microsoft SharePoint Foundation Web Application Service activated. Service automatically deploy the solution in other servers.

Handle Multiple Domain during SharePoint Migration

This blog describes the problem statement and resolution i.e. How to handle multi-domain issue during SharePoint Migration.

This is quite interesting & common scenario, which we face in almost all migration project i.e. On-Premises to On-Premises or On- Premises to Online.

SharePoint Migration project easily enters into escalation mode due to multi domain users after entire application migration.

Somehow application team tries to convince the business user to adapt or change the User Name with a NEW domain. This is something no business user ready to accept.

Scenario illustrated in below diagram:-

Problem Statement:-

Before Migration, Project was using Domain OLD.com and application URL like https://sharepoint.old.com where the user also have their login id like <<Domian>>\<<USerName>> old\user etc.

Business wants to migrate the application to different domain i.e. On Premises or Online.

New Domain like NEW.com and application URL like https://sharepoint.new.com

Users, who are part of the NEW domain can easily recognize by control and start using the application but some users are still part of the old domain.

As our new migrated application hosted into new domain so old domain user doesn’t recognize into new domain application.

Below are the ways to resolve the issue:-

Option 1:-

If both domains have TWO WAY TRUST. No configuration required. the user can be added as <<OLDDomain>>\<UserID>; instead of only user name.

Option 2:-

If both domains have ONE WAY TRUST. Only people picker control configuration need to do using PowerShell. It will help control and application to recognize the user.

Option 3:-

If both domains don't have TRUST process. User Profile Synchronization needs to perform. It will help control and application to recognize the user.

Ref :- https://collab365.community/sharepoint-2013-people-picker-problem-with-2-way-trusted-domains/

Estimate The Time Frame To Migrate Content To SharePoint Online

This article focuses on the actual content migration effort which is separate from planning, redesign, fixes, deployment, and configuration.

It's a very common question during the analysis phase of a SharePoint migration project. - How much time a "Tool or Migration API" will take to migrate the actual content from the source to the destination?

I found a couple proposals where people simply say 5GB per hour but it's not really practical.

It depends on multiple factors. I am not going to dive deep into how the below factors impact this. Just take the estimation based on content.

Network bandwidth
Type of content & file format i.e. List Item, Document, and Video etc.
Check In / out files & Versions
User base, Custom Permission & Groups
Workflow (OOTB, Design. Custom, Nintex)
Customization
Asp.Net Forms, InfoPath Forms
Threshold limit (Items, Lookup, Unique permission)

High-level content migration estimation view

List Item size is very low and associates with the large metadata, Workflows, Events etc.

Library item size quite big (files size like MBs) associated with versioning, large metadata, workflow, events etc.
File Share – No metadata, No Versioning
Video – Big size files.

How Migration API (Most of the tools use) works