Migration jobs have always moved data into a bucket. On the Business plan they now go the other way too: pick a bucket as the source, a server as the destination, and an optional key prefix to limit what's copied.

It rides the same machinery as every other job — incremental re-runs, streamed transfers so file size isn't a limit, atomic writes that never leave a half-written file, and host-key pinning on the destination.

Bucket → bucket is deliberately not offered here: that's a backup job, which compares ETags and does it better.