RAJA BALWANT SINGH COLLEGE

BICHPURI CAMPUS
AGRA.

A
SYNOPSIS
ON
DATA MIGRATION
By

Palak Agarwal Rashi Saxena Tarun Gupta

(0700410052) (0700410066) (0700410082)

Submitted in Partial Fulfillment of the

Requirement for the degree of
Bachlor of Technology (B.Tech)
 TABLE OF CONTENTS

 Abstract

 Introduction

 Problem Statement

 Literature Survey

 Plan of work

 Conclusion & Future work

 ABSTRACT

Data Migration is application software which provides user an easier

approach to convert many files of one of the database into other just in
one click.

This software is used to import records from one database to

another totally different database (ex. Access to SQL) without make
changes to their schema. Data can be transfer to same system as well
as to other system connected to the same LAN or another.

This project uses basic concept of Data Base Management System

(DBMS) and Computer Networks.

Tools used:

Front end : DotNet (Visual Basic)

Operating System : Windows XP/7

Software : DotNet framework2008

Note: Visual Basic is used just because it is easy to code complex

programming in modular form and having advance graphical tools.
 INTRODUCTION

Data Migration is the process of transferring data between storage

types, formats, or computer systems. Data migration is usually
performed programmatically to achieve an automated migration,
freeing up human resources from tedious tasks. It is required when
organizations or individuals change computer systems or upgrade to
new systems, or when systems merge (such as when the organizations
that use them undergo a merger/takeover).

To achieve an effective data migration procedure, data on the old

system is mapped to the new system providing a design for data
extraction and data loading. The design relates old data formats to the
new system's formats and requirements. Programmatic data migration
may involve many phases but it minimally includes data extraction
where data is read from the old system and data loading where data is
written to the new system.

Data migration is the process of making an exact copy of an

organization’s current data from one device to another device—
preferably without disrupting or disabling active applications—and then
redirecting all input/output (I/O) activity to the new device. There are a
variety of circumstances that might cause an organization to undertake
a data migration, including:
• Server or storage technology replacement or upgrade
• Server or storage consolidation
• Relocation of the data center
• Server or storage equipment maintenance, including workload
balancing or other performance-related maintenance.

Database migration

it may be necessary to move from one database vendor to another, or

to upgrade the version of database software being used. The latter case
is less likely to require a physical data migration, but this can happen
with major upgrades. In these cases a physical transformation process
may be required since the underlying data format can change
significantly. This may or may not affect behaviour in the applications
layer, depending largely on whether the data manipulation language or
protocol has changed - but modern applications are written to be
agnostic to the database technology so that a change from MySQL, DB2
or SQL Server to Oracle should only require a testing cycle to be
confident that both functional and non-functional performance has not
been adversely affected.

The process of translating data from one format to another. Data

migration is necessary when an organization decides to use a new
computing systems or database management system that is
incompatible with the current system. Typically, data migration is
performed by a set of customized programs or scripts that
automatically transfer the data.
 PROBLEM STATEMENT

Various organizations hire database professionals to convert databases

from one format to another. These professionals demand very high cost
to get engaged in the database conversion process even then some
data redundancies exist in the resultant database. In order to avoid all
these data replications database conversion software is created that
provides professional services to the users for converting databases of
earlier technology into the database of new and latest technologies in
very less time.

Database conversion utility converts data between different data

source by allowing database administrator or developer to import data
from existing database formats into the latest demanding database
formats in just one click. The database converter is a core technology
that handles the database conversion at lowest cost and offers smooth
migration path using automated technologies. Database migration
software services are expertise in accelerating the migration of the
database to the desired target database in seconds. Reliable and cost-
effective migration utility transforms database from one format into
another database format with easy to use database conversion tool of
advanced and latest technology.
 LITERATURE SURVEY

Data Migration categories

Data is stored on various media in files or databases, is generated and

consumed by software applications which in turn support business
processes. The need to transfer and convert data can be driven by
multiple business requirements and the approach taken to the
migration depends on those requirements. Four major migration
categories are proposed on this basis.

Storage migration

A business may choose to rationalize the physical media to take

advantage of more efficient storage technologies. This will result in
having to move physical blocks of data from one tape or disk to
another, often using virtualization techniques. The data format and
content itself will not usually be changed in the process and can
normally be achieved with minimal or no impact to the layers above.

Database migration

Similarly, it may be necessary to move from one database vendor to

another, or to upgrade the version of database software being used.
The latter case is less likely to require a physical data migration, but this
can happen with major upgrades. In these cases a physical
transformation process may be required since the underlying data
format can change significantly. This may or may not affect behaviour in
the applications layer, depending largely on whether the data
manipulation language or protocol has changed - but modern
applications are written to be agnostic to the database technology so
that a change from MySQL, DB2 or SQL Server to Oracle should only
require a testing cycle to be confident that both functional and non-
functional performance has not been adversely affected.

