In a situation where we have years of legacy SW assemblies (593 SW assemblies with multiple configurations) in zip files. Because of this and the nature of our products, we have a lot of parts with duplicate names but not necessarily duplicate design content (dimensions, configurations etc.). Looking for some ideas on how to best transition this data. Tried picking the duplicate file with the latest date in each case, and loading the entre data lot, but during testing we are getting a lot of SW assemblies with missing parts, and wrong versions of parts. Estimated work hours to fix this would be 6400 hours. This is non-starter for management.

Options being considered:

1. load only the most used SW assemblies.

2. Load SW assemblies only as needed.

3. Load SW assemblies in groups that share parts as needed and clean up small lots of data.

3. Load small hardware parts first and slowly integrate the assemblies.

4. Load the entire data lot and give each file with duplicate names as suffix to make that file unique.

Looking for any other thoughts, ideas or experiences