[Monzer Osama]

Microsoft Dynamics GP, as Great Plains was renamed and associated with Microsoft Dynamics family of products, created by joining together with future synergy and integration purposes: Navision NAV, Axapta AX, Solomon SL, and Dynamics CRM, so now GP version 10 was introduced in Summer 2007 for MBS partners and then for customers. Version update will be the next step to be offered to GP customers. You should understand your ERP upgrade path and associated investment and possible risks. In this small article we would like to give you initial start for upgrade process and have you to think about it and do your homework

1. Upgrade Path. MS Dynamics version update utility works by recognizing your current build and checks if it has upgrade path for your current version. If it doesn’t have it – it can not upgrade. Currently (no service packs were yet released for 10.0), GP 9.0 upgrade works if you applied SP 2. It also can initiate upgrade in you are on GP 8.0 with SP5. If you are on 9.0 without SP applied, consider to apply SP 2 and then move on to upgrade to GP 10.0. If you are on newer than 9.0 SP 2 build, you should wait GP 10.0 SP 1 to be released later in 2007

2. Older versions. In you are on version, earlier than 8.0, such as 5.0, 5.5, 6.0, 7.0 or 7.5, you should consider updating to version 8.0 or 9.0 first, and then immediately update to version 10.0, assuming you are considering the contents of the paragraph above

3. Pervasive SQL and Ctree/Faircom DB platforms. Microsoft Business Solutions decided to terminate support to these non-Microsoft DB platforms in December 2004. If you are still on these legacy platforms, you should consider migration. Migration is available for old versions up to 7.5. The technology of migration is straight forward – Dexterity module which allows you to connect old DB with newly created MS SQL Server Dynamics GP databases. Professional consultant help is highly recommended as migration has multiple what-ifs scenarios and may lead you to confusion

4. Third Party modules upgrade. If you deploy third party GP satellites, such as Mekorma, Avalara, Wennsoft, Horizon Manufacturing, etc. – you should check with them on the availability for the upgrade path for their modules and if required - wait

5. Custom Technologies upgrade. Among customization technologies, you should identify if you deploy one of these: Microsoft Dexterity (former name is Great Plains Dexterity – chunk files, DYNAMICS.DIC with source code in needed to upgrade), VBA/Modifier (this is legacy OLE related technology, you should have DYNAMICS.VBA dictionary with VBA scripts in it), Integration Manager (you should find on your network IM.MDB file, where integrations metadata resides). eConnect eCommerce and GP Business Portal Upgrade paths are complex and require separate consideration outside of this article