Create Plan/Approach for Java Application Migration -- 2

Hello. I am a freelance database/network engineer who has been asked by a client of mine to move their old java application to new java editions. This is a 21 page application that was developed 7-8 years ago. It is for all purposes a stand alone web application in which users enter data from 6-7 warehouses in the country and it generates reports/pricing. I need to provide a plan for my upgrade and, if approved, will work with you to do so. Presently I ONLY need help creating a comprehensive approach/plan/steps to submit. If approved, I will get the work and will work with you to migrate the application. Present ---> Moving To Java EE 1.4 --->Java EE 7 Apache Struts 1.3 ---> Apache Struts 2.3 Hibernate 3.0 ---> Hibernate 4.3 Apache Ant 1.3 ---> Apache Ant 1.9 XDoclet ---> Unacceptable. Application to be refactored to remove this technology JBoss Application Server 4.0 ---> JBoss Application Server 7.3 Database is Microsoft SQL and I will be upgrading to 2014 from 2008. Presently the JBoss Application Server 4.0 has been bundled into the application (tool) ecosystem, along with patches to support SOAP and EJB 3. The application build scripts are designed to output a standalone package consisting of the JBoss server with the application (tool) installed in it. This package can then be run as a self-contained server. According to the system admin, who is not Java savy, tight integration of an application server with the application itself, the sophisticated Ant build scripts, and the use of XDoclet for code generation and configuration generation might present a unique challenge in modernizing this application.