Hello, in my personal experience (we use both versions here in my company, enterprise for design and proof of concept and community for some definitive solutions) I think depends more on the specific components that you used in the commercial version. From our own experience, what we use most in enterprise are form grid, jdbc access lists and CRUD components. None of these three (among many others) are available in the community version. What did we do? Import the BPMN diagram to the community platform and migrate each of the forms and other elements from their JSON definitions and for the missing components, adapt "generic" javascript components for specific functionalities in the forms and use some DB "tricks" for the lists. Coding will always be necessary.
Now if you do not have possibility of this, and your group of users is reduced, you can use an on-demand version at reasonable costs. We also use it: you save effort in server configuration, but you lose some "power" since you can not access the DB with a heavy client (in our case, for example, we use postgresQL a lot for its geographic components).
