In most organizations information are frequently added, deleted or updated to and from the CRM database. During these operations there are chances for alteration in entering the data into different fields and structures. The relation between the fields also sometimes varies depending upon the business needs. The customer data are gathered from disparate data sources or shared between different departments. Minor errors or problems can arise during these operations. If these problems are discarded by just giving a patch work and allowing the database to continue its operation can lead to a dangerous situation.

The danger occurs when large data integration is carried out. It is because the accumulation of these minor problems will become a stumbling block for data integration. There are some common factors that the organization or individuals refuse to give importance which can finally lead to the whole project crash.

They are the lack of proper maintenance of the application; due to the sudden move of people responsible for maintenance, and outsourcing of the application to a new company with different priorities. Another danger sign for data integration disaster is the emergency update of the application without proper documentation and finally losing the needed files. The problem may also arise when there is no proper entry of data, policies, and lack of management of database.

Over the time, the mishandling of these problems can eventually degrade the quality of the database which can finally end up in a major mishap. The seriousness won’t strike the organization until an attempt for major integration occur causing the project to crash. This is a very disastrous state which is often led due to the lack of proper knowledge about handling the whole system.