<<Project Name>>

Migration Plan
Customer Name
Directions for using template:
Read the Guidance (Arial blue font in brackets) to understand the information that
should be placed in each section of this template. Then delete the Guidance and
replace the placeholder within <<Begin tet here!! with "our response. There ma" be
additional Guidance in the Appendi of some documents# which should also be
deleted once it has been used.
$ome templates ha%e four le%els of headings. The" are not indented# but can be
differentiated b" font t"pe and si&e:
'eading ( ) Arial Bold (* font
'eading + ) Arial Bold ,talic (- font
'eading . ) Arial Bold (. font
'eading . ) Arial Bold ,talic (+ font
/ou ma" elect to indent sections for readabilit".
Author
Author 0osition
1ate
2ersion: (.3
345+(5+3(-
2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues
discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accurac of an
information presented after the date of publication.
This document is for informational purposes onl. MICROSOFT MAKES NO WARRANTIES E!PRESS OR
IMP"IE# IN T$IS #OC%MENT&
Microsoft and !isual Basic are either registered trademarks or trademarks of Microsoft in the "nited #tates and$or
other countries.
345+(5+3(-
Revision & Sign-off Sheet
6hange Record
1ate Author 2ersion 6hange Reference
Re%iewers
7ame 2ersion Appro%ed 0osition 1ate
1istribution
7ame 0osition
1ocument 0roperties
,tem 1etails
1ocument Title 8igration 0lan
Author
6reation 1ate
9ast :pdated
345+(5+3(-
Table of Contents
$ummar"..........................................................................................................................
;b<ecti%es and Goals.......................................................................................................
Business=Related ;b<ecti%es.......................................................................................
8igration=Related Goals.............................................................................................
8igration $trategies........................................................................................................
8igration $trateg" (...................................................................................................-
Tools.......................................................................................................................-
,mplications............................................................................................................-
8igration $trateg" +...................................................................................................-
Tools.......................................................................................................................-
,mplications............................................................................................................-
8igration >n%ironment..................................................................................................?
8igration Guidelines......................................................................................................?
8igration 0rocess...........................................................................................................?
Test >n%ironment........................................................................................................?
0reparation..................................................................................................................?
8igration $tage (.......................................................................................................*
8igration $tage +.......................................................................................................*
1ecommissioning of Replaced Resources.................................................................*
Roll Back 0lan............................................................................................................*
345+(5+3(- 3
%Intro'uction to t(e Tem)late
#escri)tion* The Migration &lan describes the migration from e'isting sstems or
applications to the new solution. Migration is often more important in infrastructure
deploment than application development pro(ects, but application development
pro(ects usuall will also include some sort of migration. )nformation on what will be
migrated is found in the *unctional #pecification. The !ision$#cope document ma
also provide some insight into the overall migration strateg.
+usti,ication* Migration is critical to success. +ithout well,tested migration paths,
new solutions can fail because legac components introduce risks that were never
accounted for during planning. )f data or functionalit from legac sstems cannot be
migrated successfull to the new solution, the new solution cannot be deploed and a
return on investment cannot begin.
-Team Role Primar-* #e.elo)ment an' Release Management are responsible for
creating the Migration &lan. .evelopment will write code that enables certain aspects
of the migration. /elease Management needs to be familiar with the migration plans
to account for them in the .eploment and 0perations &lans where appropriate. The
migration will involve some short,term activit between different sstems that ma
span different firewalls, operating sstems and hardware1 /elease Management must
account for this. The will also implement the decommissioning of legac sstems
that are no longer needed. Test approves the plan and incorporates migration tests
into their Test &lans.
Team Role Secon'ar-* Program Management ensures that the Migration &lan is
developed and incorporated it into the Master &ro(ect &lan.23
345+(5+3(-
Summar-
/#escri)tion* &rovide an overall summar of the contents of this document.
+usti,ication* #ome readers ma need to know onl the highlights of the plan, and
summari4ing creates that user view. )t also enables the full reader to know the
essence of the document before the e'amine the details.3
<<Begin tet here!!
O0jecti.es an' 1oals
/#escri)tion* The 0b(ectives and 5oals section defines the primar drivers that were
used to create the migration approach and the ke ob(ectives and goals of that
approach.
+usti,ication* )dentifing the drivers and migration ob(ectives signals to the customer
that Microsoft has carefull considered the situation and created an appropriate
migration approach.3
Business-Related Objectives
/#escri)tion* The Business,/elated 0b(ectives section identifies the business
ob(ectives that are driving the migration. This ma include things such as better
manageabilit, greater scalabilit, improved securit, and improved availabilit. This
information ma be derived from the !ision$#cope or other appropriate documents.3
<<Begin tet here!!
Migration-Related Goals
/#escri)tion* The Migration,/elated 5oals section defines the migration goals. This
could be described in categories such as the amount of disruption that will occur,
impact on securit, etc.3
<<Begin tet here!!
Migration Strategies
/#escri)tion* The Migration #trategies section describes the one or more strategies
that will guide the migration process. These do not have to be mutuall e'clusive but
ma describe different pieces of the overall migration. #trateg could be organi4ed
around releases 6related to the business or to development$technolog maturit7 or
organi4ed around solution components. These strategies also need to consider
moving legac sstems into the new solution environment.
+usti,ication8 .eveloping strategies ensures that the migration process isn9t a :one,
off; activit, that the solution and its environment are approached strategicall.3
345+(5+3(- +
Migration Strategy 1
/#escri)tion* The Migration #trateg < 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. 3
<<Begin tet here!!
Tools
/#escri)tion* The Tools section identifies the tools that will be emploed to support
this migration strateg. These ma be installation tools, testing tools, training tools,
etc., and ma include tools from third parties.3
<<Begin tet here!!
Im)lications
/#escri)tion* The )mplications section describes the impacts caused b the
migration and what other things will need to occur in con(unction with the migration in
order for it to be successful. This ma include training, ac=uisition of hardware,
changes in user environment, facilities and support, etc.3
<<Begin tet here!!
Migration Strategy
/#escri)tion* The Migration #trateg 2 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.3
<<Begin tet here!!
Tools
/#escri)tion* The Tools section identifies the tools that will be emploed to support
this migration strateg. These ma be installation tools, testing tools, training tools,
etc., and ma include tools from third parties.3
<<Begin tet here!!
Im)lications
/#escri)tion* The )mplications section describes the impacts caused b the
migration and what other things will need to occur in con(unction with the migration in
order for it to be successful. This ma include training, ac=uisition of hardware,
changes in user environment, facilities and support, etc.3
<<Begin tet here!!
345+(5+3(- .
Migration En.ironment
/#escri)tion* The Migration >nvironment section provides details on the e'isting
and$or future environment in which the solution will operate and the people will use
the solution. )t describes the current environment 6all relevant aspects7 and the future
environment 6hardware$software, facilities, etc7.3
<<Begin tet here!!
Migration 1ui'elines
/#escri)tion* The Migration 5uidelines section describes what guidelines need to be
followed within this environment, such as what trust e'ists between domains or
where user accounts reside.
-Team Role Primar-* Test1 .evelopment1 /elease Management
Team Role Secon'ar-* &rogram Management23
<<Begin tet here!!
Migration Process
%#escri)tion8 The Migration &rocess section describes how the migration will be
conducted. )t includes the preparator activities as well as the migration stages
necessar to complete the migration process. There are sub,sections for 2 stages1
however, this does not impl that the pro(ect will have onl 2 ? create as man as
appropriate for the pro(ect.
+usti,ication8 0utlining the migration process ensures that migration will be
conducted in a logical and controlled manner.3
Test !nviron"ent
/#escri)tion The Test >nvironment section describes the test environment6s7 that, to
the e'tent possible, replicate6s7 the production environment. This should include
identification of all environmental attributes that must be in place. There ma be more
than one environment ? a series of them could be phased in to control testing. An
e'ample of this is to include users after the initial phase.
-Team Role Primar-* Test
Team Role Secon'ar-* .evelopment1 /elease Management23
<<Begin tet here!!
#re$aration
/#escri)tion* The &reparation section identifies and describes all tasks re=uired to
prepare for migration1 ac=uisition, test, training, etc. )t also describes the task
se=uences, durations, responsibilities, and e'pected results.3
<<Begin tet here!!
345+(5+3(- -
Migration Stage 1
/#escri)tion* The Migration #tage < section describes stage < of the migration
process. )t identifies what is migrated and in what order.3
<<Begin tet here!!
Migration Stage
/#escri)tion* The Migration #tage 2 section describes stage 2 of the migration
process. )t identifies what is migrated and in what order.3
<<Begin tet here!!
%eco""issioning of Re$laced Resources
/#escri)tion* The .ecommissioning of /eplaced /esources section describes how
e'isting resources will be taken offline. This should include criteria that will determine
when and how those resources will be decommissioned.3
<<Begin tet here!!
Roll Bac& #lan
/#escri)tion* The /oll Back &lan section describes how, if problems do occur, a
customer can roll back to the prior configuration.
-Team Role Primar-* Test1 .evelopment1 /elease Management
Team Role Secon'ar-* &rogram Management23
<<Begin tet here!!
345+(5+3(- ?