Great Plains eEnterprise Upgrade Notes

When Microsoft acquired Great Plains Software, eEnterprise was transformed into Microsoft Great Plains Professional: versions 7.0 and 7.5, later on renamed into Dynamics GP Professional: versions 7.5 (Dynamics family was introduced in September 2005), 8.0, 9.0 and current version 10.0.  This historical excurse should define the upgrade path for eEnterprise.  Let’s briefly review the options and scenarios:

1. eEnterprise was MS SQL Server application.  You are more likely on Microsoft SQL Server 7, if you still use eEnterprise.  Please note that earlier versions of Dynamics C/S+ were available on Btrieve and Ctree/Faircom, however eEnterprise was targeted to mid-size and large businesses and so MS SQL Server only option was reasonable: SQL Server 6.5 and 7.0.  Considering SQL Server DB platform, the upgrade process doesn’t require migration from legacy DB platforms
2. eEnterprise to GP Professional upgrade path.  If you own eEnterprise and are current with Microsoft Business Solutions annual enhancement program (which is not necessary the case, as the question is why you didn’t upgrade since 2001?), then with some exotic exceptions, you should be owning GP Professional licenses for current version 10.0, and from business relations with Microsoft standpoint, there are not objections and you are good for the upgrade.  If you are not current with Enhancement program, then you need to be reenrolled – this will give you access to new version, contact your MBS VAR of records or if you are not sure who they are, you can call Albaspectrum
3. Upgrade Scenarios.  Assuming that you are on eEnterprise version 6.0.  You will need to upgrade to GP Professional 7.5 first, then to GP 9.0 and apply 9.0 Service Pack 2, and at this point you can go to the finish – GP 10.0
4. Third Party modules.  GPS and Microsoft Business Solutions as its successors, opened Great Plains platform to ISV partners for beefing up GP business logic and creating industry verticals.  In the time of eEnterprise the programming language of choice was Great Plains Dexterity.  If you have GP ISV modules: Intellisol, Mekorma, Dynamics.Zip, Avalara, and others or if you have Dexterity modules developed specially for your company – you will need to contact ISV or theirs successors, plus hire Dexterity experts to help you with in-house modification upgrade
5. Walking away from eEnterprise.  If you are migrating to JDEdwards, PeopleSoft, Oracle, or other ERP application, you need help with exporting eEnterprise master records and transactions (work, open and historical) to DB format, convenient for new MRP programmers – typically tab delimited text files, Microsoft Access DB, or MS SQL Server custom database