Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
Yes I would recommend to move transactional data if ERP system allow system down time
This can be done by using coupling techniue.
For a running business, the thought of adopting a newer database will be with an intent to eliminate some fundamental application or database issues that is hogging the enterprise. The company will not do away with he existing enterprise data. During the phase of feasibility analysis itself, an effort to look at the risks of loosing data will always will be assessed and mitigations will be ascertained. If possible, it is always good to migrate the existing transactional data in the base. As a matter of fact the selection of new database will be finalized only after consideration of the compatibility with existing database platform. In the event of a compatible product is not found, it is always better to start a new database, by maintaining the old database as well for the required amount of time mandated by the business management. The modern database has tools for migrating data from any kind of database, maybe some data cleaning and normalization maybe required to be done.
Migration of data is very difficult process from one software to another because both the software may be made on different platforms with different computer languages, if data migration is possible in the same manner as we need then we should go migration rather than fresh data base and opening balances and
if data migration is difficult and we not sure about it then we should definitely go for fresh data base and opening balances.
Migration of data will consume less time.
