Skip to main content
Solved

Migrating VBR on Windows (13.0.x) to Veeam Software Appliance 13.1.x: has anyone done it?

  • Nov 10, 2026 4:03 PM UTC
  • 7 comments
  • 81 views

Hi everyone,

I’m planning to migrate our existing Veeam Backup & Replication server from Windows to the Veeam Software Appliance and would like to hear from anyone who has been through this.

Current environment

  • VBR on Windows, version 13.0.12067

Target

  • Veeam Software Appliance, version 13.1.2.57

What I found so far

My questions

  1. Has anyone migrated from VBR on Windows to the Software Appliance with 13.1.x? What path did you take (deploy 13.0.x then upgrade, or something else)?
  2. Is my understanding correct that restoring a 13.0.x configuration backup onto a 13.1.x appliance is not supported?
  3. Did you run into any issues, for example with the configuration restore, proxies, repositories, credentials, or jobs after the migration?
  4. Any tips or things to check before starting?

Thanks in advance for any feedback!

Best answer by YassineN

Thank you sincerely for your replies and for the time you devoted to my request.
Based on your feedback, I have decided to wait for the release of version 13.2 before proceeding.

This will allow me to benefit from the latest improvements and avoid steps that might become unnecessary after the update.

View original

7 comments

CMF
Forum|alt.badge.img+8
  • Veeam Legend
  • Nov 10, 2026 4:07 PM UTC

Hi ​@YassineN there is a path to migrate under 13.0. to an 13.0 appliance via the support. 

In this case you have to migrate first and then update to the latest version in a second step. 

But i have not done that migration yet.

Regards

Chalid


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

I have done over 30 migrations.  I have my own runbook but it is based on KB4800.  Use the PowerShell from that article to stop/disable services.

Furthermore, you need to use 13.0.x, as 13.1 will not work and will block you until 13.2 is released.  Before the migration, also open a support case to get a migration key from them, which you need during the migration (configuration backup restore).


tm67
Forum|alt.badge.img+4
  • Veeam Legend
  • Nov 10, 2026 4:46 PM UTC

If you are in no hurry, I suggest waiting for VBR version 13.2 to arrive. There is not yet a release date but hopefully it will be released in the next few weeks/months. 

There will be official support for the migration, and Veeam is probably improving the migration process. 

So, you need to upgrade your Windows VBR to 13.2 as soon as its released and then deploy a VSA 13.2 and start the migration. 

If you need to do it now, follow the official guide: https://www.veeam.com/kb4800


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

If you are in no hurry, I suggest waiting for VBR version 13.2 to arrive. There is not yet a release date but hopefully it will be released in the next few weeks/months. 

There will be official support for the migration, and Veeam is probably improving the migration process. 

So, you need to upgrade your Windows VBR to 13.2 as soon as its released and then deploy a VSA 13.2 and start the migration. 

If you need to do it now, follow the official guide: https://www.veeam.com/kb4800

13.2 definitely looks to have better migration steps for sure and would be my choice at this point.  I did all mine with the 13.0.2 release because I started in April.  LOL

Hopefully a new wizard for migration will come too with 13.2. 🫣


lucasmagnum
Forum|alt.badge.img+1
  • Experienced User
  • Nov 10, 2026 7:56 PM UTC

​@YassineN  hi!! 🚀

I followed the procedure described in the official KB4800 article: https://www.veeam.com/kb4800.

I encountered a few issues along the way, so I eventually decided to wait for the next release, hoping it would include further improvements to the migration process.

I encourage you to give it a try and share your experience here. If you run into any issues, feel free to post them, and we can work together to help you troubleshoot them.


  • Author
  • Comes here often
  • Answer
  • Nov 16, 2026 11:38 AM UTC

Thank you sincerely for your replies and for the time you devoted to my request.
Based on your feedback, I have decided to wait for the release of version 13.2 before proceeding.

This will allow me to benefit from the latest improvements and avoid steps that might become unnecessary after the update.


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

Thank you sincerely for your replies and for the time you devoted to my request.
Based on your feedback, I have decided to wait for the release of version 13.2 before proceeding.

This will allow me to benefit from the latest improvements and avoid steps that might become unnecessary after the update.

Not a problem and good luck with 13.2 when it releases.