It is possible, but it would be a very manual process involving modifying retention policies, deleting & recreating PVCs, CRs, etc..
Therefore it would be unsupported and we strongly discourage it.
Trident’s metadata is maintained in Kubernetes Custom Namespace Definitions (CRD) that are namespaced. Installing Trident in a new namespace is equivalent to creating a completely fresh Trident install.
For Trident to be moved to a new namespace and still be cognizant of the PVCs it created you will need to move all Trident CRs to the destination namespace.
Typically there are no PVCs in the Trident namespace. PVCs will be in the application namespaces.
See the Trident Documentation