You’re offline. This is a read only version of the page.
70
Hey Guys,
Had a few issues that I'm stumbling on right now and hoping someone here could help. I am attempting to migrate from quickbooks enterprise to dynamics GP, but running into some errors when importing them in. First im getting transactions errors and when I go next on map unmatched records using wizard, its showing unmapped price levels, department, and job title. If i don't map anything, which i cant because there is no data to map to in the system yet, I get a error
referenced table is missing or unavailable [Exception] Incorrect Syntax near '<'
Anyone know what is going on there?
I was originally using integration manager to move the orders over, but had some issues with that as well, all of the invoices that Im bring over from QB, if the price was manually changed for that order, it doesnt seem to bring the pricing over correctly. Not sure where to go from here because a ton of invoices are showing as $0.00, some without quantity, some without pricing.
*This post is locked for comments
I have the same question (0)Edward - I hope this will save you some time and frustration. I have used the QB migration tool several times over the past year on various versions of QB, always migrating to GP 2013.
We encountered a problem very similar to the one you described, during one of these migrations and spent some time with Tech Support attempting to resolve it. We had no luck resolving the issue you described and spent 72 hours troubleshooting it. We attributed the problem to an update applied to QB.
My suggestion is you should choose another machine or provision a virtual machine, install QB and GP fresh and, restore back ups and do the migration in this environment
I was able to install a fresh copy of QB, with no updates, on a Virtual Machine and perform the migration in the virtual environment. I then move the GP databases into the Client's live environment. This was much faster than trying to resolve the issue in the live environment.
The easiest way to perform QB migrations is to focus on Master Records only, then tackle the issues invariably caused by the migration (i.e. decimal places for quantities default to two decimal places).
When we do full migrations, we use SQL Queries, macros, utilities and PSTL to solve data problems. Importing transactions with the migration tool prevents the use of the utilities to change the decimal place defaults, unless you are willing to destroy the transactions and recreate them.
We use SmartLists, Macros and Integration Manager to capture the imported records in Excel files, remove them and bring them back in again modified as required.
The problem is, unless you set client expectations about the process, you are going to wind up eating a ton of time, especially if you have to run this process multiple times.
Share
Report
All responses (
Answers (
