What about copying the connections first and migrate the sessions with the session manager (-> file -> import) afterwards?You may find more information in the "Getting Started" section of Help -> capture 9.6 Migrating from IBM i Access for Windows ;-)
The systems are pretty easy to type in manually, given the Copy function (in "Actions->Management->System Configurations"). Just fully configure one and then copy for the other hosts. (You could also directly edit the settings file for this, but that would involve exporting, unzipping, manually editing XML, zipping, and importing. Seems a lot harder and slower that way.)The sessions might be worth direct copying and editing of the settings files, particularly if you have any scripting skills, such as Python. Each session has its own .hod file, so once you've fully configured one, you can copy it to another name and edit the relevant properties. I think the only ones you may have to futz with are name, workstationID, and host; but you should try it on one or two .hod files to confirm and make necessary adjustments before doing all 140 or so. I haven't actually had to do this myself, so I'm just presenting ideas, not providing authoritative information.If you don't already know any scripting languages, you'll probably want to use tools for (1) making multiple copies of a file, (2) renaming multiple files (if not already covered by the first tool), and (3) doing search-and-replace on multiple files. Some recommendations that I've used personally (on Windows): Bulk Rename Utility for renaming and grepWin for search-and-replace. Also check out this Server Fault question for multiple copies.