Considering new 200 records are to added/created to dedicated table and NOT updates. here goes pseudo script
Go to layout Table1
Show All Records
#OR found set to be transferred
Go to Record/Request Page [first]
Set variable[$CData; value:Table1::ContainerField1]
Go to Layout Table 2
Go to record/Request page[Next/exit After Last]
After execution of script, you can delete records from Table1 (wrong table in which container data is stored - 200 records).
Another Option: script loops through records, exports the container field contents to desktop or temporary folder. Then add new record to table2 and insert file/picture transfer data to table2::containerField2
While container data cannot be exported with export records it can be imported from one FileMaker file to another using import records. So use import records to import this data into table 2 from table 1. No script will be needed unless this is something that you will need to do more than once.
Thanks guys. I'm trying to use Phil's method, but I used the option of external secured storage for my container files. My container files backed up on the server in a folder but the references are still looking for the server.
Change the field's storage option so that this is not the case in your source file before attempting to import this data into the new target file.