I think we have couple more option before we think of DB update:
1.Can you identify all the test cases from that project in the new project? if you could, its better to delete those and migrate that project again with required information.
2. You can extract Test Set Folder and Test Set tables into excel spreadsheet and then create a OTA script to create those folders and test sets into QC. The id and folder id will help to determine father and child. folders needs to added first and then test sets. You can teh map test instances into Test sets
3. if both of the above options won't work for you, you can look for DB update. I recommend you to check with DBA for he needs to understand the sequence and sequences of how these info is maintained in backend. This is again similar to option 2, but all updates in db tables. If your new project has nothing in Test Lab, then DBA can extract the Test Set(Cycle) and Cycl_fold tables as such from previous projects. Otherwise he has to go with the last Test Folder ID in new project and reorganize rest of the folders and test sets. For Test Instance, he can copy instances from Test Inatance table in previous projects and identify the test case id's in new project to map it. Step and Run id references has to be removed as you don't have any in those tables. afterall he has to update Sequences table with last ID's for each of Test Set, Test Instance, Test Set folder etc.
1.Can you identify all the test cases from that project in the new project? if you could, its better to delete those and migrate that project again with required information.
2. You can extract Test Set Folder and Test Set tables into excel spreadsheet and then create a OTA script to create those folders and test sets into QC. The id and folder id will help to determine father and child. folders needs to added first and then test sets. You can teh map test instances into Test sets
3. if both of the above options won't work for you, you can look for DB update. I recommend you to check with DBA for he needs to understand the sequence and sequences of how these info is maintained in backend. This is again similar to option 2, but all updates in db tables. If your new project has nothing in Test Lab, then DBA can extract the Test Set(Cycle) and Cycl_fold tables as such from previous projects. Otherwise he has to go with the last Test Folder ID in new project and reorganize rest of the folders and test sets. For Test Instance, he can copy instances from Test Inatance table in previous projects and identify the test case id's in new project to map it. Step and Run id references has to be removed as you don't have any in those tables. afterall he has to update Sequences table with last ID's for each of Test Set, Test Instance, Test Set folder etc.