qtest migration: REST API scripting vs. bulk copy for execution history

Migrating a small qtest test suite between projects while preserving execution history and requirement traceability.

The UI bulk copy generates new test case IDs, breaking links to historical runs and requirement associations, and may time out on larger suites.

The REST API allows custom field mapping and scripted moves, but test runs are read‑only and cannot be reassigned to new IDs, requiring manual re‑linking.

• Can the qtest REST API re‑assign historical test runs to new test case IDs during migration?
• What is the UI bulk copy performance limit for suites exceeding 1,000 test cases?
• Does requirement traceability survive a test case move via the API instead of the UI?