Microsoft Dynamics GP ERP, or former name Great Plains Dynamics is available on Microsoft SQL Server platform only (current version GP 10.0), earlier versions: 7.5, 7.0, 6.0, 5.5, 5.0, 4.0 were also available as Great Plains Select on Pervasive SQL 2000 (which is successor of Btrieve) and Ctree/Faircom
In this small publication we will try to orient you even in the case when you are on Great Plains Accounting for DOS or Windows to upgrade it all the way up to current Dynamics GP version 10.0
1. If you are on Dynamics GP 8.0, or 9.0. Upgrade is simple enough, just take to consideration that Great Plains 8.0 is not compatible with SQL Server 2005. However if you have GP 8.0, you still can move it to SQL Server 2005 (just databases and user security – please request user logins transfer technical knowledge paper from your Great Plains VAR) and then do upgrade on SQL 2005 level. Upgrade is just one step – please apply the most recent service pack to GP 10.0, currently SP3 (December 2008)
2. If you are on GP 7.5, 7.0 on Microsoft SQL Server 2000. We recommend two steps: first step – upgrade to GP 8.0 and then go to 10.0 on the second step. Please, be aware, that if you are on Pervasive SQL 2000 or Ctree – you will need migration to Microsoft SQL Server – Migration tool is available from Microsoft Business Solutions, request it from your Great Plains Reseller or consultant, read next paragraph for additional details
3. Migration to Microsoft SQL Server. If you are with older version of Great Plains (please, if you are on GPA for DOS, be patient, your solution is few paragraphs down), we recommend you make upgrade on the same DB platform: Pervasive SQL or Ctree all the way up to version 7.5. And then on GP 7.5 you migrate to 7.5 on Microsoft SQL Server 2000. Migration tool works simple – it reads your data on Pervasive/Ctree and through ODBC connection moves it to GP 7.5 on MS SQL Server. Naturally – you will need to create blank companies on MS SQL Server with exactly the same account segmentation, plus refer for additional setup in Migration manual
4. Great Plains Accounting for DOS. We recommend you to migrate to GP 7.5, initially update GPA to version 9.5. If you do not have the budget to migrate away from GPA, you may consider strategy of moving GPA server from old Novell or Windows NT to Windows 2003 Server, where you mount it on Pervasive SQL 2000. Special setting must be done, this step requires consultant help
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
