Last modified: 23 November 2023
Q. How do I install the Migration Model on my Teams team?
A. You just create a normal Teams team and SMART Migration then creates the standard SharePoint Lists, Libraries, Site Columns and Content-Types needed. (Standard PnP provisioning template is applied.)
Q. Do I need to install any special App on my Team?
A. No, everything works with standard “Out-Of-The-Box” Teams/SharePoint functionality.
Q. What about permissions for the individual content owner groups? (They may not se each others file names)
A. Each content owner group can have their own SharePoint “Migration Model” Library with unique set of permissions.
Q. How can validation be trusted when the same tool is performing both the migration and the validation?
A. The validation is a completely different program, approach and content crawl. The migration job reporting is based on the information Microsoft is returning plus any program exception thrown during transfer where the validation is based on a new content crawl and local comparison to the stored in the reports.
Q. On a scale issue…how will it be able to handle millions of files?
A. MigrationFlow can handle as many millions of documents as you like. And the “Migration Job” creation along with metadata manipulation etc. can be fully automated using all the full feature set of SMART Migration, making a ton of PowerShell and Excel completely obsolete.
Yes, it will take some time to create millions of small proxy files.
But in any project scale the benefits of “Migration Modeling” are huge and outweighs the model creation time greatly.