Hi Sodby, going from Classic 2023 to Kinetic 2025 just a couple of months back. (On prem here). We did a “back to base” campaign that was basically “try doing your job fully on the browser and let us know when you are missing something”, and this was in Kinetic 2023. We ported most things into 2023 and let the normal upgrade process upgrade the Kinetic screens.
FYI if they didn’t tell us they needed thing then it’s not in 2025.2. Apart from Fulfilment workbench we are 100% Browser based now.
Out of curiosity, why stick with the classic FWB?
From a business point of view we need to fulfill orders that can range from sticking one part in a jiffy bag riiight upto 80ft containers. In classic you can group by X,Y and Z then click on the group header and click Select then go through the motions of assigning. In Kinetic you need to select every-line in the group. This makes manual selection really slow (think 200+ line orders) and we send out lots of deliveries. Epicor have improved it a bit but it’s not there yet. Also, as FFW is essentially a datagrid on steroids and Kinetics Datagrids are horribly slow the entire experience is very sub par to classic.
Sorry, need some [/rant] tags 
@shobdy If you’re not wedded to ripping off the band aid all at once, why not start migrating the apps to Kinetic now? Then you can make a BAQ that looks at menu maintenance to see what’s still assigned to Classic.
Couple that with using Activity Tracking Detail filtered to classic menu’s, and you can quickly target the heaviest used UI’s first.
Don’t forget about configurators if you use them… That’s holding us back from switching Quote and Order Entry to Kinetic at the moment. We’ve got to rebuild them from scratch in Kinetic.
Also test opening and adding attachments.
Call logs and change logs have broken sorting in 2025.2.13.
Having each department test their full process is key. You’ll find a lot of little issues where Kinetic lost functionality from Classic (even in 2025.2, “working as designed” ) that may need work arounds or updatable dashboards to get lost efficiency back. Your users will also need training.
Our users liked having the smart-client open in Classic, and the browser open in Kinetic. This way they could test and train themselves side by side. If you’re a one man band for Epicor at your company, make sure to leave lots of time for training your supervisors and users. That needs to be done before the switch, and is really hard if everyone switches at the same time. We did department by department, over a few months to attempt to limit the chaos.
(edit - added)
We also moved the majority of our Setup and Reports menu folders to Kinetic first, since those aren’t used as frequently, and usually there’s a bit more time to figure things out vs the regular apps in the General Operations menu path.
Good luck!
They need to improve multiple line selection indeed. Highlight the rows then some kind of “Select rows” command.
Have you tried the “new” automated fulfillment? You can create fulfillment rules that automate much of what you do manually with the fulfillment workbench. This eliminates the manual stop of running fulfillmen workbench on a daily (or hourly for some companies) to find what can be shipped. The Automated fulfillment can take care of the 90% of the work.
This! We have run across some BPMs that were effected. There are some processes that call different methods in Kinetic vs Classic. We have some dual BPMs floating around while we are transitioning.
Same for us. Should of noted which ones were for Classic so we could clean up after the classic sunset. 
You can determine the client, browser vs Classic with a condition on bpms so that will help you if you have differences between classic and browser.
Thanks Tim, I have looked into it but will be doing again with a bit more time now we have an updated 2023->2025.2 Kinetic system. We have also started experimenting with getting the AI to manage this for us two so interested in what works better, even better if, kind of thing.