"Correct. 7 days is not enough time to stream >200TB of data, let alone find a place to stream it to. This puts a human being in a crisis position."

Agreed that this is a crisis but it is not impossible.

You can use 'rclone' - running on your own system or hosted elsewhere - to move data between cloud providers.

You don't rely on your own bandwidth - they talk directly to one another:

  rclone gdrive:blah s3:some/bucket/whatever

... and if you don't want to bother even installing rclone, you can run it somewhere it is already installed:

  ssh user@rsync.net rclone gdrive:blah s3:some/bucket/whatever

Which means ... for either the price of (zero) or (minimum rsync.net) you can move that data at (whatever speeds google <--> aws are capable of).

I am, admittedly, hand-waving away the actual configuration of those "remotes" as they are called, which involve your login and/or API keys, etc. - here is an example of what that config might look like:

https://www.rsync.net/resources/howto/rclone.html