If you’re in the market for migrating data from one platform to another, you’re likely finding that there is a host of tools available ranging at various price points. Depending on the features available, SharePoint migration platforms can be as little as $1,999 and into the tens of thousands. In this blog post, we’ll highlight one of these tools, ShareGate Migration.
Note: Opinions and experiences stated in this blog post are our own. We have not been incentivized in any way to review this product.
ShareGate Migration is priced on the lower end at $1,999 for a single user license and is for migrating data only. The ShareGate product line does include an option for a SharePoint Management Tool, but we will not be covering that at this time. Here, we’ll dive into the more common and interesting features available with ShareGate to help summarize this product for you.
When you launch ShareGate Migration you will see a screen similar to that shown below. You can do quite a bit, including:
- Copy Site Objects like Site Collections and sub-sites
- Copy content like Documents, list items and document sets
- Import data from file shares into SharePoint
- Export from SharePoint into file shares
- Script out your actions using PowerShell
One of the options you have is to set the level of performance when migrating your content. This can be helpful to control how much impact the migration will have on your end users that are still working in SharePoint while you are migrating content. Using the slider, you can choose how much or how little of your servers resources should be used for the migration tool. The more you use, the faster ShareGate runs, but your users may see a performance hit while using SharePoint.
Here is a quick look at some of the options you have when migrating a site collection from on-prem to SharePoint Online.
Some options you can set for your migrations are highlighted in the ribbon. You can set options for things like what site templates you want to assign, and what to do with unresolved users.
Here is a look at the screen for mapping site templates. This is useful if you want to choose specific templates to be migrated. For example, there is no site template for a “Blank Site” in SharePoint Online, so you can choose to have any source site that is a “Blank Site Template” to be migrated to a “Team Site” template or whatever you wish.
The tool tries to maintain the information for the Created By and Modified By fields, but sometimes the users no longer exist in the company. Therefore, you have the option of setting those “unresolved users” to a default user of your choice.
Once you have chosen your source and destination, you are presented with a series of screens for setting certain additional options. The Title of your destination site is set to the same as the source, but you can change it, as needed. The URL gives you the choice of the two online options, Sites or Teams, and then what you want the URL to be, again defaulting to the source’s value. Because the destination is SharePoint Online, you can set the values for the storage quota and the Resource Quota.
The other options are self-explanatory and give you a decent amount of control over what you do or do not want to migrate over, including sub sites.
The next screen gives you the option to choose to monitor the migration and decide on a case by case basis what to do when certain conditions are encountered (Interactive Mode), or to set default actions and let the job run without you monitoring it (Silent Mode):
If you choose ‘Silent Mode’ you can then set the default actions for certain conditions, again giving you some flexibility in how and what gets migrated.
One of the other nice features is the ability to perform a ‘Pre-Migration Check.’ This lets you set many of the options we showed above and generate a migration report without actually migrating the content. This can be very useful as a way of seeing what issues you will encounter and gives you a chance to address them before actually migrating. The migration report can be exported to an Excel file and reviewed by the team any time.
When a ‘Pre-Migration Check’ or actual migration is complete, a migration report is created. This tells you any of the warnings and errors that were encountered.
These reports are in an Excel format that you can export and store/share. Below are a couple of screen shots showing some of the fields it exports including the warning/error message:
A helpful feature of the Migration Report is a column, Help Links:
If ShareGate has a helpful article about how to address the error that was thrown, this column will have a link to it so you can click the link and see what their recommendations are for how to address it. An example of this is shown below:
Tip: One thing that can be frustrating using the tool is when you choose to save the Migration report. The default name it gives for the report is very generic. There is no mention of the actual site title that was migrated, so you need to keep track of what you are doing so you can properly name your reports.
Overall, I have been pleased with the tool, especially for the price. It also bears mentioning that the responsiveness of the support team has been very good. I usually get a reply in the same day and they follow up with me until it is resolved.
There are several tools out there to help with your migration and I do feel that ShareGate is well worth looking at. If you have questions or additional information to share, I’d love to hear from you.