Microsoft Dynamics GP data migration – overview for programmer

As simple if might look – this approach requires close familiarity with GP architecture, its Microsoft Dexterity database features (such as DEX_ROW_ID).  So, here we would like to orient you in which set of tools should be tried first, which the second and the third.

• Data export.  In the case of Accpac you have either Pervasive SQL 2000 or MS SQL Server database, so, you can pull data from Accpac via ODBC connection.  You may create Linked Server from MS SQL Server Enterprise Manager – this will let you manipulate Accpac Pervasive SQL data directly from MS SQL Server.  In the case of MAS 90 you can use reports and send them into text files and then import them into MS SQL Server custom database
• Period Balances approach.  In this case you decide that in GP you will have period balances in GL for each month of the year plus for the beginning of current year.  You will need to prepare General Ledger transactions for year opening and each month
• Master Records migration.  In order to migrate such records as customers, vendors, accounts, employees, addresses, we recommend you first to consider GP Integration Manager.  If IM is not available in your case, you can try to migrate data via SQL scripting directly into RM00101 – customer master table, PM00200 – vendor master table, etc.  Prior to SQL migration – make DB backup in case if you need to roll back.  When you try one step (like customers), open GP workstation and run check links: File->Maintenance->Check Links
• Historical Data migration.  We discourage you from doing historical transaction migration to GP, instead we recommend you to keep your old Accpac or MAS 90 for inquiry only.  If history migration is absolutely necessary, consider first importing transactions via IM and then post them in modules (if you plan initial balances approach, see above, in posting settings unmark Post to GL: Tools->Setup->Posting select series and origin).  If IM is not available, you should never run Check Links against your historical migrated data in the future