There's a few ways to do this:
With WCC:
1. Use the ECLI. First you export your existing jobs using "autorep -J ALL -q > jobs.out", then use the WCC ECLI import function to load that file and it creates the jobs on the Autosys(in the database) for you. The downside to this is the file you upload has a max-size which some customers hit up against. Also, if there is an error during the import process(ie what was proper jil in 4.5 is no longer so in 11.3) then you won't get good error indications. The ECLI import is good for small groupings of job imports (boxes, etc).
2. Use the GUI (AppEdit and QuickEdit) to create jobs. This would take a really long time if you had a lot of jobs to import.
With Autosys:
1. Export your old jobs via "autorep -J ALL -q > jobs.out" and then re-import them via running "jil < jobs.out" on the target autosys side. If you get errors(jil syntax changes, required machines missing, etc) it will show up pretty clearly in the output window and then you can debug from there. You also don't get last job-run info(from your old database) using this method.
2. Use the Autosys DataMover utility which is part of the normal migration procedure.