|
|
Great Plains Technical Consultant News: Dynamics GP Data Migration - Alba Spectrum
Alba Spectrum
If you are on the data export from legacy accounting system, data massage in Excel or SQL Server, and data conversion/migration to Microsoft Dynamics GP, we would like to give you some technical recommendations, based on our 15 years Great Plains Consulting practice. Plus, in our opinion data conversion recommendations or say stronger principles are applicable to other ERP and MRP systems:
1. Master records migration. This is likely the required step, where you move your GP Chart of Accounts, Customers, Inventory Items, Bills of Materials, Vendors, Employees, etc. In GP these are so-called master records. The simplest way is Dynamics GP Integration Manager. If you only need GL accounts, you could try direct SQL Insert into GL00100 and then run Check Links on Account Master tables cluster. In all other cases we do not recommend direct SQL insert, as it is not guaranteed that business logic required dependencies will be restored by Check Links routine
2. Beginning Balances. When you are done with master records migration, we recommend you to keep historical transactions lookup in your old accounting system: Peach Tree, MYOB, QuickBooks, or whatever it was. In this case, you launch New Year or new fiscal period in Great Plains by entering beginning balances to each GL account in one General Ledger transaction, review and post it on the day of the first date in the new fiscal period. Preferred way it to start GP in production on January 1st, or whatever is your first day of your Corporate ERP fiscal year
3. Open AR, AP. We recommend you to import via Integration Manager unpaid AR and AP, then post them and wait for payments to be issued (AP) or received (AR and SOP)
4. Historical Data Conversion. We recommend you to consider avoiding it and instead keep legacy accounting open for inquiries. If this is absolutely impossible, consider creating historical company in GP, closed for new transactions and then move historical records there, here you can use SQL Insert statement. Please, never run check links in this historical company, as your historical data migration will likely be inconsistent, but good for querying. Another way, which might be taken - import all your historical transactions via Integration Manager and then post them by historical dates. The pitfalls of this approach might be the problems with historical data export quality and IM performance
5. If you have concerns, please give us a call: 1-866-528-0577, help@albaspectrum.com
Andrew Karasev, Alba Spectrum, help@albaspectrum.com http://www.albaspectrum.com 1-866-528-0577. Please visit our info portal Pegas Planet: http://www.pegasplanet.com Local Service in Chicago, Atlanta, San Diego, Los Angeles, Orange County, Houston. We also have SAP Business One Software Development Factory and SB1 Technical Support Call Center, serving USA country side businesses and internationally: Canada, Brazil. Illinois practice: Naperville, Aurora, Plainfield, Marseilles, Ottawa, DeKalb, Springfield, Oakbrook, Glenn Ellyn, Wheaton, Bolingbrook, Romeoville, Lisle, Melrose Park, Brookfield. San Diego and LA practice: Rancho Bernardo, Oceanside, Poway, Long Beach, Irvine, Mission Viejo, San Marcos, Carlsbad, La Jolla, Escondido. Houston Practice: Dallas, Galveston, Sugar Land, Pearland, Katy, Pasadena, Rosenberg, League City, Galena Park
Author Site
6/8/2009
|
|
