Microsoft Great Plains ERP or new name Dynamics GP requires precise approach in implementation, user training, initial data migration and conversion, reporting, EDI and possible customization and interface modification. Microsoft Dynamics GP consultant selection is often critical to the implementing process success. In this small publication we would like to review data massage and conversion recommendations and scenarios:
1.Data Export from your legacy ERP or accounting application. There are few possibilities, and this is dependent on your legacy MRP application platform. Usually old ERP allows you to export data in tab delimited or comma delimited text file format. However cheap small business accounting packages might be lacking export tool, and if this is your case, you should export data in the form of reports. Reports could be further massaged in Excel and then you should come to the next step Great Plains Integration Manager data import
2.GP Integration Manager. IM can read text files as well as ODBC data sources. If you are sort of giving up in using IM and thinking that it doesnt work in your case you should read samples of advanced ODBC data sources. Advanced ODBC allows you to create advanced SQL Select, group and other aggregated statements. On MS Windows 2003 Server as well as on Vista or Windows XP workstations Microsoft Text driver has known issues and if you think it doesnt do the job we recommend you to call us in order to help you with advanced ODBC driver configuration
3.Excel data massage techniques. Here you typically process your initial export text file and make needed corrections
4.Data Conversion levels. Ideally you should import GL Chart of Accounts, Master records, such as Customers, Vendors, Employees, then you import your work transactions. In some cases you need to keep restricted number of open sales invoices while you are awaiting collection or payments
5.Great Plains Historical Data Conversion. This is what we do not really recommend or at least try to avoid that. GP History conversion is really tough process. Plus you will likely going to get data integrity issues while doing future check links in GP
1.Data Export from your legacy ERP or accounting application. There are few possibilities, and this is dependent on your legacy MRP application platform. Usually old ERP allows you to export data in tab delimited or comma delimited text file format. However cheap small business accounting packages might be lacking export tool, and if this is your case, you should export data in the form of reports. Reports could be further massaged in Excel and then you should come to the next step Great Plains Integration Manager data import
2.GP Integration Manager. IM can read text files as well as ODBC data sources. If you are sort of giving up in using IM and thinking that it doesnt work in your case you should read samples of advanced ODBC data sources. Advanced ODBC allows you to create advanced SQL Select, group and other aggregated statements. On MS Windows 2003 Server as well as on Vista or Windows XP workstations Microsoft Text driver has known issues and if you think it doesnt do the job we recommend you to call us in order to help you with advanced ODBC driver configuration
3.Excel data massage techniques. Here you typically process your initial export text file and make needed corrections
4.Data Conversion levels. Ideally you should import GL Chart of Accounts, Master records, such as Customers, Vendors, Employees, then you import your work transactions. In some cases you need to keep restricted number of open sales invoices while you are awaiting collection or payments
5.Great Plains Historical Data Conversion. This is what we do not really recommend or at least try to avoid that. GP History conversion is really tough process. Plus you will likely going to get data integrity issues while doing future check links in GP