Hi @SteveMann 

Thanks for posting in our business forum.

Depends on how far you would like to go for the Omada road.

If your needs grow fast, and you may also need more advanced features for the network down the road where Omada might not catch up with your needs, you should consider the RBP. Because you can have two RPBs and use them for different purposes down the road. While OC200 is a proprietary system for Omada Controller.

In short, PBR will be more versatile.

If you are not that geek in playing around with networking, this is just a temporary craze for upgrading the network, then OC200 might be a good choice. Not every year you upgrade your whole network system.

People still use WIFI 5 for regular stuff. Just buy things based on your needs instead of getting into the trap of consumerism.

Think far. Up to you.

 I recall the migration would be slightly different between the software and the hardware. Should not be a serious problem. @Hank21 may take a further look at this.

  @SteveMann 

Currently, with the latest versions of the Controllers you cannot migrate between hardware and software (there is another thread on this).  So if you are running 5.13 on your Pi, you will be re-creating everything on the OC200 should you choose to go that route.  There are also Pi-clones like the Libre Computer boards, which you can get a 2G 4core for $35.  I have an OC200, and some software controllers running in Docker containers on NAS and the above PI clones.  I like the Pi approach because you can do other things with it, like UPS management, PiHole, DDNS, Wireguard (for those of us with ER605v1's) etc.

  @d0ugmac1   @SteveMann 

When performing migration, please note that for controller v5.13.11.41 and above, only the configuration file from a controller with the same first-three-part version number can be used. Currently, software controllers cannot be migrated with hardware controllers due to their different first-three-part version numbers. However, our related department will release firmware with the same first-three-part version number for hardware controllers in the future, allowing for migration.

  @SteveMann 

Everything.  Just like if the universe had just been born and you found yourself standing in the black void holding an OC200.  But wait, there's light...

Now, if you have backups from older versions of your software controller, from say 5.9 or even 5.12, your could temporarily spin up the older software controller version, restore the backup to it, then export the site(s) one by one from the old controller version using the Controller->Settings->Migration option to local files. Then downgrade the OC200 to the same major.minor version, and then restore each site, one by one.  Finally upgrade the OC200 back to the current version.

TPlink really needs to fix this silliness.  Or, failing that, makes the backup exportable in XML so we can fix it ourselves.

  @SteveMann 

So you were using a version below 5.13 then on both software and oc200?