What I mean is that: tSel_Age=1|1|16
tSel_AgeTag=1|1|Age is obviously saying that the age of the character is 16, and that the name for the field should be 'Age' (localization, I take it). On the Pathfinder Character sheet (whichever one you are targeting, there are several), there is probably an attribute named 'character_age', which would need to be set to the value 16. That's not terribly difficult. It's also not so bad to parse that structure and know that you have Age and can ignore AgeTag. What is likely to be tedious is knowing that ('Age' of 16 needs to be set in the attribute 'character_age') X (all the other fields for import). Someone has to build that lookup. Then it gets more complicated when you take things like: tSel_Race_HitDieType=1|1|=IF(COUNTIF(t_Types,tSel_Race_Type)=0,"d4","d"&VLOOKUP(tSel_Race_Type,t_Types,index_type_HD,FALSE)) (which may not need to be imported, but I didn't look at every line to find one I am certain would be) That's more than just data, thats a lookup in a collection of data that isn't in the export. That's logic that would either need to be replaced/parsed/ignored. So, speaking of special programs, he'd need an API script to do the import, or possibly a sheet worker script on the character sheet. If you could get the sheet maintainers interested in parsing this format and importing it into their sheets, they would likely know how to do it. I can't speak to if they would be willing, or what it would take. Character sheets are mostly community driven. The most likely scenario I can think of if the TOS+ author wants to get a smooth path into Roll20 characters would be for him to write his own character sheet and write the importer himself. That would allow him to control both sides to where he can make whatever changes to either one he wants without breaking the other.