Converting From QB Online to Desktop-Not Creating QBXML File Correctly

Which QB Desktop year version did you use?

Converting from QuickBooks Online (QBO) to QuickBooks Desktop (QBDT) comes with several technical limitations, FLBill.

Before we proceed, could you please let me know if you're encountering an error message while trying to convert QBO to QBDT? This will help us identify and provide you with the most accurate solutions.

To begin with, it can be related to the complexity of the conversion tool. The new migration tools support multiple browsers, which can lead to browser compatibility issues, data size restrictions, permissions issues, setup errors, and potential interference from background software.

Once you have verified that all the above points are correctly addressed, you can proceed to redo the conversion process.

If the issue of an empty QBXML file persists even after checking your system and attempting the conversion again, I recommend getting in touch with our Live Support Team to identify the root cause.

Let us know if you need assistance by clicking the Reply button.

2024 QB Accountant Desktop Plus

When I try to access the XML file I downloaded with the Desktop migration tool I get the following error:  The file you selected is not a valid MXL.  Select another file and try again.

The downloaded XML file reports a size of zero KBs.

Thanks.

@FLBill  

Do you have an older version? e.g 2022 or 2023

Another option, you can contact @Fiat Lux - ASIA directly by email for assistance.

I do have older versions going back 15 years or so.

But the downloaded XML file reports zero KBs.  It doesn't seem to have any data in it?

I've downloaded the XML file from QBO three times and all three times it reports zero KBs as its file size.

Thanks.

One other thing:  I am using Firefox as my web browser.

All is now well.  The problem was Firefox.  I downloaded the XML file using Edge and the file imported with no problem.

I thank all who replied.  As usual, the problem was between the seat and the keyboard.  A classic ID10T error.

Thanks again.