Andrew Karasev asked:


Microsoft Business Solutions Great Plains Dynamics GP version update technology seems to be straight forward – you insert new version CD and upgrade will be launched automatically with wizard. Proven Great Plains Dexterity technology will determine your current version and it will replace first GP workstation side files: Dynamics.exe, Dynamics.dic, Dynamics.set, etc., then it will begin Dynamics database tables conversion process (if new version has modified table structure, this table will be copied into temporary table, then dropped and recreated and then repopulated from temp table). The same DB rebuilding process then will be launched for all the companies you have, where you will have decision making control via wizard. Real life situation however requires you to make your homework and think through different upgrade pitfalls and scenarios. Let’s come through some of them:

1. Upgrade path. This term is used when you are on older version of Microsoft Great Plains or Great Plains Dynamics/eEnterprise. Historical versions are: Great Plains Dynamics/Dynamics C/S+ 4.0, 5.0, 5.5, Great Plains Dynamics/eEnterprise 6.0, Microsoft Great Plains Dynamics/eEnterprise 7.0, 7.5, Microsoft Great Plains Dynamics GP standard and professional: 8.0, 9.0, Microsoft Dynamics GP Professional and Business Ready 10.0. Current GP version as of fall 2007 is 10.0. Versions, prior to 8.0 were available on Microsoft SQL Server, Pervasive SQL 2000/Btrieve and Ctree/Faircom. If you are on non-Microsoft SQL Server version, you will need one extra step – migration to SQL Server 2000 or 2005. Otherwise upgrade path typically shows you version upgrade line, for example if you are on version 6.0 and would like to switch to 10.0 you will need first to upgrade 6.0->7.5, then 7.5->9.0, then apply 9.0 Service Pack 2 and then you are good to go to version 10.0

2. Third Party Modules. Through the history of Great Plains Software – its Great Plains Dynamics Dexterity platform was ready for third party ISV to develop satellites or extensions to core GP logic: Icontrol Manufacturing, MatchData Project Accounting, Intellisol Advanced POP and Project Accounting, Mekorma, Avalara, Dynamics ZIP – these are good examples of third party modules. Obviously even if Microsoft Business Solutions encourages its ISV partners to extend Dynamics GP, it can not stay behind third party update process – you should have your GP partner contact your third party module vendor and check on update path and if targeted new version is available for your extension
3. Great Plains Accounting for DOS, Windows and Mac. In earlier 1990th GPA was popular and the versions you may have are 9.5 or 9.2. Upgrade path includes migration module to Microsoft Great Plains 7.5 and then regular upgrade for GP. If you consider staying on GPA, we do not recommend this as Great Plains Accounting is no longer supported by Microsoft (successor of GPS). The only way to support GPA is to look known issues DB available for Microsoft Business Solutions partners, but you understand that this is not equal in support quality to dedicated GPA consultant support – these people do not exist anymore as they changed their career path in late 1990th