This is a very exciting acquisition for Microsoft who purchased data migration company mover.io back in October of 2019. You can read all about it at https://blogs.microsoft.com/blog/2019/10/21/microsoft-acquires-mover-to-simplify-and-speed-file-migration-to-microsoft-365/.
We all know what a nightmare it can be to move data into SharePoint or OneDrive. I am pleased to say that mover.io goes a long way to easing this that pain.
Consider this post more of a “hey check out this cool technology” than a comprehensive tutorial on all things mover.io. However, I did documented my first experience and it was a very pleasant experience indeed.
Things this post does not consider:-
- Advice for cleaning up the source data
- Permissions migration
- Agent considerations (firewalls, permission etc.)
For that you can lean on the mover.io knowledge-base found here – https://mover.io/guides/
As always, I hope you found this post useful and informative. Happy migrating!
1. Sign up for a new mover.io account at https://app.mover.io/account/create
2. Choose your data source. I chose the agent as I wanted to migrate from an on-premise file share
3. I needed to install the agent and chose to install it as a service. There are lots of options to suit your needs.
4. The agent.msi will download. Complete the install.
5. Once the agent is installed. Open the settings and select copy key.
6. Copy the key and paste that back into the agent connector screen which should still be open in the browser.
7. You will now be able to pick your folders in the source data source.
8. Select your destination connector. Select authorize new connector.
9. I selected Office 365 as I wanted to upload the file share data to a private site document library (common).
10. As you would expect, mover.io will create an enterprise application in your Azure Active Directory. In order for it to be able to interact with the target SharePoint Online environment and Azure Active Directory, you will need to grant permissions.
Another fact of life with SharePoint migrations is file name and path limitations. Mover.io will highlight any issues but they will still need manual remediation. This solution is not a “silver bullet”.
11. There are two places you can consent to grant the permissions mentioned above. The first is easily in the wizard.
The second is, once the Enterprise Application is created, inside the enterprise application itself.
12. With that done you will now see your destination SharePoint location listed and you can select continue migration
13. Now its a simple case of selecting the source path you identified in step 7 above and the destination SharePoint document library. Step one is to scan for any file and folder limitations (such as file path depth).
Note: Don’t be discouraged by the user interface. In our example we want to migrate everything from the C:\File_Data folder to the target SharePoint library but it refers to “1 user”. This is because the tool allows seeding of personal home drives, data into pre-provisioned OneDrive MySite locations (how cool is that)!
14. Then you start the migration
Note: The status is updated from never to “Scan Pre-Checks” by completing step 13 above.
15. You are asked for scheduling (very cool!)
16. The data is then transferred from the file share to SharePoint.
Note: I use a script to create as realistic data as I can. A mix of small and large files and the transfer was complete before I finished the article. So I felt the performance was excellent.
17. And within the SharePoint document library.