If you migrated your own server into a bucket on Pro, restoring that data back onto the server used to require an upgrade — discovered at the moment you needed it.

That gate is gone, and the reason is structural rather than generous. A restore cannot choose where it writes: it puts data back exactly where the migration took it from, and there is no destination to name. If the migration was allowed, the way back is allowed.

Still Business, and unchanged: naming a server as a destination in the first place — server-to-server and bucket-to-server migrations, and connecting a server as a drive. Those are the cases where you point at an arbitrary machine.

See Plans & billing.