You are on page 1of 12

Migration Plan Project Name

MIGRATION PLAN
The Migration Plan describes the migration from existing systems or applications to the new
solution.
The paragraphs written in the Comment style are for the benefit of the person writing the
document and should be removed before the document is finalized.
SEPTEMBER 11, 1998
Revision Chart
This chart contains a history of this documents revisions. The entries below are provided solely
for purposes of illustration. !ntries should be deleted until the revision they refer to has actually
been created.
The document itself should be stored in revision control" and a brief description of each version
should be entered in the revision control system. That brief description can be repeated in this
section.
Version Primar A!thor"s# $es%ri&tion o' Version $ate
Com&(ete)
Draft TBD Initial draft created for distribution and
review comments
TBD
Preliminary TBD Second draft incorporating initial review
comments, distributed for final review
TBD
inal TBD irst complete draft, w!ic! is placed
under c!ange control
TBD
"evision # TBD "evised draft, revised according to t!e
c!ange control process and maintained
under c!ange control
TBD
etc$ TBD TBD TBD
%&%'()*#+$doc ,-%.-).#-/ Page -
Migration Plan Project Name
PRE*ACE
The preface contains an introduction to the document. #t is optional and can be deleted if
desired.
Intro)!%tion
T!e Migration Plan describes t!e migration from e0isting systems or applications to t!e new
solution$ Migration is often more important in infrastructure deployment t!an application
development projects, but application development projects usually will also include some sort of
migration$ Information on w!at will be migrated is found in t!e unctional Specification$ T!e
1ision.Scope document may also provide some insig!t into t!e overall migration strategy$
+!sti'i%ation
Migration is critical to success$ 2it!out well3tested migration pat!s, new solutions can fail because
legacy components introduce ris4s t!at were never accounted for during planning$ If data or
functionality from legacy systems cannot be migrated successfully to t!e new solution, t!e new
solution cannot be deployed and a return on investment cannot begin$
Team Ro(e Primar
Development and "elease Management are responsible for creating t!e Migration Plan$
Development will write code t!at enables certain aspects of t!e migration$ "elease Management
needs to be familiar wit! t!e migration plans to account for t!em in t!e Deployment and
5perations Plans w!ere appropriate$ T!e migration will involve some s!ort3term activity between
different systems t!at may span different firewalls, operating systems and !ardware6 "elease
Management must account for t!is$ T!ey will also implement t!e decommissioning of legacy
systems t!at are no longer needed$ Test approves t!e plan and incorporates migration tests into
t!eir Test Plans$
Team Ro(e Se%on)ar
Program Management ensures t!at t!e Migration Plan is developed and incorporated it into t!e
Master Project Plan$
%&%'()*#+$doc ,-%.-).#-/ Page #
Migration Plan Project Name
CONTENTS
$ew paragraphs formatted as %eading &" %eading '" and %eading ( will be added to the table
automatically. To update this table of contents in Microsoft )ord" put the cursor anywhere in the
table and press *+. #f you want the table to be easy to maintain" do not change it manually.
1. INTRODUCTION.................................................................................................... 4
#$# MI7"8TI5N P98N S:MM8";$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ &
#$% MI7"8TI5N P98N 5B<=>TI1=S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ &
&.'.& ,usiness -b.ectives.................................................................................................../
&.'.' Migration -b.ectives................................................................................................/
#$? D=INITI5NS, 8>"5N;MS, 8ND 8BB"=1I8TI5NS$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$&
#$& "=="=N>=S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ &
2. MIGRATION STRATEGIES..................................................................................... 5
%$# MI7"8TI5N ST"8T=7; #$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ +
'.&.& Tools..........................................................................................................................0
'.&.' #mplications.............................................................................................................. 0
%$% MI7"8TI5N ST"8T=7; %$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ +
'.'.& Tools..........................................................................................................................0
'.'.' #mplications.............................................................................................................. 0
3. MIGRATION ENVIRONMENT................................................................................ 7
4. MIGRATION GUIDELINES..................................................................................... 8
5. MIGRATION PROCESS.......................................................................................... 9
+$# T=ST =N1I"5NM=NT$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ '
+$% P"=P8"8TI5N$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ '
+$? MI7"8TI5N ST87= #$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ '
+$& MI7"8TI5N ST87= %$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ '
+$+ D=>5MMISSI5NIN7 5 "=P98>=D "=S5:">=S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$'
+$( "599 B8>@ P98N$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ #-
6. INDEX................................................................................................................. 11
7. APPENDICES....................................................................................................... 12
%&%'()*#+$doc ,-%.-).#-/ Page %
Migration Plan Project Name
LIST O* *IG,RES
$ew figures that are given captions using the Caption paragraph style will be added to the table
automatically. To update this table of contents in Microsoft )ord" put the cursor anywhere in the
table and press *+. #f you want the table to be easy to maintain" do not change it manually.
This section can be deleted if the document contains no figures or if otherwise desired.
=rrorA No table of figures entries found$
%&%'()*#+$doc ,-%.-).#-/ Page ?
Migration Plan Project Name
1- INTRO$,CTION
This section should provide an overview of the entire document. $o text is necessary between the
heading above and the heading below unless otherwise desired.
1-1 Mi.ration P(an S!mmar
Provide an overall summary of the contents of this document.
1ome pro.ect participants may need to 2now only the plans highlights" and summarizing creates
that user view. #t also enables the full reader to 2now the essence of the document before they
examine the details.
1-/ Mi.ration P(an O01e%tives
The -b.ectives section defines the primary drivers that were used to create the migration
approach and the 2ey ob.ectives and goals of that approach.
#dentifying the drivers and migration ob.ectives signals to the customer that Microsoft has
carefully considered the situation and created an appropriate migration approach.
1-/-1 B!siness O01e%tives
The ,usiness -b.ectives section identifies the business ob.ectives that are driving the migration.
This may include things such as better manageability" greater scalability" improved security" and
improved availability. This information may be derived from the 3ision41cope or other
appropriate documents.
1-/-/ Mi.ration O01e%tives
The migration5related ob.ectives section defines the migration goals. This could be described in
categories such as the amount of disruption that will occur" impact on security" etc.
1-2 $e'initions, A%ronms, an) A00reviations
Provide definitions or references to all the definitions of the special terms" acronyms and
abbreviations used within this document.
1-3 Re'eren%es
6ist all the documents and other materials referenced in this document. This section is li2e the
bibliography in a published boo2.
%&%'()*#+$doc ,-%.-).#-/ Page &
Migration Plan Project Name
/- MIGRATION STRATEGIES
The Migration 1trategies section describes the one or more strategies that will guide the
migration process. These do not have to be mutually exclusive but may describe different pieces
of the overall migration. 1trategy could be organized around releases 7related to the business or
to development4technology maturity8 or organized around solution components. These strategies
also need to consider moving legacy systems into the new solution environment.
9eveloping strategies ensures that the migration process isnt a one5off activity" that the
solution and its environment are approached strategically.
/-1 Mi.ration Strate. 1
The Migration 1trategy & section describes the specific elements of the solution are that will be
migrated. #t describes the current and future environmental aspects of the migration" the time
frame within the overall solution" and the se:uence in which the elements will be migrated.
/-1-1 Too(s
The Tools section identifies the tools that will be employed to support this migration strategy.
These may be installation tools" testing tools" training tools" etc." and may include tools from
third parties.
/-1-/ Im&(i%ations
The #mplications section describes the impacts caused by the migration and what other things
will need to occur in con.unction with the migration in order for it to be successful. This may
include training" ac:uisition of hardware" changes in user environment" facilities and support"
etc.
/-/ Mi.ration Strate. /
The Migration 1trategy ' section describes the specific elements of the solution are that will be
migrated. #t describes the current and future environmental aspects of the migration" the time
frame within the overall solution" and the se:uence in which the elements will be migrated.
/-/-1 Too(s
The Tools section identifies the tools that will be employed to support this migration strategy.
These may be installation tools" testing tools" training tools" etc." and may include tools from
third parties.
/-/-/ Im&(i%ations
The #mplications section describes the impacts caused by the migration and what other things
will need to occur in con.unction with the migration in order for it to be successful. This may
include training" ac:uisition of hardware" changes in user environment" facilities and support"
etc.
%&%'()*#+$doc ,-%.-).#-/ Page +
Migration Plan Project Name
2- MIGRATION ENVIRONMENT
The Migration !nvironment section provides details on the existing and4or future environment in
which the solution will operate and the people will use the solution. #t describes the current
environment 7all relevant aspects8 and the future environment 7hardware4software" facilities" etc8.
%&%'()*#+$doc ,-%.-).#-/ Page (
Migration Plan Project Name
3- MIGRATION G,I$ELINES
The Migration ;uidelines section describes what guidelines need to be followed within this
environment" such as what trust exists between domains or where user accounts reside.
Team <ole Primary= Test> 9evelopment> <elease Management
Team <ole 1econdary= Program Management
%&%'()*#+$doc ,-%.-).#-/ Page )
Migration Plan Project Name
4- MIGRATION PROCESS
The Migration Process section describes how the migration will be conducted. #t includes the
preparatory activities as well as the migration stages necessary to complete the migration
process. There are sub5sections for ' stages> however" this does not imply that the pro.ect will
have only ' ? create as many as appropriate for the pro.ect.
-utlining the migration process ensures that migration will be conducted in a logical and
controlled manner.
4-1 Test Environment
The Test !nvironment section describes the test environment7s8 that" to the extent possible"
replicate7s8 the production environment. This should include identification of all environmental
attributes that must be in place. There may be more than one environment ? a series of them
could be phased in to control testing. @n example of this is to include users after the initial
phase.
Team <ole Primary= Test
Team <ole 1econdary= 9evelopment> <elease Management
4-/ Pre&aration
The Preparation section identifies and describes all tas2s re:uired to prepare for migration>
ac:uisition" test" training" etc. #t also describes the tas2 se:uences" durations" responsibilities"
and expected results.
4-2 Mi.ration Sta.e 1
The Migration 1tage & section describes stage & of the migration process. #t identifies what is
migrated and in what order.
4-3 Mi.ration Sta.e /
The Migration 1tage ' section describes stage ' of the migration process. #t identifies what is
migrated and in what order.
4-4 $e%ommissionin. o' Re&(a%e) Reso!r%es
The 9ecommissioning of <eplaced <esources section describes how existing resources will be
ta2en offline. This should include criteria that will determine when and how those resources will
be decommissioned.
4-5 Ro(( Ba%6 P(an
The <oll ,ac2 Plan section describes how" if problems do occur" a customer can roll bac2 to the
prior configuration.
%&%'()*#+$doc ,-%.-).#-/ Page *
Migration Plan Project Name
Team <ole Primary= Test> 9evelopment> <elease Management
Team <ole 1econdary= Program Management
%&%'()*#+$doc ,-%.-).#-/ Page '
Migration Plan Project Name
5- IN$E7
The index is optional according to the #!!! standard. #f the document is made available in
electronic form" readers can search for terms electronically.
%&%'()*#+$doc ,-%.-).#-/ Page #-
Migration Plan Project Name
8- APPEN$ICES
#nclude supporting detail that would be too distracting to include in the main body of the
document.
%&%'()*#+$doc ,-%.-).#-/ Page ##

You might also like