Data migration in a bloody enterprise: what to analyze, so as not to overwhelm the project

Data migration in a bloody enterprise: what to analyze, so as not to overwhelm the project 3r3r1314.  
3r3r1314.  
A typical system integration project for us looks like this: the customer has a wagon system for customer accounting, the task is to assemble customer cards into a single database. And not only to collect, but also to clear from duplicates and garbage. To get a clean, structured, full customer cards. 3r3r1314.  
3r3r1314.  
For beginners, I will explain that the migration goes according to the following scheme: 3r31316. sources → data conversion (meets 3r314. ETL 3r3131318. or 3r3r166. bus 3r31318.) → receiver 3r31319. . 3r3r1314.  
3r3r1314.  
On one project, we lost three months simply because a third-party integrator team did not study the data in the source systems. The most annoying that this could have been avoided. 3r3r1314.  
from the vacancy page on hh.ru . [/i]
+ 0 -

Add comment