If you have solid Great Plains VAR support from your local partner or certified consultant, then this routine should be entrusted to their hands and you should not worry about it.
However if you are without support, typically when you are using one of historical Great Plains versions: 7.5, 7.0, 6.0, 5.5, 5.0 or even GP 8.0 and you are not sure who is your current Great Plains Partner, then you need to local Microsoft Dynamics GP consultant for helping you in Great Plains migration from one server to another. Let’s consider migration scenarios:
1. Great Plains on MS SQL Server 2000 (or SQL Server 2005). In the case of being on MS SQL 2000, you need first to understand, that you should move it to exact blend of SQL Server. Especially it is important if you are on version 7.5 or earlier – these versions were sensitive to SQL license. This means that if you are using MSDE, you can’t redeploy Great Plains on new server, where you load MS SQL 2000 Standard, for example. If you have SQL DBA in staff – you can ask her or him to simply transfer all the databases, users and security to new server. If you don’t have DBA, then you should have your GP consultant to use GP users capture and transfer scripts, available from Microsoft Business Solutions Partner or Customer Source (if you are not current with GP annual enhancement program, likely that your customer source expired too)
2. Great Plains on Ctree. This version is easily transferrable to new server, assuming that you are on GP 7.5 or 7.0. You should install Ctree default GP on the new server and then copy over files from your old server. You will need help with Location Translation, when you first launch Great Plains. You can call us to get this help
3. Great Plains on Pervasive SQL. You should have Pervasive SQL CD, and you install Pervasive server first on the server. If you plan to use GP on Pervasive as Single User Workstation, you do not need to install Pervasive SQL Server there. Then simply repeat steps described in #2
4. Great Plains Standard on MSDE. You follow the same recommendations as in #1, however we recommend you to use Microsoft SQL Server 2000 client tools – SQL Enterprise Manager and Query Analyzer. You can probably do the work with DOS based tools available for MSDE instead, however it is more difficult
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
