SharePoint 2013: SharePoint Migration Assesment Tool – Part II!

In my previous blog post about the SharePoint Migration Assessment Tool (SMAT) I did a short introduction about the tool. In this new blog post I will show you how to use SMAT:

  • First thing you have to do is just download SMAT from the following URL. SMAT download is a zip file that contains the following elements:
    • A set of assemblies used by SMAT application to do its work.
    • Two configuration files: a JSON (ScanDef.json) file where you can configure different settings in regards of how SMAT makes the scan of your farm (for instance, you can enable the scanning of big lists in this file); and a CSV file (SkipSiteList.csv) where you can specify any sites in the farm you don’t want to be scanned by SMAT).
  • To use SMAT, I recommend you to create a folder where store all the files and folders generated by SMAT. Once you have created that folder, open the command line tool in the server and browse SMAT navigation. Once you are in the SMAT path, simply run the tool using the following syntax

  SMAT.exe –o <SMAT_Logs_Folder> –t <Number_Parallel_Threads>

  • Once you hit enter, SMAT starts working and gathering all the information of your farm including any possible problems and issues you could have in a migration scenario where you want to move to SharePoint Online.



  • As you can see in the screenshots, I have executed SMAT with the -o option and -t options. -o option allows to specify the path where SMAT Logs are going to be saved; -t option allows to specify the number of parallel threads to be used by SMAT execution. As a result of running SMAT in my SharePoint Test Farm I found some issues in regards of unsupported web templates, Secure Store Service App Ids and Web Application Policies.
  • Additionally, SMAT execution ends asking the domain of my SharePoint Online tenant for a migration scenario.
  • As a result of executing SMAT, we will get a log file with all the scanning operations done by SMAT and also a set of reports with all the potential issues we will have to deal with in a migration to SharePoint Online. The details of all the issues that can be reported by SMAT can be found in the following support article:



  • The following is an example of report generated by SMAT where you can find any site in your farm created with a site template not available in SharePoint Online. The information in regards of not supported site templates is stored I the informe UnsupportedWebTemplate-detail.csv file.


And that’s all!!!

Un pensamiento en “SharePoint 2013: SharePoint Migration Assesment Tool – Part II!

  1. Pingback: SharePoint & Office 365: Resumen de posts (XV)! | Pasión por la tecnología...

Deja una respuesta

Introduce tus datos o haz clic en un icono para iniciar sesión:

Logo de

Estás comentando usando tu cuenta de Salir /  Cambiar )

Imagen de Twitter

Estás comentando usando tu cuenta de Twitter. Salir /  Cambiar )

Foto de Facebook

Estás comentando usando tu cuenta de Facebook. Salir /  Cambiar )

Conectando a %s