I am a FileMaker Pro Developer in California. I operate my own business which is essentially correcting faulty databases and normalizing or getting data ready for import into a new database from an older version, sometimes called ETL (extracting, transferring and load) data migration and normalization. My high bid is based on my fees per hour as a developer, and the fact that you might not know what is causing the abnormalities in your present database. I have to look at
1) the data set itself, we can use an NDA
2) the original database in Version 12 or a modified
3) the new database.
Converting databases is not a matter of merely changing versions. The problems you are experiencing with your present database can be numerous - in the scripts, in the layout design, in the programming of the layout, and the calculation of fields based on the layouts. All of the language I have used herein is specific to FileMaker.