Do Custom Field Mappings Survive QTest Upgrade Failure and Backup Restore?

QTest's documented upgrade recovery path relies on restoring a pre‑upgrade database and file‑system backup rather than an automatic rollback. The upgrade wizard does not revert schema changes or re‑apply custom configurations when it aborts mid‑process, leaving administrators to reconcile any partial updates manually.

A gap remains in the official guidance: it does not explicitly state whether custom field mappings and integration scripts—stored as metadata in the database and as files on disk—are fully preserved when a failed upgrade is followed by a backup restore. Community reports suggest these artifacts may be reset or require manual re‑import, but no authoritative source confirms the behavior across versions.

Which QTest versions have been verified to retain custom field mappings after a backup restore following a failed upgrade? Does the restore process also reinstate integration script files and their registered endpoints without additional steps? What verification steps does QTest support recommend to confirm that all customizations are intact before returning the system to production?