You can use getaddressinfo on a bunch of your addresses and check that the wallet says "ismine": true for them. You can use listunspent before and after migration to verify that the wallet knows the same UTXOs. You can use listtransactions before and after migration to verify that the wallet knows the same transactions. It overwrites the original wallet.dat file, but a backup of the original is created at the start of the migration process. That backup can be restored manually (by copying the file, or by using restorewallet or File > Restore Wallet), and is also restored automatically if the migration fails so that you don't have a wallet that is partially migrated. I opened a PR a couple weeks ago to produce the watch-only wallet file directly instead of having to do the import stuff: There's a followup PR to add a menu action to the GUI to do that: This was slightly complicated to do because of the legacy wallet code. But with it removed, the implementation becomes much simpler. There was a PR to add import things to the GUI but it was closed after a couple years of not getting any review. Everything in the "descriptors" field, i.e. everything after the opening square bracket, to the matching close square bracket, including the brackets themselves. The contents of the descriptors do not need to be modified and are intentionally such that the whole thing can be copy-pasted into importdescriptors. "internal": false / "internal": true that is seen in the output, but that is not seen in the expected format to import it, which also has this which is not seen in the output... so what im supposed to do there? Nothing, those are optional fields.
You can use getaddressinfo on a bunch of your addresses and check that the wallet says "ismine": true for them. You can use listunspent before and after migration to verify that the wallet knows the same UTXOs. You can use listtransactions before and after migration to verify that the wallet knows the same transactions. It overwrites the original wallet.dat file, but a backup of the original is created at the start of the migration process. That backup can be restored manually (by copying the file, or by using restorewallet or File > Restore Wallet), and is also restored automatically if the migration fails so that you don't have a wallet that is partially migrated. I opened a PR a couple weeks ago to produce the watch-only wallet file directly instead of having to do the import stuff: There's a followup PR to add a menu action to the GUI to do that: This was slightly complicated to do because of the legacy wallet code. But with it removed, the implementation becomes much simpler. There was a PR to add import things to the GUI but it was closed after a couple years of not getting any review. Everything in the "descriptors" field, i.e. everything after the opening square bracket, to the matching close square bracket, including the brackets themselves. The contents of the descriptors do not need to be modified and are intentionally such that the whole thing can be copy-pasted into importdescriptors. "internal": false / "internal": true that is seen in the output, but that is not seen in the expected format to import it, which also has this which is not seen in the output... so what im supposed to do there? Nothing, those are optional fields.

You can use getaddressinfo on a bunch of your addresses and check that the wallet says "ismine": true for them. You can use listunspent before and after migration to verify that the wallet knows the same UTXOs. You can use listtransactions before and after migration to verify that the wallet knows the same transactions. It overwrites the original wallet.dat file, but a backup of the original is created at the start of the migration process. That backup can be restored manually (by copying the file, or by using restorewallet or File > Restore Wallet), and is also restored automatically if the migration fails so that you don't have a wallet that is partially migrated. I opened a PR a couple weeks ago to produce the watch-only wallet file directly instead of having to do the import stuff: There's a followup PR to add a menu action to the GUI to do that: This was slightly complicated to do because of the legacy wallet code. But with it removed, the implementation becomes much simpler. There was a PR to add import things to the GUI but it was closed after a couple years of not getting any review. Everything in the "descriptors" field, i.e. everything after the opening square bracket, to the matching close square bracket, including the brackets themselves. The contents of the descriptors do not need to be modified and are intentionally such that the whole thing can be copy-pasted into importdescriptors. "internal": false / "internal": true that is seen in the output, but that is not seen in the expected format to import it, which also has this which is not seen in the output... so what im supposed to do there? Nothing, those are optional fields.

You can use getaddressinfo on a bunch of your addresses and check that the wallet says "ismine": true for them. You can use listunspent before and after migration to verify that the wallet knows the same UTXOs. You can use listtransactions before and after migration to verify that the wallet knows the same transactions. It overwrites the original wallet.dat file, but a backup of the original is created at the start of the migration process. That backup can be restored manually (by copying the file, or by using restorewallet or File > Restore Wallet), and is also restored automatically if the migration fails so that you don't have a wallet that is partially migrated. I opened a PR a couple weeks ago to produce the watch-only wallet file directly instead of having to do the import stuff: There's a followup PR to add a menu action to the GUI to do that: This was slightly complicated to do because of the legacy wallet code. But with it removed, the implementation becomes much simpler. There was a PR to add import things to the GUI but it was closed after a couple years of not getting any review. Everything in the "descriptors" field, i.e. everything after the opening square bracket, to the matching close square bracket, including the brackets themselves. The contents of the descriptors do not need to be modified and are intentionally such that the whole thing can be copy-pasted into importdescriptors. "internal": false / "internal": true that is seen in the output, but that is not seen in the expected format to import it, which also has this which is not seen in the output... so what im supposed to do there? Nothing, those are optional fields.