SharePoint Online Migration Planning Traps and Tricks - Part 2
Sharing Our Expertise

Our consultants solve challenging business problems and love sharing their knowledge. Tap into our insights and put them to work for you.

Back to Blogs >>

Published by , on Tuesday, September 12, 2017

This is the second of a two-part blog series on SharePoint Online migration planning and “traps and tricks.”  Part 1 focused on some of the major planning items that need to be addressed (

Part 2 will focus on some of the “traps and tricks” that we need to take into consideration as part of a SharePoint Online/Office 365 migration. At PSC Group, we have run across many of these issues in various migrations.

Here are the topics we’ll focus on in this post:

  • Custom Script Setting
  • SharePoint List and Library New Experience
  • Office 365 Portal Office Software Install
  • Browser Wars
  • What versions of MS Office are we supporting?


Custom Script Setting

One of the items that can cause unexpected results is the “Custom Script Setting” that is controlled in the SharePoint Admin Center:

 SharePoint, Custom Script Setting, Administration, Migration

The default setting is: “Prevent users from running custom scripts,” both on personal and self-service created sites. This can have significant impact and restrict several items that we might need to migrate from our legacy SharePoint sites. Here is just a sampling of items that will be rendered inoperable with the default setting:

  • SharePoint Designer Workflows will not function
  • Save Site as Template is no longer available
  • Save document library as template is no longer available
  • A number of the web part galleries that we have been accustomed to are no longer available
  • The default setting can also negatively impact the function of some of our migration tools.

Here is a link that provides more details on the Custom Script setting: 

Adjusting the Custom Script Setting requires the following settings:

Requires either Global Administrator or SharePoint Administrator to adjust

Go to Admin Center then SharePoint Admin 

Once in SharePoint Admin, go to Settings and scroll down to ‘Custom Script‘, then change the setting to ’Allow users to run custom script” both on personal sites and self-service created sites’:


After the setting is saved, allow 24 hours for this change to occur in the portal.


SharePoint List and Library New Experience

The default setting is to use the “New Experience.”

SharePoint, Document Library, Administration, Migration

It is a fundamentally different user experience than what users will be used to when coming from legacy sites with classic lists and libraries. It is possible to reset them back to classic experience, but that is only temporary as Microsoft will soon be removing that option.  

As a result, we need to plan for end user orientation to the new experience during our migration. Here is a link that provides additional details on the new user experience for lists and libraries:


Office 365 Portal Office Software Install

Depending on the Office 365 licenses enabled, one of the options that is provided by default is the option to install Office 2016:

SharePoint, Custom Script Setting, Administration, Migration

Do we want this option available to our end users?  If IT has deployed, managed and/or imaged desktops, it may be advisable to control Office 2016 install through IT and turn this option OFF.  

Here’s how to address this option:

Requires Global Administrator

Go to Admin Center

 SharePoint, Administration Center, Administration, Migration

Go to Software Download Settings

SharePoint, Install Office, Administration, Migration 

Turn off 2016 desktop and mobile apps

SharePoint, Software Download Settings, Administration, Migration 


Wait approx. five minutes and this option will be turned off in the system. 

Here’s a link that provides additional details: 


Browser Wars

Depending on the browser(s) we might be supporting in our environment (I.E., Chrome, Edge, etc.) our user experience is liable to be quite different for each of our users, even when viewing- the same site, lists, or libraries. 

  • For example, people who use the “File Explorer” view will need to have IE available as this view is not supported in either Edge or Chrome.  
  • Additionally, if we have libraries set to “Open in Application” instead of the default Web App on documents, we need to confirm that each of our browser options accept this setting. They may not.  
  • Also, if we have folks who are exporting data from SharePoint lists to Excel spreadsheets with the “Export to Excel” option, this only works with IE and Edge, but not Chrome.

Here’s a couple of links with some references information: 


What versions of MS Office are we supporting?

We may need to review the versions of MS Office that are presently deployed to our users and update if needed. Here are some items to consider:

  • MS Office 2013 is the minimum version that supports full functionality with Office 365 apps.
  • Be aware of Connected Services in MS Office with Office 365 Apps. Make sure they are properly configured for our users.


Here are some other tips: 

Many thanks to various contributors for content and to my teammates at PSC Group.


Categories: SharePoint,SharePoint Online,SharePoint Workflow,Office 365

Original Post:

Recommended For You
Many obscure issues can occur that can cause the Dynamics 365 App for Outlook to disconnect and disappear, but thankfully there are a couple of s...
View More ...
Office 365 can improve and modernize your workplace faster and enable you to focus on strategy and adoption rather than implementation.
View More ...
Join Mark Roden for "Using VSTS to automate build and deployment tasks for SharePoint Framework webparts" at SharePoint Fest Chicago on Dec 7.
View More ...
What do email-enabled apps look like in the modern (cloud) workplace? In this multi-part series, I try to answer that very question– beginning ...
View More ...