>>105845987
You should probably be fine. Just clone the drive with Macrium and you should be free to go.
For edge cases where you migrate from a 512{e/n} drive to a 4K sector-native drive, it's not that simple.
https://knowledgebase.macrium.com/display/KNOWX/Incompatible+Disk+Selected

In which case you might just want to image the Windows partition (cut out the middleman and use DISM to image it from a WinPE)
dism /Capture-Image /ImageFile:"X:\Backup\WinBackup.wim" /CaptureDir:C:\ /Name:"Windows Backup" /Description:"%DATE% %TIME% - to NVMe drive" /Compress:max /CheckIntegrity /Verify /EA
Tune the CaptureDir value if the Windows volume letter you want to backup is different (so, not C:), and set the ImageFile path to the external storage.
Prepare the right partition layout for your new drive with diskpart (a notorious change with 4Kn drives is that the EFI partition has to be 260MB - with the extra 4 megs for safe measure: 4KB sector times 65526 clusters for minimum FAT32 volume size).
Then you deploy the Windows image with the very same tool you made a capture of - DISM (but with the /Apply-Image switch: set the ApplyDir path accordingly.)
dism /Apply-Image /ImageFile:"X:\Backup\WinBackup.wim" /Index:1 /ApplyDir:W:\ /CheckIntegrity /Verify /EA
After that you make the installation bootable with BCDBoot - it will deploy the Windows Boot Manager in the EFI system partition and set-up the BCD registry. Also configure the recovery partition with REAgentC.

Here's some neat MSFT documentation regarding manual deployment of Windows.
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/capture-and-apply-windows-system-and-recovery-partitions
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/capture-and-apply-windows-using-a-single-wim
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions