You can use ER to move the data, might take a while but you don't have that much data. It will allow you to move to a new physical layout.
Use Enterprise Replication (ER/CDR) to move the data to the new system.
With ER you have the option to test the new platform and play around with it.
When you are ready with testing, you can "Check and Repair" the data on the Target and when this is finished, you can switch over when ever you want within Minutes.
When we did this several years ago, I used Enterprise Replication to enable and complete the migration. That meant I had to go and add primary keys to several tables that didn't have them, but once that was all set, it allowed us to run in parallel for a while before doing the final cutover. This was especially worthwhile because we were moving to a new hardware platform, a new OS and a new DB version. (At the time, from IDS 11.10/IDS 11.50 on AIX/Power7 to IDS 12.10 on Linux x86_64.) If you do this, just be sure to do all of the initial syncs in the foreground, lest you grind your system to a halt. On page size, concur with what Art wrote: On our systems, we have three or at most four page sizes in play. 16 KB always for indexes (and never anything else, as I like having a dedicated buffer pool for just indexes); 14 KB for some wide-row tables; 2 KB for everything else. We have one system where I also needed to add 8KB pages, but that was a special case.