Data conversion project might be neglected in its planning phase and this fact might lead to implementation going over budget and even the desire to seek for second opinion.
Let’s review general recommendation of data migration theory for Corporate ERP application and some practical advises on planning the way out of crisis. This small publication is intended for managerial personnel and company owners and it is not really going to the technical level and might be not practical to programmer. Initial highlights are always good to review to avoid the issues in design and planning which could be traced down the road:
1. Corporate ERP and Data Conversion Theory. If your newly selected ERP or accounting application doesn’t have migration tool from original software vendor then data import scope should be limited. Of course it is impractical to manually key in thousands of customers, vendors, associated addresses and inventory items. However historical invoices, purchase orders and payments from customers and to vendors should be analyzed on the subject of feasibility to be transferred from legacy system to the new one. Each ERP system is unique and pushing historical documents typically means reprocessing them in the new system by imitation of being entered and then posted all the way through General Ledger and updating business partner summaries. General wisdom recommends you to keep old accounting available for possible future and transition period queries from vendors, customers and sales people
2. ‘Well but in our opinion it is good idea to move maximum number of documents from legacy to the future ERP. What is wrong about our motivation and desire to cut off old system completely?’ Well it is mathematically possible to convert ‘everything’ but the cost might be huge and non-predictable at the time of estimation. When conversion is in progress multiple cycles might be expected and this process is something that could delay the date of going into production with the new system. Is it a big compromise for you to keep old accounting application up and running for data inquiry only? If not then you can save implementation tame and budget and keep good relations with your original SAP B1 reseller
3. Facing inevitability of historical data conversion. You might have no choice in the scenario where your old accounting application was licensed as subscription and if you stop it then you lose the way to login user interface. We saw several examples of subscription casing the problem in the future and we would like to recommend checking future access possibilities to your documents in such new schemas as Cloud. If your subscription expires in few months consider the option to export your old accounting tables into something neutral such as Microsoft SQL Server or MS Access DB format. If you have a database replica then the historical documents are there and if required you can request document info pulling procedure from your IT department
4. Data Transfer Workbench. Historical data conversion typically has huge number of documents to import. SB1 consultants are trained to use CSV or often referred as Excel templates to be filled in and then migrated. In the case when you have to import several hundred thousand or over a million rows Excel might be not the tool to do the job. We found it more useful to connect in DTW to ODBC data where you can expose something more powerful like SQL View for example. Workbench is pretty simple tool and its logic is straightforward and it recognizes CSV templates format as preferred. This is why you have to imitate Excel template format in your view select statement including column headers
5. Please call us 1-866-304-3265, 1-269-605-4904 (for international customers, where our representatives pick up the phone in Naperville and St. Joseph, MI call center). help@efaru.com. We have local presence in Chicagoland, Southern California, South West Michigan, Houston and Dallas areas of Texas. We serve customers USA, Canada, Mexico and Brazil nationwide and internationally via web sessions and phone conferences (Skype is welcomed). Our consultants speak English, Spanish, Portuguese, Russian and Chinese. One of our experiences is international Corporate ERP and Consolidated Financial reporting
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
