We are live on 2024.1 with everyone except MES in the browser from day one. We came from a 100% Classic 2022.2 and made the switch to Kinetic and the Browser then. I would not say .2 releases are more stable, they will have newer features and a few things fixed that Epicor can’t fix in the smaller patches but this is not Server 2008 & 2008R2.
What we did here for the transition was to get an instance of 2024.1 (I would do .2 if I were you since 2025.1 is not yet GA) and went through it to make sure everything worked, reports, dashboards, screen customs/configurators converted to Kinetic, etc. We had a very, very small team that did that initial validation that it was ready for department heads to see and introduce to their teams.
Once it got to that point we brought those heads in and walked them through the broad stroke changes, we did not re-teach how to enter an order/quote/etc, we focused on having them understand how to work with the new UI since entering an order is essentially the same, just with a new UI.
We had a deadline for when we were doing the cutover and they were made aware of that and that they would need to do department specific testing (to make sure nothing had been missed) and training/familiarization with their actual teams. From there is was just a matter of dealing with the odd thing that came up.
Its been 4 months since we went live like this and while there are definitely still a few annoying things with Kinetic we are, as I said, 100% browser for non-MES, about 50% Browser for MES and growing. It is no doubt a big shift from what people are used to, particularly if you are not using Kinetic screens yet but once people get over the ‘WTF moment’ of Kinetic it is simply a matter of relearning the UI, if you are already on Kinetic for a bulk of your screens then moving to the browser is even easier.