Unlike the previous steps, the following tasks do not have to be completed in any particular order.
Instead, it is advised that you carry them out before making new enhancements to your application, to ensure that any issues relating to the migration are not complicated by changes in functionality.

1. While it is not necessary to remove your older theme for your freshly migrated app to work, your older theme no longer serves any functional purpose.
   If you haven't created any custom templates in your older theme (which you'd want to copy over), or if you don't need to keep the older theme for reference, consider deleting the older theme.

2. Ensure that the list items for Navigation Menu are correct, and that the Current For attributes are properly set.
   Your tabs will be converted into a list format. If the current for attributes are not set correctly, the navigation links will not be selected when you navigate to each of the pages.

   

3. Decide if you want to stick with Side Navigation or change to the Top Menu as the application's primary means of navigation.

   If you choose to stick with side navigation, it is recommended to select Navigation Icons for each menu entry, otherwise each page will have the same default page icon.
   By going to Shared Components > Navigation Menu > List Entry, you can choose from a variety of pre-built icons, allowing you to choose the best match for each page type.
   Please note that these icons will only appear if you are using side navigagtion.

   To change to Top Menu you will need to navigate to Shared Component > User Interface Attributes > Edit Universal Theme. Then change Position to Top and List Template to Top Menu Navigation, and then apply changes.

   

4. 

While most migrations will be relatively painless, there is no set path for how dealing with issues arise as a result of this change. Consider the following pointers for how to exhaustively find and resolve such problems in your new Universal Theme Application.

1. Visually review the migrated application.
   - Run each page of your application, or at least a good cross section of different pages to make sure that there are no obvious display issues.
   - If you have installed your original application under a different Application Id, perform side-by-side comparisons on a wide selection of pages, to ensure different page elements, such as buttons, and the overall page layout are not too divergent.

2. Check non-standard components.
   - Be sure to check any pages where you implemented your own JavaScript to ensure the page still operates correctly. Many of the default class names for elements were changed, and some of the inline scripts that you have augmented your pages with may no longer be needed.
   - Review any pages or templates where you have added any CSS libraries. If necessary, reapply the CSS libraries into the migrated application.
   - Review all plug-ins used throughout your application to ensure they are still functioning correctly. Some plug-ins from third parties may not work correctly with Application Express 5. If so, you may need to remove the plug-in or search for an APEX 5.0 compatible plug-in.

3. Ask your users to test your app.
   - After testing the application yourself, the next step is to ask your users to use the new migrated application to ensure they are comfortable with the new user interface, and can readily use the application.
   - Determine from your end users if any end user training material or application documentation needs to be revised before releasing the new application into production.

Once you have brought your application up to a "functional" state, you should consider a few more simple improvements you can readily make to your application, so that you can take full advantage of the new features in both Application Express 5 and Universal Theme. For example, you may want to prototype some different layout options, with a select group of users, to see if existing pages can be readily improved by simply changing some Template Options.