Why are you restoring a backup?
Before you do so, take a new image and AOA backup. Then you can undo the restore.
Is it the exact same model # of robot and controller? Does it have all the same options and hardware in the controller?
That's good.
Still start by taking image and AOA backups of each robot.
Then you can restore from the other completed robot.
After that you will want to load the correct mastering counts. If the new robots were already mastered you can simply load the sysmast.sv file from your AOA backup. If not then you should enter them manually from the original data sheet. After mastering, take reach robot joint to 0 degrees to verify mastering is correct.
Then go into the system variables and enter the correct robot F#.
After that is completed you can do your list of things above (tool, frames, vision, etc).
Your order is good. User tool, user frames, vision, then run slow in teach mode and touch up as needed.
Worth noting/adding to what HawkME said (also for future readers of this thread):
NEVER restore an IMG from another robot system!
As long as two (or more) robots are of the same model, their controllers are the same kind and they both have the same software options installed then you can restore the AOA from another robot.
(If not, then you're better off manually entering the frame data, payload, manually loading TP-programs and so on.)
However......
Unless they also share the same exact version of the system software, leave out the SYSSERVO.SV-file and the SYSVARS.SV-file when restoring.
Also (for obvious reasons) never restore the SYSMAST.SV-file from another robot.
As a last reminder:
Before loading something new in to a robot, make an IMG-backup as well as an AOA-backup in case things go south...
