While producing and consuming pure RESTful endpoints is possible, you may consider renovating your solution landscape to product and consume OData as part of a mid to long term project to reduce or eliminate some technical debt.
By service enabling your systems, you can create an abstraction layer between the model/controllers and the views. This recipe allows for more robust applications while make the solutions less fragile with regards to maintenance and evolutions.
OData is a good mid to long term choice for service enabling solutions. OData has many advantages over purr RESTful endpoints with many verbs to perform the basic Create, Read, Update, Delete (CRUD) operations. There are also some nifty enhancements in version 4 to support more efficient batch processing (less chatty apps), annotations to support smart controls, etc.
There are some solutions available for you to add OData CRUD operations to databases as a use case for a legacy two tier application. Checkout the WSO2 Enterprise Integrator for off the shelf, or Apache Olingo if you want to roll your own.
I have refactored many legacy landscapes as a first step to major renovations towards more modern, standardized recipes. The process to service enable forces you to look at solutions at a process level and to extract the services/micro services that are executing. This will give you a better picture of what the solution does, what roles depend on the solution and how the solution compares to other solutions in the enterprise to identify candidates for absorption into other systems.