As this paper describes, make sure that your PVCS repo isn't too large for a git repo.
It is a mistake to think of a PVCS conversion as only moving files and their revision history to Git or Subversion. The requirements for moving history, updating scripts, training and best practice approach should be well thought out to fit your specific conversion needs and needs of the developers who are impacted by the change.
I wouldn't try to get all the history for each file, but rather:
check if that PVCS repo contains labels (as in this question),
display each tag in its local workspace
import that as a single revision in a git repo (with the git-work-tree tip, as in this answer).
As this paper describes, make sure that your PVCS repo isn't too large for a git repo.
I wouldn't try to get all the history for each file, but rather: