Migrate Datto Workplace to SharePoint and OneDrive
If you are consolidating a Datto Workplace tenant into Microsoft 365, you have probably found that the usual migration tools do not have a Datto Workplace connector. This is why, and what to do about it.
Why there is no easy button
Datto Workplace is a file sync and share platform. The mainstream migration tools that move data into SharePoint and OneDrive, ShareGate, BitTitan MigrationWiz and Microsoft's own Migration Manager, do not have a native Datto Workplace source. Mover, which Microsoft acquired, has been retired. In practice that leaves most teams with a manual down-and-up: sync everything to a workstation with the Datto client, then drag it into OneDrive and hope nothing breaks on the way.
That works for a handful of files. It does not work for a real tenant. There is no audit trail, no handling of the names SharePoint rejects, no verification that every file arrived, and no way to prove to a client that the job was done properly.
Why teams are moving anyway
The driver is almost never a deadline. Datto Workplace is not end of life. The driver is cost: an organisation already pays for Microsoft 365, and SharePoint and OneDrive already provide the storage, so a separate file sync and share subscription is a line item worth removing. The migration is a consolidation, and it usually sits with the MSP who owns the Microsoft 365 relationship.
What trips a Datto Workplace migration up
Three things catch nearly every migration into Microsoft 365, whatever tool you use. They are worth understanding before you start.
- The names SharePoint will not accept. Reserved names, illegal characters and a 400-character path limit that a Windows file server never enforced. Files that have worked for years are simply rejected. The file and folder names SharePoint won't accept.
- OneDrive or SharePoint. The same content looks identical once synced, but personal files belong in OneDrive and shared content belongs in a SharePoint site, and getting it wrong is expensive to unpick later. OneDrive or SharePoint? Decide before you migrate.
- Speed is not your bandwidth. Migration throughput is set by the source and destination API rate limits, not your internet connection, so a faster line does not make it finish sooner. Your internet speed is not your migration speed.
The approach that works: directly, over the API
The reliable way to move Datto Workplace into Microsoft 365 is to go API to API, with no sync client and no staging share in the middle. Each file is read from the Datto Workplace API, uploaded to Microsoft Graph, verified, and recorded, one at a time. That means the source is never modified, there is a per-file record of exactly what happened, and the names SharePoint rejects are detected and tidied before they cause a failure rather than after.
Liscaragh Migrate does exactly this
Liscaragh Migrate is purpose-built to move Datto Workplace into SharePoint Online and OneDrive. It runs on your own machine, reads Datto read-only, streams each file straight into your tenant, learns Datto's rate limit as it goes, tidies the names SharePoint rejects and records every one, verifies every file by size and content hash, and writes a client-ready report at the end. It is €499 per tenant, one-time, with all sources included.
Before you start
Whichever way you migrate, a short bit of planning saves a lot of rework. Decide which projects are personal (OneDrive) and which are shared (a SharePoint site) before you copy anything. Run a preview and review the list of names that will be tidied. Be aware that source version history and share permissions do not come across the API, and plan for them if either is a compliance requirement. And estimate the duration from measured throughput, not from your line speed.
Ready to look properly? Read about Liscaragh Migrate, check the FAQ, or ask us a question.