Dynamics GP Upgrade Scenarios Brief Overview

We also assume that the reader is not Dynamics GP consultant (as consultants have access to Dynamics GP technical upgrade guides and steps), that you are IT manager or Controller:
1. Do you own new version reg key?  Answer might be decisive in the dilemma resolution.  If you are current in Microsoft Business Solutions GP annual enhancement program, or if you are not sure - do you remember when you paid last time to MBS directly (they send annual enhancement Quote to each current customer) or via your Dynamics GP Partner?  If that even is in really in history, then likely that you are not current in this program and you will need to reactivate your plan, or be reenrolled.  If you are not current in program, you do not have new version reg key.  If you are current - you have automatic access to your reg key via Customer Source
2. Pluses of upgrading to new version.  If you are Microsoft IT shop, you may like the idea to be on the newest trends.  Safe upgrade strategy in our opinion is upgrade to newest version, when First (or maybe Second) Service Pack is released.  Newest version is typically better supported as your Dynamics GP Partner usually has GP Consultants trained in new functionality, plus new customers implement current version, so consultants have more experience with known issues and their fixes
3. Some concern to new version upgrade.  Corporate ERP application upgrade is "The Project".  Each project requires budget, resources allocation, it has some risks, so in other words this project should be respected.  If you think that you did upgrade just a year or couple of years ago, you may decide that your system may work OK another couple of years.  And this approach is respected, it is known as "Skipping Over One Version" in Dynamics GP Update strategies.  And, usually you see Corporate ERP Vendors, such as MBS, they officially support the latest version (currently 10.0) and one or two previous versions (at this time only version 9.0, support for 8.0 and earlier is no longer available).  So, approach when you skip one upgrade should be still OK
4. If you are on old archaic version: 8.0, 7.5, 7.0, 6.0, 5.5, 5.0, 4.0 (versions 7.5 and earlier were available on Pervasive SQL 2000/Btrieve and Ctree DB platforms), or even Great Plains Accounting for DOS or Windows.  If this is your case - the biggest risk, in our opinion is lack of support from Microsoft (MS acquired Great Plains Software earlier in 21st Century ).  You can still find old Dynamics GP consultants, who may remember how to support your version.  However if you plan to grow your business, there is no way for you to purchase new modules for Great Plains (until you reenroll your organization into Dynamics GP annual enhancement program, see #1 - this might be very costly option, we saw customers, who simply decided to repurchase their Dynamics GP from MBS as if they are new customer)
5. Upgrade Path.  Exact upgrade path is better to discuss, knowing your current version, if you have Dynamics GP ISV Add-Ons (Wenn Soft, Mekorma, Intellisol, etc.).  Let us give you hypothetic path, when customer upgrades from Great Plains Accounting for DOS 9.2 to Dynamics GP 10.0: GPA9.2->GPA9.5; then migration GPA9.5->Microsoft Dynamics GP 7.5 on MS SQL Server 2000; GP 7.5->9.0 and then GP9.0->10.0.  If you have Add-ons, which are not longer in wide use for modern version (one of them is Intellisol Advanced Purchase Order Processing), you need to consider migration scenarios (Intellisol APOP has migration tool to GP POP module for version 7.5).  It is also common that Dynamics GP ISV Partners have their own annual enhancement program, so check with your Add-ons provider what is the status of your account
6. Customization, Integration, Reporting upgrade.  If you have unique customizations (often programmed in Great Plains Dexterity, eConnect, VBA/Modifier, Extender, SQL Stored Procedures), custom reports in SSRS, Crystal Reports, Web Reports, ReportWriter, please talk to your original programmer, or report designer.  If these professionals are no longer available - feel free to call us for your case evaluation
7. FRx reports.  If you are updating from GP 9.0 to 10.0 - FRx is not a big concern, as you will need to apply new FRx 6.7 Service Pack (10 or 11).  If you are on older version of FRx (6.5, 6.0 or earlier) then upgrade requires following special procedure.  Older version upgrade typically have complication of moving to new Windows Server (from 2000 or WindowsNT to 2003, or 2008), where FRx Sysdata requires special redeployment steps
8. Moving GP from old Server to new Hardware.  Assuming that you are redeploying GP on SQL 2005 or 2008 from the version running on MS SQL Server 2000, and you have only one step (from GP 8.0 or 9.0 to 10.0), then you should follow reasonably simple techknowledge on GP Databases redeployment with SQL capture logins scripts.  However, if you have more than one step, be ready to have intermediary server (with SQL Server 2000 maybe), as you cannot deploy Dynamics GP 7.5 directly on MS SQL 2005
9. if you are large organization with reasonably complex GP integration with your legacy systems (Oracle, PHP/MySQL/Linux ecommerce website, EDI, etc.), you should expect additional "discovery", so this article is for orientation only
10. How to get help?  Please, feel free to call us: 1-866-528-0577, outside of USA: 1-630-961-5918 or email us help@albaspectrum.com  We are very technical and real Dynamics GP Dexterity, SAP Business One SDK programming gurus.  We have Great Plains Software Development Factory and could support unlimited Dynamics GP Customization and Programming needs.  Plus we speak English, Chinese, Spanish, Portuguese, Russian, and not only as native speaking sales folks, but as real technical consultants.  If you prefer skype: albaspectrum