If they're available via ESS, you should just be able to straight import from the ESS tables into the blank filemaker tables.
you can do an export -> import to create new tables, however you will need to do a lot of followup configuration anyways (setting primary keys, auto-enter calcs, create/modify dates & users, etc..)
This stuff is easily scriptable too once you get the tables setup in filemaker.
Below technique will allow you to create local FM Native tables from an ESS table currently residing in the same file and preserving the field IDs so layouts and scripting are still mapped correctly in new table.
Go to ESS table
Show all records
Choose File import/Remote
Select current file (execution)
Select the ESS table
From top right drop down choose ‘New Table’
change import order drop down to ‘Creation Order’
repoint all items on map from ESS instance to local instance
validate scripts and layout look correct
POST TABLE CREATION
validate create/mod date times/allow mod off
check for local calc fields in those ESS table
check field types (num, text, date formats)
Mike's advice is spot-on.
You can save a step or two with just the Import script step and a SQL call (SELECT) to the ODBC source. No need to show the data in an ESS table/layout.