We're migrating from Google Drive to SharePoint, can we do this with a flow?
A flow for file migration can work, but realise it is a one-time project, not ongoing automation. Tool choice depends on volume: up to 100GB n8n or Make does fine, beyond that a dedicated migration tool pays off.
Try this first
- 1Inventory first: how many GB, how many files, what folder structures, what permissions, what shared links. Without that you'll patch retroactively.
- 2Small volume (up to 50GB): n8n self-host or Make scenario that per file: download Drive, upload SharePoint, copy permissions, log result. Test on a sub-folder first.
- 3Permissions don't translate 1-to-1: Drive's 'anyone with link' differs from SharePoint's 'specific share'. Document the mapping before you start.
- 4Run migration in batches per department. User comms: new links, old links still working for 30 days, deadline.
- 5After migration: a compare flow that diffs file counts and sample hashes between source and target. No blind trust on 'seemed to work'.
When to bring us in
Got terabytes or complex permissions, a tool like ShareGate or Movebot pays off. We can pick and plan.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.