Microsoft Dynamics GP ERP requires regular maintenance and support – version updates, new modules setup and implementation, new users training, data recovery and fixes (such as unlocking the batch, stuck in posting process).
In this small publication we would like to give you highlights on moving old version of Great Plains Dynamics from Pervasive SQL 2000 or Ctree database platform to Microsoft SQL Server 2000 or 2005. If you are on Btrieve/Pervasive, likely that your GP version is 7.5, 7.0, 6.0, 5.5 or 5.0. There might be multiple reasons to update Great Plains version: outdated as the hardware old Windows NT Server, the need to add new Great Plains modules (you can’t get them for your old version) to name a few
1. Migration tool. We recommend you first to upgrade your GP version to 7.5 and deploy migration tool for this version to move your databases to Microsoft SQL Server platform. The technology is simple: you install exactly the same empty companies on Microsoft SQL Server 2000, where you will need to pay special attention to account framework setup (number of segments, their length, etc.). Do only setup, please check migration manual. Then from your Pervasive SQL GP you should create new ODBC connection to MS SQL Server – at this point you are ready to launch Great Plains migration
2. Migration issues, if any. Again, so far what we saw were the problems associated with different account structure – you should move old data into exactly the same accounts framework. If you make your segments longer, then it is not a big problem, assuming that you are OK to see blank spaces in Account maintenance window
3. GP Standard software license. If you are on Ctree or Pervasive, your current license key will not allow you to work with Microsoft SQL Server based GP Standard. In order to get new license you should be current in Microsoft Business Solutions annual maintenance or also known as annual enhancement program. If you are current, then your Great Plains VAR should be able to obtain new GP Standard key from Microsoft
4. Upgrading to current GP version. At this time it is version 10.0. From 7.5 we recommend you two steps: 7.5->9.0 and 9.0->10.0. Please, do not forget to apply service packs when you are doing each step
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
