The first thing I'd do is try and identify the file 'header', and then search for a pattern within the file.
If I were to export, say, some path-finding data from my file, I'd want to know how to read it back in.
I'd write out the header, containing how many nodes there are in the level, etc, then the data would come straight after it.
This way I could safely read it back in without having to hack in checks for how many nodes were written out. (A good reference for file headers in games is maybe the Q3 BSP file format)
Then for the pattern, I'd assuming it would write out an array (node table) of type T (node data), so it might look like 'float float float unsigned int unsigned char' per node.
Hopefully this helps. I can't really do more without the file and game in question.
Good luck!
EDIT: And of-course using a disassembler/debugger on the function that reads in/writes out the file could give you some useful information

It also might be worth practising on your own file reading/writing test application so you know what to look for (This way you'll have source code to compare to)