If your fields don't have container, set ODBC sharing then import from ODBC matching field names as
SELECT old AS new, ...
Great, thanks! I'll give that a go. I could in theory loop through the list of fields and replace field contents with the ExecuteSQL, right?
Hmmm I can't seem to get SELECT...AS to work.
For example, in the old table the primary key is zzp_UID, and the new DB's primary key is _P_UID, but SELECT "OldTable"."zzp_UID" AS "_P_UID" FROM "OldTable" doesn't bring in any records when run from a script as the SQL argument on Import Records. I've set up the ODBC source etc. Is there a step I'm missing?
A couple of other ideas:
1. create a duplicate (converted) of your OLD files, rename the fields as needed, import into NEW.
2. use of XML export with XSLT to 'map' the field names to the NEW will also work.
NOTE: none of these, except the FM-FM will bring in container fields, thus I tend to use #1 for that.