Works well when used for the tasks it is designed for.
|
|
|
|
|
|
|
Sharegate is not an enterprise level tool and does not have or do.
|
Consolidated always up-to-date and actionable reporting. You have a consistent and consolidated overview of where the migration project stands. The reporting output can be used directly for ReMigration orRetryMigration . Effectively eliminating all CSV and Excel sheets. Notice that you can secretively ReMigrate files to fix metadata issues etc. even thought initially migrated successfully.The consolidated always up-to-date actionable reporting includes:
|
|
You have to develop your own bespoke migration automation tool yourself for each project in PowerShell and then use Sharegate as a callable function (CMDLET) in your code. In other word a complete application that a part from the Sharegate CMDLET functionality must include:
|
|
Migration where one or more data sources drive the migration rather than the source storage location – In other words: a list of files, optionally also versions, with or without metadata |
|
Reporting is a manual task where you must “dive into” hundreds or thousands of text or raw Excel files. In other words you must create your own reporting solution. |
|
Everything is hardcoded and tied to a single configuration. In many cases a migration task or data integration task consists of multiple steps that interact and take parameters. In Sharegate you have to start coding complex PowerShell to do any of that thereby totally compromising the simplicity of the Sharegate UI experience |
|
All tasks are hand crafted and 100% hand held. Any automation must be custom programmed in PowerShell with no exception, compromising the simplicity of the Sharegate UI experience |
|
Nothing can be dynamic, parameterized or calculated in any way. |
|
No support for querying anything but file extension and modified date in a SharePoint Library |
|
No functionality what so ever. The lack of any functionality is consistent with the fact that the environment is 100% static, has no automation, calculations or dynamic capabilities at all. |
|
Combine files from FileShares with metadata from SQLServer and create document library items with version history |
|
Use a data source (SQL, CSV, Excel, SP List) to dynamically control file source and destination + metadata |
|
Break up large Libraries and FileShares and distribute the files across many SharePoint destinations with dynamic metadata |
|
No actions are visually previewed. You have to try and se what happens by “diving into” the text based logs sheets raw sheets it in Excel. |
|
Then Sharegate environment is 100% static, manual and hardcoded and offers no way to do composite or parameterized jobs in any form. To accomplish any kind of dynamic or automated behaviour you must code your own solution in PowerShell, totally compromising the simplicity of the Sharegate UI experience |
|
There is no way to do any form of notification for job progress tracking. or job results |
|
The reporting and the way it works internally is simply not suited for high volume processing (>1 million files) or distributing content to many locations/sites (>500 locations/sites) |
|
Any task can only run while logged into the UI of Sharegate. In other words there is no way to have jobs running unless logged in to the machine having Sharegate installed and having the Sharegate running. |
Explanation to the above quote: While the other car makers were having highly specialized people for each task, all working on a single car at a time (essentially custom building each one, analogously to using PowerShell scripts over and over again), Ford were using tested and automated assembly line. He did not invent the wheel every time. He just used the methods that were already tested and proven and did not have to employ an army of specialists. See? So using PowerShell and Sharegate as Cmdlet (analogue to a screwdriver) is by far inefficient and error prone. And more over this constellation totally compromises the simple Sharegate UI experience.
Last modified:
18 October 2022
Post your comment on this topic.