您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

入门:加速迁移Get started: Accelerate migration

正确地协调业务和 IT 利益干系人有助于克服迁移障碍并加速迁移工作。Proper alignment of business and IT stakeholders helps to overcome migration roadblocks and accelerate migration efforts. 本文提供了以下建议步骤:This article provides recommended steps for:

  • 利益干系人对齐Stakeholder alignment
  • 迁移规划Migration planning
  • 部署登陆区域Deploying a landing zone
  • 迁移前10个工作负荷Migrating your first 10 workloads

它还可帮助您实现适当的管理过程。It also helps you implement proper governance and management processes.

使用本指南来优化协调总体迁移工作所需的过程和材料。Use this guide to streamline the processes and materials required for aligning an overall migration effort. 本指南使用在此图中突出显示的云采用框架的方法。The guide uses the methodologies of the Cloud Adoption Framework that are highlighted in this illustration.

Azure 中的迁移入门

如果你的迁移方案为非典型迁移方案,则可以通过使用 战略迁移和准备工具 (智能) 评估来了解组织的迁移准备情况。If your migration scenario is atypical, you can get a personalized assessment of your organization's migration readiness by using the strategic migration and readiness tool (SMART) assessment. 使用它来确定最符合当前需求的指南。Use it to identify the guidance that best aligns to your current needs.

入门Get started

迁移工作负载所需的技术工作量和过程相对简单。The technical effort and process required to migrate workloads is relatively straightforward. 有效地完成迁移过程是很重要的。It's important to complete the migration process efficiently. 战略迁移准备情况对时间线的影响更大,并成功完成总体迁移。Strategic migration readiness has an even bigger impact on the timelines and successful completion of the overall migration.

若要加快采用,你必须在迁移期间采取措施来支持云采用团队。To accelerate adoption, you must take steps to support the cloud adoption team during migration. 本指南概述了这些迭代任务,以帮助客户从适当的路径转向任何云迁移。This guide outlines these iterative tasks to help customers start on the right path toward any cloud migration. 为了说明支持步骤的重要性,迁移在本文中列出为步骤10。To show the importance of the supporting steps, migration is listed as step 10 in this article. 在实践中,云采用团队可能会与步骤4或5并行开始进行第一次试验性迁移。In practice, the cloud adoption team is likely to begin their first pilot migration in parallel with steps 4 or 5.

步骤1:使利益干系人对齐Step 1: Align stakeholders

若要避免常见的迁移阻塞程序,请为迁移创建清晰且简洁的业务策略。To avoid common migration blockers, create a clear and concise business strategy for migration. 利益干系人与动机和预期业务成果的协调决定了云采用团队做出的决策。Stakeholder alignment on motivations and expected business outcomes shapes decisions made by the cloud adoption team.

  • 动机:战略性协调的第一步是获取推动迁移工作量的动机的协议。Motivations: The first step to strategic alignment is to gain agreement on the motivations that drive the migration effort. 首先理解和分类来自各个利益干系人的动机和常见主题。Start by understanding and categorizing motivations and common themes from various stakeholders across business and IT.
  • 业务成果:在动机调整后,可以捕获所需的业务成果。Business outcomes: After motivations are aligned, it's possible to capture the desired business outcomes. 此信息提供了可用于衡量整体转换的明确指标。This information provides clear metrics you can use to measure the overall transformation.

Deliverables:


