Some reason to want to do this? personally I would avoid the potential uncertainty and just make a backup to file on the Source server, copy that backup to the new Destination server and restore it there. That gives you options to minimise the downtime (Source server / databases can remain running, provided they use FULL Recovery model, until the very last moment (and then use a final LOG backup to cut-over to the new server). If they don't use FULL Recovery model you can do the same thing with a DIFFERENTIAL backup, but the cut-over won't be quite as quick - might still only be a few minutes though.
Here's my notes on what I have found in upgrading server and SQL versions over the years: