From time to time, you must move your ERP business application to another server, often because of hardware problems, or obsolescence of the old server. Let the different situations and migration scenarios, including the recently released Dynamics GP 2010 and older versions: 10.0, 9.0, 8.0, 7.5, 7.5 and earlier, including the Great Plains on Pervasive SQL Select Server 2000/Btrieve Ctree or Great Plains Accounting for DOS or Windows:

1. Great Plains Dynamics and Microsoft Dynamics GP eEnterprise on Microsoft SQL Server 2008, 2005, 2000, 7.0 or 6.5. You need a new server with Microsoft SQL Server have made installed version compatible with your application within the Great Plains. For example, if you click on Dynamics GP version 8.0, the options would be SQL 2000 or 2005 (for MS SQL Server 2005, you must have applied Dynamics GP Service Pack used). If you are from the old version, usually MS SQL Server 2000 should be fine (for GP 8.0, 7.5, 7.0, 6.0, 5.5, 5.0 and earlier versions, we recommend , hold the SQL version you present). Please also note that for Microsoft SQL Server 2000, it is advisable to deploy Windows Server 32 Bit (You can try the test on 64-bit Windows, but there may be areas of conflict). Generally, you want to save on the dynamics and all your corporate databases, and then again on the new SQL server, and the transfer of security, with DTS or run scripts for Dynamics GP recommended transfer of the safe use, contact your Dynamics GP VAR or directly from the customer source. If your old server is only limited storage resources or simply overwritten, you can try the only SQL database files (Log files are not really necessary) and fit better on the new server (flexibility in general, if the SQL books online and use the system stored procedures, compared to SQL Enterprise Manager wizard)

2. Select Dynamics GP or Great Plains on Pervasive SQL Server. Here is the file transfer is easy as you need to find the folder with files Btrieve Dynamics (file system file systems, databases analog dynamics), and each folder has subfolders companies in the modules: GL, AP, payroll and payroll, AR, etc . difficult part of the procedure is to install Pervasive SQL Server 2000 (we recommend it with Service Pack 3 or 4), then change the default settings in the Control Center if necessary (see Pervasive SQL recommended settings for Dynamics GP to source client or simply call Dynamics GP Partner for details). If you buy a new server and operating system for Great Plains on Pervasive SQL 2000 deployment, please note that you install on Windows Server 2003 or even 2007 (including SBS) but we need the 32-bit version (you will not able to install Pervasive SQL 2000, you officially own version) on Windows 64

3 Great Plains Accounting for DOS, Windows (Version 9.5, 9.2, 9.1 or earlier). GPA is on Btrieve and if you are moving to new servers (or single-user version of Windows workstation). If you move within the multi-user version GPA, we encourage you to shift Pervasive SQL Server 2000 with parameters, similar to Great Plains on Pervasive SQL Select (parameters can be found via partner or customer source source). Please make sure your new server is Windows 32-bit version. When Great Plains Accounting for DOS or Windows for the future review low as possible, we recommend Windows XP to use workstation (we saw the case, if installed Win XP with multiple applications and powerful anti-virus program GPA, Windows blocks away, started, GPA for DOS but was still viable). The recommendations outlined should work, although if you of Novell, Windows NT 4.0 or earlier

4 feet. Great Plains Accounting DOS, Windows, Macintosh, Great Plains on Pervasive SQL 2000 Select or Ctree. Support for this archaic versions of remote web sessions, phone conferences recommended. You can try to find a local support, but could be due to the number of local customers GPA active-site support of poor quality or
learning curve 5. For additional assistance, please call 1-866-528-0577, 1-630-961-5918, 1-269-605-0330 Michigan or e-mail help@albaspectrum.com We are available to USA, Canada, National and to serve internationally. Local service in Chicago, Southern California, Western Michigan, Houston, TX

SQL 2005, the audit