They are architecturally both Catalyst 9300 hardware. The MS390 has a different BIOS' and some cosmetic differences(lacks front USB for instance). With the -M it is identical to the c9300 outside of some different stickers showing the Cloud-ID(Meraki Serial).   Software wise, if the switches are on the save version, say CS15.21.1. They both will be running the same underlaying operating system IOS-XE and container code. We do restrict the -M from installing deprecated firmware. The best example of this is you can have a MS390 running deprecated MS11 firmware, which the c9300-M can't run.   But you are correct, they are architecturally the same. With the shipping firmware on the -M being the most stable firmware with all the lessons learned baked in from the MS390. ... View more

You can migrate the switch today, just remove the NM-2Y module and then complete the migration process. I've fixed the documentation bug showing 2Y support today.   We plan on fully supporting the 2Y module on the 9300-M by our launch date for the C9300-NM-2Y-M in Jan/Feb. With Early access coming sooner (Dec/Jan). Stay tuned! ... View more

Meraki did a great service by splitting the firmware trains between classic and catalyst switches. The two firmware, MS16(traditional) and CS16(catalyst) are the same train but specific to the hardware platform. A great number of bugs revolved around mixing of these two code-trains. Most of the issues with the MS390 have been resolved around MS15 firmware and with CS16 it's only gotten better.    With the MS390 firmware stabilized, we're seeing alot of adoption of CS16 in the field, it's quickly becoming a GA candidate. If you haven't upgraded yet, i highly recommend so. The -M hardware should ship with CS16, so we won't have to worry about any factory-firmware issues that impacted the MS390.   The new c9300-M hardware is a whole new software stack based on the newer firmware, and have been getting very positive reviews from the field already on EFT.    This is the Meraki way, we learn, refine and improve perpetually. Wrangling the Catalyst into dashboard was a challenge, not without some pitfalls, but with the dedicated firmware and hard work from engineering... we're starting to reap the benefits.    Thanks to all that have stuck with us on the platform, and for those that are still waiting on the -M.... we look forward to proving our resolve.    _Nico ... View more

No license is currently required until it goes GA(Nov). You'll then have 30 days to migrate your license to Meraki if you want to keep it in managed mode. The license migration is easy, follow the guide below. Here's a helpful guide on the migration process including license handling https://meraki.cisco.com/wp-content/uploads/2023/05/quick-start-migrating-switching-DNA-management-mode-to-meraki-management-mode.pdf Best of luck! ... View more

So to clarify, only the conversion process is "beta" because the conversion/migration process will return the switch to factory defaults. Once the switch is in Meraki mode, it is fully GA. It runs the same firmware as the MS390 which is currently GA.  The conversion process is improving and in the future, you'll be able to convert from unmanaged, to monitored to fully managed without loosing configuration. ... View more