# PVCS repository preservation and migration record
Guide: https://yenra.com/merant-pvcs/
Work from a verified copy. This worksheet does not execute any migration.
Owner; exact Version Manager/client/server versions; OS; licensed tooling:
Project database; archive locations/file server; configuration; permissions:
Backup creation; restore environment; restore evidence; immutable source hash:
Representative sample: text, binary, renamed path, branch, labels, keyword expansion:
Release label -> per-file revision mapping and missing components:
Export policy: source bytes or expanded workfiles; line endings; executable mode:
Author mapping; time zones; branch mapping; unavailable metadata:
Scope: snapshot-only / selected releases / reconstructed history:
For each release: file count, paths, hashes, executable flags, build result:
Explain every intentional difference; attach mapping and comparison evidence:
Target repository permissions; rejected/unsupported names; test clone:
Uncommitted work; change freeze; final delta; read-only original; recovery owner:
Acceptance: original can be restored; required releases can be reconstructed;
representative builds and tests pass; stakeholders accept documented omissions.
Fictional example: release R1 may select a.c revision 1.7 and b.c revision 1.3.
Copying each file's latest revision would not reproduce R1. Record mappings first.
Version-specific source: https://help.serena.com/doc_center/pvcs/ver8_1_4/vmug.pdf
Target format: https://git-scm.com/docs/git-fast-import