Developing a cloud migration strategy Chapter 03 8
Azure Migration Center. Head to the
Azure Migration Center to begin planning
your migration strategy, find discovery
and data migration software tools from
Microsoft and our partners, and check out
additional resources.
Microsoft Assessment and Planning
(MAP) Toolkit. Collect and organize
system resources and device information
from a single networked computer. MAP
performs four key functions: discovery and
inventory of computers and applications,
hardware and software migration readiness
assessments, software usage tracking, and
capacity planning for virtualization as well
as public and private cloud migration.
Azure Migrate. Assess on-premises
workloads for migration to Azure while
evaluating your existing infrastructure with
Azure Migrate. You can perform cloud
suitability analysis of on-premises machines
and performance-based sizing, with cost
estimations provided for running your
on-premises machines in Azure. After
running a cloud assessment with Azure
Migrate, begin migrating your on-premises
virtual machines (VMs) to Azure using
services including Azure Site Recovery and
Database Migration Service. Visit the Azure
Migration Center to learn more and to find
discovery and data migration software tools
from our partners.
Database Migration Guide. Get help
with moving your data by consulting
the Database Migration Guide, which
provides comprehensive, step-by-step
instructions. You can simply define your
source and destination database platform
for assistance with end-to-end guidance,
including pre-migration, migration, and
post-migration.
Migration partner tools. Use other
Migration partner solutions to support the
assessment process and beyond with tools
like Movere, Cloudamize, CloudPhysics,
Corent, TSO Logic, and Turbonomic.
Define the migration portfolio
To understand which applications to
move—and when and how to move
them—it's important to create a well-
attributed catalog of IT-managed
apps. Then you can weigh the relative
importance of each attribute (for example,
business criticality or the amount of system
integration) to build a prioritized list. There
might be many attributes, ranging from
document classification types, to server
counts, to protocols. Note that it's often useful
to group these into sets of overall attributes.
