Microsoft Great Plains Implementation checklist

By: Andrew Karasev

We will review generic ERP application implementation checklist first and then we will go down to specifics:

  • Data conversion and massage.  Light approach, when you enter initial balances or more advanced way, when you pursue historical data conversion – these are typical scenarios in ERP upgrade, and you will see these decision making requirements implementing all ERP systems
  • Modules selection.  This decision making process should be the balance between standard MRP modulated model and specific processes automated in Microsoft Dynamics GP.  GP fits to generic accounting: GL, AR, AP, INV, FDA, POP, SOP, discrete manufacturing, field service, non-profit and government organizations
  • Platform Technology.  Here we see pretty successful and rapid evolution.  Historically Great Plains Software Dynamics was GPS Dexterity written application.  Now Microsoft is moving this ERP to MS office stack and enables GP to MS Visual Studio developers via such tools as Extender, eConnect and even Microsoft CRM SDK development and Microsoft CRM integration module with Great Plains
  • Integration Scenarios.  eConnect is probably the key player, however we should mention GP Integration Manager module, which in turn is under performance improvement process (deploying more eConnect logic and technologies).  Then please consider integration options via MS SQL Server Stored Procedures.  Legacy MS Dexterity also can do the job, however you should consider Dexterity fate and the availability of Dex programmers on the market
  • Microsoft Dynamics GP VAR pool.  Yes, when you plan to implement GP for your company, you should select MBS VAR or partner who will be doing implementation for you and who will be your representative with Microsoft Dynamics subdivision

Microsoft
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 

» More on Microsoft