Towards the Industrialization of Data Migration: Concepts and Patterns for Standard Software Implementation Projects

Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5565)


When a bank replaces its core-banking information system, the bank must migrate data like accounts from the old into the new system. Migrating data is necessary but not a catalyst for new business opportunities. The consequence is cost pressure to be addressed by an efficient software development process together with an industrialization of the development. Industrialization requires defining the deliverables. Therefore, our data migration architecture extends the ETL process by migration objectives to be reached in each step. Industrialization also means standardizing the implementation, e.g. with patterns. We present data migration patterns describing the typical transformations found in the data migration application domain. Finally, testing is an important issue because test-case based testing cannot guarantee that not a single customer gets lost. Reconciliation can do so by checking whether each object in the old and new system has a counterpart in the other system.


Data Migration Patterns ETL Standard Software ERP 


  1. 1.
    Gabriel, C.: Plattform-Wechsel: Parforce-Übung mit weitreichenden Folgen, Schweizer Bank, Zürich (June 2007)Google Scholar
  2. 2.
    CMMI for Development, Version 1.2, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA (2006)Google Scholar
  3. 3.
    Fowler, M.: Patterns of Enterprise Application Architecture. Addison-Wesley Longman, Boston (2002)Google Scholar
  4. 4.
    Fraternali, P.: Tools and Approaches for Developing Data-Intensive Web Applications: A Survey. ACM Computing Surveys 31(3) (September 1999)Google Scholar
  5. 5.
    LeanStream® – COMIT Implementationsmethodik, V. 3.0, Comit AG, Zürich (2007)Google Scholar
  6. 6.
    Haller, K.: Datenmigration bei Standardsoftware-Einführungsprojekten. Datenbank-Spektrum 8(25), 39–46 (2008)Google Scholar
  7. 7.
    Haller, K.: Data Migration Project Management and Standard. In: 5th Conference on Data Warehousing (DW 2008), St. Gallen, Switzerland. Lecture Notes in Informatics (2008)Google Scholar
  8. 8.
    Chaudhuri, S., Dayal, U.: An Overview of Data Warehousing and OLAP Technology. SIGMOD Record 26(1), NY (1997)Google Scholar
  9. 9.
    Wu, B., Lawless, D., Bisbal, J., et al.: The Butterfly Methodology: A Gateway-free Approach for Migrating Legacy Information Systems. In: ICECCS, Como, Italy (1997)Google Scholar
  10. 10.
    Morris, J.: Practical Data Migration. British Computer Society, Swindon (2006)Google Scholar
  11. 11.
    Data Migration – The Endava Approach, White Paper, London (2006)Google Scholar
  12. 12.
    Burry, C., Mancusi, D.: How to plan for data migration, Computerworld, May 21 (2004)Google Scholar
  13. 13.
    Hudicka, J.R.: An Overview of Data Migration Methodology. Select Magazine, Independent Oracle Users Group, Chicago, IL (April 1998)Google Scholar
  14. 14.
    Willinger, J., Gradl, J.: Data Migration in SAP R/3. Galileo Press, Boston (2004)Google Scholar
  15. 15.
    Anavi-Chaput, V., et al.: Planning for a Migration of PeopleSoft 7.5 from Oracle/UNIX to DB2 for OS/390 (Red Book), IBM, Poughkeepsie, NY (2000)Google Scholar
  16. 16.
    Manek: Microsoft CRM Data Migration Framework (White Paper), Microsoft Corporation (2003)Google Scholar
  17. 17.
    Crreira, P., Galhardas, H.: Efficient development of data migration transformations. In: SIGMOD, Paris, France (2004)Google Scholar
  18. 18.
    Rahm, E., Bernstein, P.: A survey of approaches to automatic schema matching. VLDB Journal 10, 334–350 (2001)CrossRefzbMATHGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  1. 1.COMIT AGZürichSwitzerland

Personalised recommendations