Backup migration from SSH (Legacy) to JetBackup Storage - and others

We were just looking to switch from SSH (Legacy) to JetBackup Storage and there is no migration path for old backups - which would force us to keep paying our old provider until there are enough backups in JetBackup Storage if we want to do that.

It would make sense to have a migration module on the servers that can read from any existing backup through that engine, and then push the backup to the new destination through the new engine.

There are probably ways to optimize that by deduping on the file or block level. And filtering for certain accounts and limiting to certain time periods.