REAL TIME: All files migrated successfully. The SharePoint metadata and URL issues. The failures.
Consolidated Reporting: All jobs to all destinations from all sources
The repository database gives you a comprehensive reporting solution that enables you to track and fix any issue incrementally and proactively without loosing the global overview. You can focus only on the core root issues and view meaningful processing feedback as the migration jobs progresses. So, there are no CSV or Excel files floating around.
Actionable: Feed the report output into incremental cherry-picking jobs.
Either the same job definition as used originally or modified to fix issues with MangedMetadata tags recognition, invalid users , content-types, unresolved lookups, invalid choices or bad URLs etc.
Cherry-picking for ReMigrate or RetryMigrate
based on any criteria (simple no-code UI) or wrong Content-Type, Manged Metadata tag or just revised rule set for what is right. You name it!
Incremental/sync in every possible way.
Based on any incapsulated and parameterized CAML filter (simple no-code UI) mixed with , date modified, file existence, file nonexistence etc.
|Database views||Use as source in a DataETL Step or For-Each Step|
|All files that have been processed. Also the simulated migrations executed in “Test-mode”.|
|All metadata validation warnings such as unknown users, Managed Metadata, Content-Type etc.|
| All SharePoint user processing including results for mapping and the unfiltered results from the
API call to
|Key functionality||Know what happened to each and every file and take action|
||Data about all jobs to all destinations, from all sources. All data is automatically consolidated and always up-to-date in SQL database. No “dead” useless CSV or Excel files floating around.|
||Feed the report output directly into incremental cherry-picking jobs. While constantly keeping the consolidated always up-to-date overview|
||Report only the latest instance of any given file across all migration sessions (or any filter). So for example a file that failed yesterday but completed successfully today will be reported as completed|
||Add reporting to any migration setup as an integrated Step|
||Add searchable context specific information such as Customer Id, Account Number to each reporting output row based on variables derived from a For-Each loop|
||Another job, Excel, CSV, SharePoint List, SQLServer, ODBC , PowerBI|
When handling many files it becomes a major task determining to what level the file migration or replication was successful and especially to track and correct the issues that are inevitable to happen.
In an ideal world or a demo setup the reporting and tracking task is easy and often marginalized. But the real world is very different and no one will accept that “maybe some files didn’t make it and, well metadata is wrong to some extent”
|There are many pitfalls when migrating files to/between SharePoint Document Libraries|
|Microsoft 365: The file migration process is a multi phases procedure.
|Non existing users|
| Invalid mapping or missing
|Badly formatted DateTime or bad time zone calculation|
|Non numeric value for numeric columns|
|Non-existing or inconsistently provisioned Site/Document Library|