Not every IT project goes exactly as planned. This one taught me that sometimes the most valuable thing you can share isn't a polished success story — it's an honest account of what you tried, what broke, and how you found a better path.
This is the story of migrating a client's SharePoint site data to an OneDrive archived folder — and why the Power Automate automation I planned didn't work the way I expected.
The Background
As part of an IT support collaboration, I was tasked with archiving data from an active SharePoint site for one of our clients. The goal: move the data to a designated OneDrive archived folder, keep it accessible for reference, and set up an automated process so future archival wouldn't require manual effort.
Simple enough on paper.
The Plan
My original approach had two phases:
- Phase 1 — Manual migration: Move existing SharePoint site data to the OneDrive archived folder and verify data integrity
- Phase 2 — Power Automate automation: Build a flow that monitors the SharePoint site and automatically moves files to the archive based on a trigger
Phase 1 went smoothly. Phase 2 is where things got interesting.
What Worked — The Migration
Step 1 — Inventory the SharePoint site
Before moving anything, I documented folder structure, file count, file types, and size. This gave me a baseline to verify against after migration.
Step 2 — Identify what needed archiving
Confirmed with the client which folders were inactive and ready for archival vs still in active use.
Step 3 — Execute the migration in batches
Folder by folder. Easier to verify and catch issues early.
Step 4 — Verify data integrity
Checked file counts and spot-checked file contents after each batch.
Step 5 — Confirm with the client
Client confirmed access to archived files in OneDrive and verified key documents were intact.
✅ Migration completed without issues. All data successfully moved and verified.
What Didn't Work — The Power Automate Automation
Here's where I hit a wall.
My plan: use Power Automate to trigger a flow when files met certain conditions and automatically move them to the OneDrive archive.
The problem — folder-based triggers didn't behave as expected:
- The
When a file is created or modifiedtrigger fires on individual file events, not folder-level conditions - Moving files between SharePoint and OneDrive requires careful handling of permissions and site scopes
- The folder path on the OneDrive side didn't resolve consistently — files going to wrong locations or paths not being recognised
💡 Root cause: Power Automate's OneDrive connector handles paths differently depending on whether you're working with personal OneDrive or SharePoint-connected document libraries. That distinction matters a lot when building cross-boundary flows.
How I Solved It
Rather than forcing an automation that wasn't reliable, I reframed the problem.
The goal wasn't "use Power Automate." The goal was "make future archival not require manual effort each time."
What I did instead:
- Documented a clear archival SOP — step-by-step process with folder naming conventions, verification steps, and sign-off requirements
- Scheduled quarterly archival review — recurring calendar reminder to archive inactive content in one focused session
- Flagged for future automation revisit — documented the technical blocker so it can be picked up when Microsoft updates the connector
What I Learned
| Lesson | Detail |
|---|---|
| Automation isn't always the answer | A reliable manual process beats a brittle automated one |
| Test POC early | A quick concept test would have surfaced the path issue much sooner |
| Document the blocker | Not just the outcome — document why it didn't work |
| POC still has value | The knowledge of what doesn't work is reusable |
Key Takeaways
- Inventory before you migrate — know exactly what you're moving
- Migrate in batches — validate each one before moving on
- Test automation concepts early with a small POC
- Have a manual fallback plan — a clear SOP beats a fragile flow
- Document technical blockers explicitly — saves time next time
Not every project ends with a fully automated solution. Sometimes the most professional outcome is a clean migration, a reliable manual process, and an honest record of what you tried.
Dealt with similar SharePoint or OneDrive migration challenges? I'd love to hear how you approached it — drop a comment below.
Top comments (0)