负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云策略团队Cloud strategy team
  • 云采用团队Cloud adoption team
  • 优秀或中心 IT 团队的云中心Cloud center of excellence or central IT team
  • 步骤2:协调合作伙伴支持Step 2: Align partner support

    合作伙伴、Microsoft 服务或各种 Microsoft 程序可用于在整个迁移过程中为你提供支持。Partners, Microsoft Services, or various Microsoft programs are available to support you throughout the migration process.

    Deliverables:

    • 在与支持合作伙伴联系之前,建立条款和条件或其他合同协议。Establish terms and conditions or other contractual agreements before you engage supporting partners.
    • 策略和计划模板中标识批准的合作伙伴。Identify approved partners in the strategy and plan template.

    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云策略团队Cloud strategy team
  • 云采用团队Cloud adoption team
  • 优秀或中心 IT 团队的云中心Cloud center of excellence or central IT team
  • 步骤3:收集数据和分析资产与工作负荷Step 3: Gather data and analyze assets and workloads

    使用发现和评估来改善技术的对齐,并创建操作计划来执行策略。Use discovery and assessment to improve technical alignment and create an action plan for executing your strategy. 在此步骤中,使用有关当前状态环境的数据验证业务案例。During this step, validate the business case using data about the current state environment. 然后对最高优先级的工作负荷执行定量分析和深入的定性评估。Then perform quantitative analysis and a deep qualitative assessment of the highest priority workloads.

    • 列出现有系统的清单:使用编程数据驱动的方法来了解当前状态。Inventory existing systems: Use a programmatic data-driven approach to understand the current state. 发现并收集数据,以启用所有评估活动。Discover and gather data to enable all assessment activities.
    • 增量合理化:简化评估工作,重点分析所有资产的定性分析,甚至支持业务案例。Incremental rationalization: Streamline assessment efforts to focus on a qualitative analysis of all assets, possibly even to support the business case. 然后为要迁移的前10个工作负荷添加深度定性分析。Then add a deep qualitative analysis for the first 10 workloads to be migrated.

    Deliverables:

    • 现有库存的原始数据。Raw data on existing inventory.
    • 对现有库存的定量分析以优化业务理由。Quantitative analysis on existing inventory to refine the business justification.
    • 前10个工作负荷的定性分析。Qualitative analysis of the first 10 workloads.
    • 策略和计划模板中记录的业务理由。Business justification documented in the strategy and plan template.

    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云采用团队Cloud adoption team
  • 云策略团队Cloud strategy team
  • 步骤4:创建业务案例Step 4: Make a business case

    使业务案例迁移成为利益干系人的一个迭代会话。Making the business case for migration is likely to be an iterative conversation among stakeholders. 在第一阶段,在构建业务案例时,评估可能的云迁移的初始高级恢复。In this first pass at building the business case, evaluate the initial high-level return from a potential cloud migration. 此步骤的目的是确保所有利益干系人都能满足一个简单的问题:基于可用数据,是云的总体采用方式The goal of this step is to ensure that all stakeholders align around one simple question: based on the available data, is the overall adoption of the cloud a wise business decision?

    Deliverables:


    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云策略团队Cloud strategy team
  • 云采用团队Cloud adoption team
  • 步骤5:创建迁移计划Step 5: Create a migration plan

    云采用计划提供了开发项目积压工作的加速方法。A cloud adoption plan provides an accelerated approach to developing a project backlog. 然后,可以修改积压工作(backlog),以反映发现结果、合理化、需要的技能和合作伙伴。The backlog can then be modified to reflect discovery results, rationalization, needed skills, and partner contracting.

    Deliverables:

    • 部署积压工作(backlog)模板。Deploy the backlog template.
    • 更新模板以反映要迁移的前10个工作负荷。Update the template to reflect the first 10 workloads to be migrated.
    • 更新人员和速度以估计发布计时。Update people and velocity to estimate release timing.
    • 时间线风险:Timeline risks:
      • 缺乏熟悉 Azure DevOps 可能会降低部署过程的速度。Lack of familiarity with Azure DevOps can slow the deployment process.
      • 可用于每个工作负荷的复杂性和数据也会影响时间线。Complexity and data available for each workload can also affect timelines.

    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云采用团队Cloud adoption team
  • 云策略团队Cloud strategy team
  • 步骤6:构建技能准备情况计划Step 6: Build a skills readiness plan

    现有员工可以在迁移工作中扮演实际的角色,但可能需要更多的技能。Existing employees can play a hands-on role in the migration effort, but additional skills might be required. 在此步骤中,找到开发这些技能或使用合作伙伴添加到这些技能的方式。In this step, find ways to develop those skills or use partners to add to those skills.

    Deliverables:


    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云采用团队Cloud adoption team
  • 云策略团队Cloud strategy team
  • 步骤7:部署并对齐登陆区域Step 7: Deploy and align a landing zone

    所有迁移的资产都部署到登陆区域。All migrated assets are deployed to a landing zone. 登录区域的启动很简单,可以支持较小的工作负荷,并可进行缩放以满足一段时间的更复杂工作负荷The landing zone start simple to support smaller workloads, then scales to address more complex workloads over time.

    • 选择登陆区域:根据采用模式查找正确部署登陆区域的方法。Choose a landing zone: Find the right approach to deploying a landing zone based on your adoption pattern. 然后部署该标准化基本代码。Then deploy that standardized code base.
    • 展开登陆区域:无论开始点如何,都要确定已部署的登录区域中的间隙,并为资源组织、安全性、监管、合规性和操作添加所需的组件。Expand your landing zone: Whatever your starting point, identify gaps in the deployed landing zone and add required components for resource organization, security, governance, compliance, and operations.

    Deliverables:

    • 部署第一个登陆区域,用于部署初始低风险迁移。Deploy your first landing zone for deploying initial low-risk migrations.
    • 使用优秀的云中心或 IT 团队开发重构计划。Develop a refactoring plan with the cloud center of excellence or the central IT team.
    • 时间线风险:Timeline risks:
      • 前10个工作负荷的监管、操作和安全要求可能会降低此过程的速度。Governance, operations, and security requirements for the first 10 workloads can slow this process.
      • 重构第一个登陆区域和后续登陆区域需要更长时间,但它应与迁移工作并行发生。Refactoring the first landing zone and subsequent landing zones takes longer, but it should happen in parallel with migration efforts.

    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云平台团队Cloud platform team
  • 云采用团队Cloud adoption team
  • 优秀或中心 IT 团队的云中心Cloud center of excellence or central IT team
  • 步骤8:迁移前10个工作负荷Step 8: Migrate your first 10 workloads

    迁移前10个工作负载所需的技术工作相对简单。The technical effort required to migrate your first 10 workloads is relatively straightforward. 它也是一个在迁移更多资产时重复执行的迭代过程。It's also an iterative process that you repeat as you migrate more assets. 在此过程中,你可以评估工作负荷、部署工作负荷,然后将其发布到生产环境。In this process, you assess your workloads, deploy your workloads, and then release them to your production environment.

    迭代迁移工作阶段:评估、部署、发布

    使用云迁移工具,可以通过一次或迭代迁移数据中心内的所有虚拟机。Cloud migration tools enable migrating all virtual machines in a datacenter in one pass or iteration. 更常见的情况是在每次迭代过程中迁移较少数量的工作负载。It's more common to migrate a smaller number of workloads during each iteration. 将迁移拆分为较小的增量需要更多的计划,但这会降低技术风险以及组织更改管理的影响。Breaking up the migration into smaller increments requires more planning, but it reduces technical risks and the impact of organizational change management.

    随着每次迭代,云采用团队在迁移工作负荷时更好。With each iteration, the cloud adoption team gets better at migrating workloads. 这些步骤可帮助技术团队使其功能更成熟:These steps help the technical team mature their capabilities:

    1. 使用 Azure 迁移指南中概述的工具,将纯基础结构即服务中的第一个工作负荷迁移 (IaaS) 方法。Migrate your first workload in a pure infrastructure as a service (IaaS) approach by using the tools outlined in the Azure migration guide.
    2. 展开 "工具" 选项以使用迁移和现代化,方法是使用 迁移示例Expand tooling options to use migration and modernization by using the migration examples.
    3. 使用 Azure 云迁移最佳做法中所述的更广泛的方法来开发技术战略。Develop your technical strategy by using broader approaches outlined in Azure cloud migration best practices.
    4. 通过 迁移过程改进中所述的一种高效的迁移工厂方法,提高一致性、可靠性和性能。Improve consistency, reliability, and performance through an efficient migration-factory approach as outlined in Migration process improvements.

    Deliverables:

    促进团队迁移工作负荷的能力。Continuous improvement of the adoption team's ability to migrate workloads.


    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云采用团队Cloud adoption team
  • 云策略团队Cloud strategy team
  • 优秀或中心 IT 团队的云中心Cloud center of excellence or central IT team
  • 步骤9:将生产工作负荷移交给云治理法Step 9: Hand off production workloads to cloud governance

    调控是任何迁移工作的长期成功的关键因素。Governance is a key factor to the long-term success of any migration effort. 迁移速度和业务影响非常重要。Speed to migration and business impact is important. 但无需调控的速度可能会很危险。But speed without governance can be dangerous. 你的组织需要决定符合采用模式和监管和合规性需求的监管。Your organization needs to make decisions about governance that align to your adoption patterns and your governance and compliance needs.

    • 调控方法:此方法概述了考虑公司政策和流程的过程。Governance approach: This methodology outlines a process for thinking about your corporate policy and processes. 在确定您的方法之后,您可以构建实现企业云采用工作所需的准则。After determining your approach, you can build the disciplines required to enable governance across your enterprise cloud adoption efforts.
    • 初始调控基础:了解创建管理最低可行产品 (MVP) 所需的专业知识,作为所有采用的基础。Initial governance foundation: Understand the disciplines needed to create a governance minimum viable product (MVP) that serves as the foundation for all adoption.
    • 调控基准:标识组织当前治理状态中的差距。Governance benchmark: Identify gaps in your organization's current state of governance. 获取个性化的基准报告并特选指导如何入门。Get a personalized benchmark report and curated guidance on how to get started.

    Deliverables:

    • 部署初始的管理基础。Deploy an initial governance foundation.
    • 完成调控基准规划以规划将来的改进。Complete a governance benchmark to plan for future improvements.
    • 时间线风险:Timeline risk:
      • 策略和调控实现的改进可以为每个学科增加一到四周。Improvement of policies and governance implementation can add one to four weeks per discipline.

    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云治理团队Cloud governance team
  • 云策略团队Cloud strategy team
  • 优秀或中心 IT 团队的云中心Cloud center of excellence or central IT team
  • 步骤10:将生产工作负荷移交给云操作Step 10: Hand off production workloads to cloud operations

    操作管理是达到迁移成功的另一要求。Operations management is another requirement to reach migration success. 将单个工作负荷迁移到云,而无需了解正在进行的企业操作是一种风险决策。Migrating individual workloads to the cloud without an understanding of ongoing enterprise operations is a risky decision. 与迁移并行,你应该开始规划更长的操作。In parallel with migration, you should start planning for longer-term operations.

    Deliverables:

    • 部署管理基线。Deploy a management baseline.
    • 完成操作管理工作簿。Complete the operations management workbook.
    • 标识需要 Microsoft Azure Well-Architected 审查评估的任何工作负荷。Identify any workloads that require an Microsoft Azure Well-Architected Review assessment.
    • 时间线风险:Timeline risks:
      • 查看工作簿:估算每个应用程序所有者一小时。Review the workbook: Estimate one hour per application owner.
      • 完成 Microsoft Azure Well-Architected 审查评估:每个应用程序估算一小时。Complete the Microsoft Azure Well-Architected Review assessment: Estimate one hour per application.

    负责团队Accountable team 负责人和支持团队Responsible and supporting teams
  • 云运营团队Cloud operations team
  • 云策略团队Cloud strategy team
  • 优秀或中心 IT 团队的云中心Cloud center of excellence or central IT team
  • Value 语句Value statement

    这些步骤可帮助团队通过更好的更改管理和利益干系人对齐加速其迁移。These steps help teams accelerate their migration efforts through better change management and stakeholder alignment. 这些步骤还会删除常见拦截程序并更快地实现业务价值。These steps also remove common blockers and realize business value more quickly.

    后续步骤Next steps

    云采用框架是一个生命周期解决方案,可帮助你开始迁移旅程。The Cloud Adoption Framework is a lifecycle solution that helps you begin a migration journey. 它还有助于使支持迁移工作的团队变得成熟。It also helps mature the teams that support migration efforts. 以下团队可以使用这些后续步骤来继续使其功能变得更加成熟。The following teams can use these next steps to continue to mature their capabilities. 这些并行过程不是线性的,也不应被视为阻止。These parallel processes aren't linear and shouldn't considered blockers. 相反,每个都是一个并行值流,可帮助改进组织的整体云就绪性。Instead, each is a parallel value stream to help improve your organization's overall cloud readiness.

    Team 下一次迭代Next iteration
    云采用团队Cloud adoption team 使用 迁移模型 可了解如何迁移到提供高效迁移功能的迁移工厂。Use the migration model to learn about moving toward a migration factory that provides efficient ongoing migration capabilities.
    云策略团队Cloud strategy team 以迭代方式改善 策略方法计划方法 以及采用计划。Iteratively improve the Strategy methodology and the Plan methodology along with the adoption plan. 查看这些概述并继续迭代你的业务和技术战略。Review these overviews and continue iterating on your business and technical strategies.
    云平台团队Cloud platform team 重新访问 准备就绪的方法 ,继续提升支持迁移或其他采用工作量的总体云平台。Revisit the Ready methodology to continue to advance the overall cloud platform that supports migration or other adoption efforts.
    云   治理   团队Cloud governance team 使用 " 管理" 方法 来继续改进管理流程、策略和学科。Use the Govern methodology to continue to improve governance processes, policies, and disciplines.
    云运营团队Cloud operations team 管理方法 上构建以在 Azure 中提供更丰富的操作。Build on the Manage methodology to provide richer operations in Azure.

    如果你的迁移方案为非典型迁移方案,则可以通过使用 战略迁移和准备工具 (智能) 评估来了解组织的迁移准备情况。If your migration scenario is atypical, you can get a personalized assessment of your organization's migration readiness by using the strategic migration and readiness tool (SMART) assessment. 提供的答案可帮助确定哪些指南最适合你当前的需求。The answers you provide help identify which guidance aligns best with your current needs.