Linux

No, it should work fine, but a backup is always a good idea.

It's not like Windows where it has to install a bunch of new drivers via 7 reboots. It just sees the new hardware and uses the correct drivers.

I would mostly agree with the others that you will have no issues booting, HOWEVER...that doesn't mean you won't run into some problems because we don't know your system.

Here's where you might run into problems:

1. Audio hardware: make sure whatever chipset you're moving over to is fully supported with kernel drivers, and disable any audio customizations you may have made to pipewire or pulseaudio. You may run into input confusion, hardware level/volume problems, and mixing issues, so it's best to revert to whatever defaults you may have on hand before booting.

2. Network: same thing as above, but also make sure you don't have network settings tied to a specific PCI device in your configs.

3. Disable docker and VMs from systemd before first boot: if you have any stateful containers that might be thrown into disarray by bad boots (IF they happen), you may have to spend a lot of time cleaning up. Much safer to just let them not start until you're satisfied that everything is ok, then just enable the services again.

4. Remove any Nvidia settings tied to a specific device or display. This is probably going to be the most common thing people run into. Wiping and reinstalling the Nvidia stack should fix it though if you run into issues.

All of that said, the first thing you can do to suss out IF you may have any issues with your hardware is boot a liveusb on your new build first and making sure everything works. If it does, great. If it doesn't, you know what to expect. If then booting your old drives shows problems, you've also already proven that shouldn't be the case because a liveusb worked fine, and you know where to start attacking problems.

Good luck!

I'd expect it to work maybe 80% chance.

I feel ike I've had issues with grub doing that type of swap- I can't remember the specifics, maybe hd0,x became swapped with hd1,x Or maybe i did something daft like futz with the partitions.

(assuming mint does use grub) maybe be prepared with either a grub shell cheatsheet, or just a live usb to chroot from so you can reconfigure grub.

Or just try swapping the ports over.

Only other issues I've had is maybe going non-uefi to uefi, and with things like "secure boot". You can just trial and error the few combinations if you dont know.

Maybe note down any current mobo bios settings especially re: disks and boot.

edit - i fogot cpu microcode is vendor specific - you might need to swap that or at least remove the old microcode before swapping it could be irrelevant https://wiki.debian.org/Microcode

Have done this several times. I have never had to do anything else. I just swap em and boot.

I've done this with Debian before, and it works fine. Linux usually mounts the root filesystem based on its UUID, so it doesn't matter if changing the motherboard caused a change from /dev/sda to /dev/sdb .

If you use the proprietary Nvidia driver, make sure to update it to a version that supports the new video card. If you use the open source Nvidia driver, you should be fine even if it's old, because it will at least support starting up in an unaccelerated mode.

i use mint and i upgraded my cpu from i5-9600kf to 7800x3d, and ofc mobo and ram too, and i had to reinstall. the system booted up but everything was very stuttery and slow

I did something similar recently and found it was an easy drop-in situation... so you'll likely be okay.

I upgraded my CPU on my debian server. Went from i5-4690K and RX 480 to just an i5-12600K.

I could see a potential issue if the WiFi card is different and you're not hard wired.