Application migration

Changing application vendor - for instance a new CRM or ERP platform

will inevitably involve substantial transformation as almost every
application or suite operates on its own specific data model. Further, to
allow the application to be sold to the widest possible market,
commercial off-the-shelf packages are generally configured for each
customer using metadata. Application programming interfaces (APIs)
are supplied to protect the integrity of the data they have to handle.
Use of the API is normally a condition of the software warranty,
although a waiver may be allowed if the vendor's own or certified
partner professional services and tools are used.

Business process migration

Business processes operate through a combination of human and

application systems actions, often orchestrated by business process
management tools. When these change they can require the
movement of data from one store, database or application to another
to reflect the changes to the organization and information about
customers, products and operations. Examples of such migration
drivers are Mergers and acquisitions, business optimization and
reorganization to attack new markets or respond to competitive threat.

The first two categories of migration are usually routine operational

activities that the IT department takes care of without the involvement
of the rest of the business. The last two categories directly affect the
operational users of processes and applications, are necessarily
complex, and delivering them without significant business downtime
can be challenging. A highly adaptive approach, concurrent
synchronization, a business-oriented audit capability and clear visibility
of the migration for stakeholders are likely to be key requirements in
such migrations.

Project versus Process

Further, it is helpful to distinguish between data migration and data

integration activities. Data migration is generally the term used to
describe a project where data will be moved or copied from one
environment to another, and removed or decommissioned in the
source. During the migration (which can take place over months or
even years), data can flow in multiple directions, and there may be
multiple migrations taking place simultaneously. The Extract, transform,
load actions will be necessary, although the means of achieving these
may not be those traditionally associated with the ETL acronym.

Data integration by contrast is a permanent part of the IT architecture,

and is responsible for the way data flows between the various
applications and data stores - and is a process rather than a project
activity. Standard ETL technologies designed to supply data from
operational systems to data warehouses would fit within the latter
category.

Migration as a form of Digital Preservation

Migration, which focuses on the digital object itself, is the act of

transferring, or rewriting data from an out of date medium to a current
medium and has for many years been considered the only viable
approach to long-term preservation of digital objects [1]. Reproducing
brittle newspapers onto microfilm is an example of such migration.
 PLAN OF WORK

Functional Requirement:
Hardware Specification:
 400Mz Processor
 512MB RAM
 Pentium 4 CPU
 80 GB HDD
 Corporate LAN and Internet

Software Specification:
 Front end: VB.net
 Operating System: Windows 2000/XP
 Software required: Microsoft Visual Studio 2008
Process Discription:

Data flow diagrams :

Level 0 :
Level 1 :

Not
successful

CONCLUSION & FUTURE WORK

Data Migration is the process of transferring data between storage
types, formats, or computer systems. Data migration is usually
performed programmatically to achieve an automated migration,
freeing up human resources from tedious tasks. It is required when
organizations or individuals change computer systems or upgrade to
new systems, or when systems merge (such as when the organizations
that use them undergo a merger/takeover).
To achieve an effective data migration procedure, data on the old
system is mapped to the new system providing a design for data
extraction and data loading. The design relates old data formats to the
new system's formats and requirements. Programmatic data migration
may involve many phases but it minimally includes data extraction
where data is read from the old system and data loading where data is
written to the new system.

If a decision has been made to provide a set input file specification for
loading data onto the target system, this allows a pre-load 'data
validation' step to be put in place, interrupting the standard E(T)L
process. Such a data validation process can be designed to interrogate
the data to be transferred, to ensure that it meets the pre-defined
criteria of the target environment, and the input file specification. An
alternative strategy is to have on-the fly data validation occurring at the
point of loading, which can be designed to report on load rejection
errors as the load progresses. However, in the event that the extracted
and transformed data elements are highly 'integrated' with one
another, and the presence of all extracted data in the target system is
essential to system functionality, this strategy can have detrimental,
and not easily quantifiable effects.

After loading into the new system, results are subjected to data
verification to determine whether data was accurately translated, is
complete, and supports processes in the new system. During
verification, there may be a need for a parallel run of both systems to
identify areas of disparity and forestall erroneous data loss.

Automated and manual data cleaning is commonly performed in

migration to improve data quality, eliminate redundant or obsolete
information, and match the requirements of the new system.
Data migration phases (design, extraction, cleansing, load, verification)
for applications of moderate to high complexity are commonly
repeated several times before the new system is deployed.