EFS encrypts individual NTFS files. A new account with the same name or a file copy does not replace the matching private key. Preserve existing access without deleting keys or originals.
1. Identify certificates for existing access
Sign in as the authorized user. Run certmgr.msc from Start search and open Personal, Certificates. Find the Encrypting File System purpose. Record thumbprint, validity and associated data; include every EFS certificate in use. A recovery certificate has a different role and needs separate mapping.
2. Export with the private key
Choose All Tasks, Export on the matching certificate. Select Yes, export the private key and Personal Information Exchange, PKCS #12/PFX. Never select deletion of the private key after export. If the key is unavailable or nonexportable, mark migration unresolved; a CER export does not solve that.
3. Protect export and password
Set a strong export password, confirm the protected destination and review the wizard summary. Store PFX and password separately with restricted access, not in email or public shares. Associate the file with its certificate. Creation alone is not a recovery test.
4. Test recovery on copies
Plan import into a separate authorized test user and test a working copy preserved with EFS encryption. Ordinary copying may produce plaintext depending on method; verify encryption on the test copy. Readable plaintext does not prove key recovery.
5. Migrate after acceptance
Record which protected data was read with which backed-up key and what remains unresolved. Preserve original profile, files and keys until acceptance. Do not administratively reset a password to repair EFS. Without a key or an applicable existing recovery route, recovery is not guaranteed.
