KB0013 - Moving PSU to another server
Below are Adam's comments on this topic from August 2nd, 2022:

We recommend either backing up and restoring that folder or by using a centralized source control system like Git. We offer git integration directly in PSU.
Related Articles
KB0015 - Offline PSU server has slow dashboards
Disclaimer Please be careful with changing any settings on your server around the Certificate Revocation List. You should only do this if you know what you are doing. Read the related Github articles (linked below) in their entirety. Symptom PSU ...
KB0011 - Are licenses different between Production, QA and Test/Development servers?
Update January 24th, 2023 Adam recently summarized the Developer's license per below: The only real limitation on the developer license is that it cannot be accessed remotely. The server is only available on loopback when using the dev license. If ...
KB0074 - Connecting to PSU API w/Windows Auth
Scope This article applies only to PSU environments where Windows Authentication[1] is enabled and known to be working[2]. Problem You are not able to interact with the PSU instance using the Invoke-WebRequest PowerShell cmdlet even though logging in ...
KB0014 - Enterprise versus per-server licensing FAQ
Below are some questions commonly asked about the benefits of purchasing an Enterprise license vs. individual per-server licenses. Q: What is the benefit of an Enterprise license vs. a Per Server license? A: The Enterprise license allows an unlimited ...
KB0082 - Why is PSU listening on port 5000 even though it is not configured to?
Background You have PSU setup using only HTTPS (typically on port 443) by way of the appsettings.json file located in $Env:ProgramData\PowerShellUniversal[1]. Problem The PSU instance is listening on two ports: the default port of 5000 and the port ...