Yes however with some caveats. Obviously Windows and Linux use different ways of portraying paths and devices so some editing of the VM may be necessary. Anything that is hard coded in the .vmx configuration file portraying Windows type paths and device names will need to be modified either via the Settings GUI or manually editing the .vmx configuration file. Additionally any VM that contain Snapshots where the parentFileNameHint in the Disk DescriptorFile, whether embedded in a monolithicSparse or the first non-binary extent of the snapshot virtual hard disk, that uses a FQP (Fully Qualified Pathname) it will need to be changed. If you do not know how to do that then I'd suggest one remove all Snapshots before moving to another system.
Any Windows VM's that are subject to WPA will in all likelihood need to be reactivated if the Host CPU are not in the same class.
If you are copying a Windows VM while leaving a copy on the source system you need to have and or obtain the appropriate number of licenses and or Product Keys for the number of copied you maintain.