QBO flip flops the customer name and customer ID (which you put into CW to link the accounts), so you'll have to make those consistent, and we were using GL account numbers in CW to link to QB Desktop, and I had to go in and delete those and set them up again using the GL account NAME, instead of the account number. I'm willing to deal with the missing features QBO has, as they'll get them eventually one day.įor the Mobius connection from CW to QBO, you'll need to reconfigure your customer names and GL Accounts (or at least I did). Obviously, there are things that QB Desktop (we had the Accountants version) can do that QBO can't do, but then QBO has the modern SAAS experience that we all love so much. I guess that's ok if you view them as a payroll service provider, not just providing me a module to do my own payroll. I've also noticed I can't get to information in payroll in QBO like I could in QB Desktop, I have to reach out to support to make a change on their end. Payroll is pretty dang complicated because the regulations change all the time, that the payroll module usually never gets updated to match the rest of the software. I've dealt with it in other products from Sage as well. It would be easy to throw a fit over the payroll deal, but payroll is it's own beast. The only other option is to print out every payroll report you think you'll ever need and then let your QB Desktop payroll subscription expire. But then you also need a payroll subscription in QB Desktop to view a lot of things, so you're paying for 2 subscriptions for a while. So you need to have QB Desktop around to view detailed payroll info from the past.
No previous paychecks come over, or payroll reports from previous years. Payroll employees, salaries, and deductions come over. The data synced over pretty seamlessly and it's all there.save for PAYROLL.
I didn't have access to put it on the C: drive on the server, so I had to download a copy of the file to my local machine, install QB Desktop, then upload it to QBO. The biggest pain in the butt for me was the QB file had to be on the C: drive before it would upload to QBO.
Check our upgrade guide on how to move the Desktop integration that's built into Manage to our Online with Mobius In my completely biased opinion it's the obvious best choice ?. NetExtender is an SSL VPN client for Windows, Mac, or Linux users that is downloaded transparently and that allows you to run any application securely on the company’s network. Once you get to the integration, you'll definitely want to consider my company's software. SonicWALL’s SSL VPN features provide secure remote access to the network using the NetExtender client. I was pleasantly surprised how easy it was when I did the conversion for my own company about 3-4 years ago. Fortunately this usually isn't the case with Quickbooks. It ends up being worth it for the better day-to-day experience. I used to do this a lot with large manufacturing companies who migrated to a new accounting system and couldn't import ANY historical information into their new system. IF you run into those limitations then you'll need to condense your database (remove historical records from past years that you no longer need) to migrate it and then keep a backup of the un-condensed desktop database for your historical records. Intuit has some limitations on the size of the QB database you can migrate to Online. For best results, perform the solutions in the order shown.In my experience QB->QBO is a pretty smooth process when it works. The first solution may solve your problem or you may need to try them all to resolve the issue. Intuit recommends several solutions for this problem. The file referenced in the error is in use or damaged.n.C:Program FilesCommon O23 - Service: SonicWALL NetExtender Service.
The Windows permissions for the folder containing the file are set to restrict access. O23 - Service: Intuit QuickBooks FCS (QBFCService) - Intuit Inc.