RE: Export transactions from GP2015 to import them in GP2018
Hi Julia,
Thanks for the details..
What you're trying to achieve is just impossible.. it is going to take more time and efforts to try to export new transactions from GP 2015 to import them into your TEST GP 2018 than re-entering those transactions in the TEST environment.
Basically your GP 2018 will reflect the state of your GP 2015 data after the upgrade on Day X... but going forward, there is no way you can keep in sync the data between the 2 systems, as they are on a different GP version and there is no way you can get the two systems talk together.
Trust me by my long experience of having done upgrades by the ton, that this is not a realistic Testing scenario you're looking at... There is no shortcut you can take when it comes to testing the new GP version. Your users will have to reserve some of their time and enter transactions into the new system the same way they do it in the current production. The goal is not to see if both system are going to match to the cent after a week of testing, that is impossible, but to apply true & known accounting principles to make sure transactions posted in the new system provide the expected results.
You can run some Trial Balance reports between the 2 systems at a date prior to the upgrade (cut-off) to make sure the accounts have the same totals before and after upgrade. That's all you can do.
But, to your point, if most of your GP 2015 transactions are not manually keyed in, but done thru some sort of integrations already (by using eConnect or GP Web Services), then there is nothing that keeps you from replicating the same integrations in the new system in parallel... however, I doubt you'll be able to achieve 100% similarity as there are always transactions that occur for some reason by end-users in the system (like credit notes, returns, voided documents, etc) that might not be replicated exactly on the TEST system..