Data replacement goes through your database data and replaces any hardcoded references to the URL or file path of your old site with that of the new one. If that doesn't complete correctly your site is unusable. If your site works fine then you probably have nothing to worry about.
Go to a few of your WooCommerce products which were added at the beginning and a few added closer to when you took the backup. If they are all OK there's nothing to worry about. Most likely the data replacement stopped while going through WooCommerce's order information because of a bug in XAMPP.
Aside: XAMPP is using the non-thread safe version of the PHP executable when they should be using the thread safe one. This causes instability when running a lot of requests in a short period of time such as when taking a backup or, far more likely, when restoring a backup. You can work around that by increasing the minimum execution time in both cases. The exact reason why this works is really complicated and very technical, but a minimum execution time of around 5 to 7 seconds overcomes the reasons that cause PHP to crash on XAMPP (and WAMPServer which has a pretty similar setup). I've found that the most stable local server I can have on Windows is either IIS or a custom Apache installation but they are both more involved in setting up correctly.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!