Box to Cross-Cloud Migration

Overview

This flow automates controlled, resumable file migration from Box to OneDrive for Business. On a schedule (or on demand), it lists files in a Box source folder, copies each new file to a OneDrive target root, records every copy in a Dataverse migration map (so the run can resume and never duplicates work), and posts a migrated / skipped / failed summary to Microsoft Teams.

Why it matters: manual cloud migrations are slow and error-prone. A tracked, idempotent, capped flow makes Box to Microsoft 365 migrations reliable, auditable, and safe to re-run.

Ships Off (demo).

Use Case

A team consolidating storage needs Box content migrated to Microsoft 365. The flow runs nightly, migrates a capped batch of files per run, and reports progress to the team's Teams channel. Because every copy is logged to the migration map, an interrupted run simply resumes on the next schedule without re-copying files that already landed.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Box	shared_box	ListFolder GetFileContent
OneDrive for Business	shared_onedriveforbusiness	CreateFile
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
Microsoft Teams	shared_teams

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Deep hierarchy / recursion

This build migrates one folder level. To mirror an entire Box tree, call a child flow per subfolder (or push folder ids onto an Azure Queue and process with a Do-until), reusing the same migration map.

Different target store

Swap the OneDrive CreateFile action for SharePoint CreateFile or Dropbox CreateFile; the rest of the logic is unchanged.

Metadata carry-over

Add Box GetFileMetadata and write extra columns into the map / target file properties.

Permissions mapping

Extend with a step mapping Box collaborators to M365 sharing (Box has no connector collaboration op, so use built-in HTTP).

Throughput

Raise or lower the per-run cap; keep the loop sequential so counters stay accurate.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

take(coalesce(outputs('List_Box_Source_Folder')?['body'], createArray()), variables('varMaxFilesPerRun'))

equals(items('Apply_to_each_Box_Item')?['IsFolder'], false)

equals(length(coalesce(body('Check_Already_Migrated')?['value'], createArray())), 0)

concat(variables('varTargetRoot'), '/', items('Apply_to_each_Box_Item')?['Name'])