Skip to main content
Question

Veeam Data Cloud Exit Strategie?

  • March 6, 2026
  • 5 comments
  • 32 views

Hartmut
Forum|alt.badge.img

Hi,

we are planning to use the Veeam Data Cloud for Salesforce Backup. We need to keep backups for 2 years. What, if we decide to switch the backup-partner. For example Salesforce native backup? We cancle our subscription. Fair-Use-Policy will delete the backups after 30 days, correct? What options do we have, to keep  the backups as long as our requirements are?

 

The same question would be, if we decide to use veeam backup for m365 in the data cloud. Here we would have onedrive files, with a retention time of 2-10 years. 

 

We do not plan to quit anything, but we need a valid exit strategie if we decide to use a cloud product. 

5 comments

Chris.Childerhose
Forum|alt.badge.img+21

I believe you can work with Veeam to get your data moved for access but cannot say for sure.  Best to check directly with them.


kciolek
Forum|alt.badge.img+1
  • Experienced User
  • March 6, 2026

Yes - contact Veeam they have an exit strategy for use cases like this. I was on a call the other day with an Engineer discussing this with the customer.


HangTen416
Forum|alt.badge.img+11
  • Influencer
  • March 6, 2026

I believe the exit strategy (at least for VDC for M365) is that they will migrate your data to your own Azure tenant since they only support Azure to Azure migrations. But as Ken and Chris said above, check with your Veeam rep.


Jason Orchard-ingram micro
Forum|alt.badge.img+1

Yes that correct, Veeam has a section the help centre on how to remove a tenant from Veeam data could for saleforce

 https://helpcenter.veeam.com/docs/vdc/userguide/sf_tenants_remove.html 


MicoolPaul
Forum|alt.badge.img+23

Hi,

Veeam Data Cloud Solution Engineer for M365 here, the exit strategy is that after cancellation of service you’ve got 30 days to request your data. Your data will be transferred in the most economic way to you available at the time of cancellation (who knows what options Microsoft Azure will permit in 5 years time for example). The data transferred is kept in the VB365 format, why? Because this way the data is still compressed (cost savings on storage at rest) and can be leveraged for both search & recovery purposes vs a raw data dump.

 

To access this data you would use Veeam Backup for Microsoft 365 Community Edition. This is a free edition of our software that whilst it has restrictions on new backups (maximum of 10 users), it doesn’t have any search or restoration restrictions.

 

You would maintain the storage and tooling for as long as you required to meet retention commitments. As you wouldn’t be actively backing up any data your VB365 server could remain powered off except for when you needed to patch or perform search/recoveries to cost optimise further. Once you no longer need to retain the historical data, you’d decommission your VB365 server(s), delete your storage, and be done!

For more information on this, check out the Veeam Data Cloud Service Agreement which has a section on data transfers during exit.