rsion Upgrade Dynamics GP What to Expect and How Make it Smooth

Typical customer profile is organization, which has GP in production in release 10.0 or 9.0.  We are saying that this is typical, because the majority of the active customers have active GP consulting organization support and active annual maintenance contract with Microsoft Business Solutions.  If you are in that pool, you should expect one step upgrade.  If you are trying to reactivate your legacy Great Plains Dynamics and update it all the way to the current version (it is 2010, also referred in tools, such as Dexterity as 11.0 – we are writing these lines in April of 2011), expect two steps or more.  Technically you can make it all the way from such old ERP application as Great Plains Accounting for DOS, Windows or Mac (we have limited experience working with Macintosh GPA).  If you are on Great Plains Select on Pervasive SQL 2000/Btrieve or Ctree database platform you should also expect migration from Pervasive/Ctree to MS SQL Server.  If you are currently deploying Intellisol Advanced Purchase Order Processing – there is migration tool to GP POP module.  This paper is intended for Controller or business owner with some technical details (these could be discussed with your IT staff):

1. Upgrade Technology.  It has two major steps: Server and Client.  Server update deals with Dynamics (this is sort of system database) and each company database to convert each table (which changed its structure), SQL Stored Procedures (it simply drops and recreates each one), plus other server side objects.  Client update is usually more diversified.  It includes GP workstation (with Reports.dic, Dexterity, VBA, VST, Extender customizations), FRx (or Microsoft Management Reporter), Integration Manager (typically eConnect based integrations require attention, as this technology seems to change its high level wrappers every few years), SSRS or Crystal Reports.  Server side upgrade process seems to be very solid (we recommend you wait until at least first Service pack is released, as manufactured DVD release triggers large number of pilot conversions, and these customers are reporting their problems, and these problems are fixed in the Service Pack).  If Server Side conversion fails – this might be an indication that your tables have some inconsistency (and you need data cleanup – subject to separate discussion).  Client side is more complex, as here you have multiple tools, add-ons and modules

2. How to Facilitate the Whole Process?  We recommend you to have two phases: Test Upgrade (on the new Windows Server, which should become production one in the second phase) with one or several dedicated user workstations and following Production upgrade phase.  Test phase should allow your users to print our all the critical reports (FRx, MMR, SOP Invoices, PM Checks to name few candidates).  Consider this scenario.  On Friday you launch test update phase, Server side is done by the end on the day on Sunday.  On Monday your accounting team begins QA and verifies that all the reports resemble the same results by the end of Wednesday (you disable all the data entry into Great Plains since Saturday).  If your management team approves the QA then data entry into the new system is open on Thursday morning.  We recommend you to book your consultants to be onsite (or on call) the whole week in advance, as new release user interface and possible issues should be resolved in a matter of hours, not days

3. Technology Trend Considerations.  This Corporate ERP application resides in Microsoft SQL Server and it has inevitable dependency on SQL Server technology progress.  MS SQL Server 2008 is recommended for hosting in Windows Server 2008 R2 64 bit.  There is the trend to accept such new tools as SSIS (SQL Server Integration Services) and deemphasize such older traditional technologies as Linked Server (which you could use historically in such constructions as SQL Triggers, Cross Platform Stored Procedures).  SSIS now has such predefined connections (drivers) as Oracle, SAP, Sybase (making integrations easy between Microsoft and non-Microsoft leading DB platforms)

4. FRx with its 64 bit platform dilemma versus Microsoft Management Reporter.  Well, obviously if Microsoft decided to make a switch from FRx (this is Financial Reporting tool for P&L, Balance Sheet, Statement of Cash Flow as well as the Consolidated versions of these) to Management Reporter (which seems to be very similar to FRx, but works on 64 bit Windows and opens additional opportunities, such as enabling report generation over the internet access or VPN) – FRx will go away cleaning the path for MMR.  However at this time, the year 2011, we feel that MMR is too new and doesn’t have enough QA and Service Packs released (in the case of Management Reporter they are named Functional Packs)

5. Some notes on MS SQL Server 2008.  Due to the security concerns, whatever is not required by basic SQL Server functionality is disabled by default.  You as DBA can open the functionality (usually by calling sp_configure procedure, please see books online for details).  Also in 2008 you find such new technologies as DB Mirroring (alternative to SQL Cluster, Log Shipping, Replication)

6. Small Business Financials migration to GP. This small business ERP line was terminated and the final version was 9.0.  Previously MS SBF was good alternative to migrate from Great Plains Accounting for DOS, Windows or Mac.  We do not have exact idea why Microsoft terminated this small business accounting package.  You may decide migrate to Dynamics GP Business Ready Business Essentials (Advanced Business Edition is for larger companies).  The other options would be exporting SBF tables into CSV or tab delimited text files, or even MS Access DB to let you import them into newly selected Small Business ERP (Peach Tree, QuickBooks, MYOB, SAP Business One, Accpac or another package)

7. For further information, please call us 1-866-304-3265 or email help@efaru.com.  We provide service in USA and internationally via web sessions.  Local service is available in Chicago, Los Angeles, San Diego, Houston, Dallas, West Michigan: St Joseph, Benton Harbor, Kalamazoo, Holland, Saugatuck, New Buffalo, Muskegon