Using current modules to create new ones

There are also considerations if you're using SCORM. If so, be sure to check your SCORM properties as those will be the same, so when you upload the new module to an LMS, it'll have the same ID, interaction IDs, etc.

So be sure to review and change any SCORM settings that may matter, if it applies.

Lilybiri​'s questions are quite relevant, depending on the version that created the file, and the current version, you may have quite a bit of rebuilding to deal with.If we're talking about earlier versions of the same major release, it's less of an issue.

Captivate 8.0.x -> 8.0.3.290, likely fine

Captivate 9.0.x -> 9.0.2.xxx, definitely fine

7 or before -> 9, beware!

In Cp8, I've run into some inconsistencies between File -> Save As and and duplicating files in the Windows or Mac file system.

This impacted the storage of the path for publishing, so it was rather trivial, but still annoying.

In any event, make good backups before proceeding!

Open the files from a local drive, NEVER over the network.

(Don't OPEN and SAVE AS from the only copy of a file, as it can be corrupted!)

What do you want to do about 'updates'? Do you know which version of Captivate was used to create those 'old' modules? Which version would you use to update? Although you can open most older version projects with the last version, don't expect that everything will work immediately because so much can have changed in between versions.

I believe you should be fine by choosing File > Save as and giving it the name you want in the location you want.

Cheers... Rick