平台

一个平台涵盖发现、成本建模和迁移

CloudHound 测量每一台服务器，按 AWS、Azure、Google Cloud 和 Oracle Cloud 的实时价格定价，并将其迁移到您选择的云。

已采集数据

每条记录都是来自运行中服务器的一个样本：CPU、内存、磁盘、进程和网络流。同一份数据用于对整个环境进行定价、规划和迁移。

 
条记录已采集，仍在增加

从首次安装到切换

一个典型项目的逐日进展。

  1. 第 0 天

    安装

    每台服务器一条命令，或通过 SSH 和 WinRM 无代理采集。清单、进程和连接即刻到达。

  2. 第 1 小时

    首批利用率数据

    CPU、内存和磁盘每分钟采样一次，每台服务器在几分钟内即可得到描述。

  3. 第 3 天

    完成定价的环境

    每台服务器按 AWS、Azure、Google Cloud 和 Oracle Cloud 实时费率定价：按需、预留和 Savings Plan 并列对比。

  4. 第 5 天

    依赖关系映射

    五天的网络流被聚类为应用。

  5. 第 7 天

    迁移批次计划

    根据依赖关系图生成迁移批次计划。可在批次之间拖动应用。

  6. 切换

    迁移

    每个批次依次复制、逐块校验、转换并在所选云上启动。在 EC2 上 12 分钟完成 125 台服务器。

数据驻留

创建项目组合时，您可以从十七个托管区域中选择一个。任何国家的代理都通过仅出站的 TLS 向该区域报告，其数据只在该区域处理和存储。

7,905
正在报告的代理
0
自您打开本页以来收到的记录

规格优化

代理以一分钟的分辨率持续记录高精度利用率：CPU、内存以及每个驱动器的操作数和字节数计数器。每台服务器根据连续 7 天的每分钟测量数据，按实测用量确定规格。下面是一台示例应用服务器一周的数据，配置为 8 vCPU、32 GiB 和九个驱动器，其 CPU 和内存曲线根据一台生产服务器的一周数据生成。

CPUPer minute, 7 days
MemoryPer minute, 7 days
Disk throughput9 drives stacked, per minute, 7 days, MiB/s. Legend: p99 per drive
C: System1.5 MiB/s, 151 IOPS
D: Application28.5 MiB/s, 744 IOPS
E: Logs13.8 MiB/s, 514 IOPS
F: Uploads30.9 MiB/s, 367 IOPS
G: Cache32.0 MiB/s, 2,296 IOPS
H: Queue10.1 MiB/s, 1,330 IOPS
I: Reports37.1 MiB/s, 979 IOPS
J: Backups79.6 MiB/s, 366 IOPS
K: Archive15.6 MiB/s, 334 IOPS
Provisioned

8 vCPU, 32 GiB, 9 drives

CPU needed

8 × 63% × 1.2 = 6.04rounded up to 7 vCPU

Memory needed

32 × 65% × 1.1 = 22.9 GiBof 32 GiB provisioned

Disk throughput needed

126 MiB/s = 132 MB/s

Disk IOPS needed

4,650 IOPS

Recommended

m6a.2xlarge8 vCPU, 32 GiB, 312 MB/s and 12,000 IOPS to EBS. The smallest size with enough vCPU and memory. m5a.2xlarge costs within 0.5% of it, so CloudHound picks the newer m6a.

Volumes

9 × gp3Each volume provisioned from its own p99. The busiest drive needs 2,296 IOPS and 80 MiB/s, inside the 3,000 IOPS and 125 MiB/s every gp3 volume includes, so nothing is provisioned above the baseline. io2 is recommended only above 80,000 IOPS or 2,000 MiB/s

发现一周后的一台服务器

经过一周发现后，CloudHound 对一台典型应用服务器掌握的信息。该服务器为示例，但其中每个字段都是代理会采集的。

ORDERS-APP-02
Windows Server 2016 StandardVMware VM8 vCPU, 32 GiB10.20.14.37
7 daysObserved
10,080Samples per metric
289Fields per sample
12Connections mapped
Order management application server

Hosts the customer order portal and its API in IIS, and a Java service under Tomcat that takes orders from the EDI gateway and archives documents to Amazon S3. A local SQL Server instance holds the order databases; reporting and the warehouse system read from it on 1433. Busy 07:00 to 19:00 on weekdays, quiet overnight apart from the 02:00 backup.

Migration effort2 of 5

Lift and shift. Every dependency is reached by name or IP, with no hardware dongles or host-bound licenses.

Linux replatforming3 of 5

The API and the Tomcat service move as they are. The portal is .NET Framework 4.8 and needs porting first.

Containerization3 of 5

order-sync is stateless and container ready. The database stays on EC2 or moves to RDS.

Right sizing
8 vCPU32 GiB today
m6a.2xlarge8 vCPU, 32 GiB

$520.93 a month on demand, $396.59 on a 3-year no-upfront Compute Savings Plan, Windows, US East (Ohio), plus $188.80 for nine right-sized gp3 volumes.

ProcessPortsCPUMemoryTraffic/minPresence
w3wp.exe OrdersPortalIIS worker for the order portal443, 809.8%11.2%26.5 MiB100%
sqlservr.exeSQL Server, instance MSSQLSERVER14336.1%36.0%20.5 MiB100%
java.exe order-syncTomcat 9 running the EDI order sync8080, 84433.4%9.8%6.4 MiB100%
w3wp.exe OrdersApiIIS worker for the order API-2.6%3.9%8.3 MiB100%
MsMpEng.exeMicrosoft Defender antivirus-1.1%1.3%-100%
beremote.exeBackup Exec remote agent100000.3%0.6%12.9 MiB100%
sqlagent.exeSQL Server Agent, runs the 02:00 jobs-0.2%0.4%-100%
ch-agent.exeCloudHound discovery agent-0.1%0.1%<0.1 MiB100%
zabbix_agentd.exeZabbix monitoring agent100500.1%0.1%-100%
lsass.exeLocal Security Authority-0.2%0.3%0.3 MiB100%
svchost.exe TermServiceRemote Desktop Services33890.1%0.2%-100%

Traffic per process is the sum of the traffic on the connections that process owns. Presence is the share of samples the process was running in.

DirectionPeerPortProcessTraffic/minPresence
IncomingF5 load balancer10.20.1.10443 HTTPSw3wp.exeOrdersPortal24.1 MiB100%
IncomingF5 load balancer10.20.1.10443 HTTPSw3wp.exeOrdersApi7.7 MiB100%
IncomingREPORT-SQL-0110.20.14.521433 SQL Serversqlservr.exe14.6 MiB96%
IncomingBACKUP-0110.20.3.4010000 NDMPberemote.exe12.9 MiB4%
IncomingWMS-APP-0110.20.16.111433 SQL Serversqlservr.exe5.9 MiB100%
IncomingEDI-GW-0110.20.9.218080 HTTPjava.exeorder-sync4.2 MiB100%
OutgoingFILE-0210.20.4.20445 SMBw3wp.exeOrdersPortal2.4 MiB88%
OutgoingAmazon S3us-east-1443 HTTPSjava.exeorder-sync2.2 MiB42%
OutgoingPayment gateway203.0.113.40443 HTTPSw3wp.exeOrdersApi0.6 MiB97%
OutgoingDC-0110.20.2.10389 LDAPlsass.exe0.3 MiB100%
OutgoingCloudHoundcollections443 HTTPSch-agent.exe<0.1 MiB100%
IncomingNo clients seenIdle listener8443 HTTPSjava.exeorder-sync--
DriveIOPS, 7 daysMiB/s, 7 daysVolume on AWS
C:SystemNTFS, SCSI 0:0, 78 of 120 GiB
gp3, 120 GiB, $9.60 a monthKept, the saving is under 10%3,000 IOPS, 125 MiB/s, the baseline
D:ApplicationNTFS, SCSI 0:1, 262 of 400 GiB
gp3, 400 GiB, $32.00 a monthKept, the taper lands on its size3,000 IOPS, 125 MiB/s, the baseline
E:LogsNTFS, SCSI 0:2, 41 of 100 GiB
gp3, 60 GiB, $4.80 a monthRight-sized from 100 GiB3,000 IOPS, 125 MiB/s, the baseline
F:UploadsNTFS, SCSI 0:3, 133 of 250 GiB
gp3, 190 GiB, $15.20 a monthRight-sized from 250 GiB3,000 IOPS, 125 MiB/s, the baseline
G:CacheNTFS, SCSI 0:4, 22 of 60 GiB
gp3, 40 GiB, $3.20 a monthRight-sized from 60 GiB3,000 IOPS, 125 MiB/s, the baseline
H:QueueNTFS, SCSI 0:5, 9 of 40 GiB
gp3, 20 GiB, $1.60 a monthRight-sized from 40 GiB3,000 IOPS, 125 MiB/s, the baseline
I:ReportsNTFS, SCSI 0:6, 57 of 150 GiB
gp3, 80 GiB, $6.40 a monthRight-sized from 150 GiB3,000 IOPS, 125 MiB/s, the baseline
J:BackupsNTFS, SCSI 0:8, 388 of 600 GiB
gp3, 600 GiB, $48.00 a monthKept, the saving is under 10%3,000 IOPS, 125 MiB/s, the baseline
K:ArchiveNTFS, SCSI 0:9, 610 of 1000 GiB
gp3, 850 GiB, $68.00 a monthRight-sized from 1,000 GiB3,000 IOPS, 125 MiB/s, the baseline

Web applications

ApplicationRuntimeFrameworkServed byBindings
OrdersPortalD:\inetpub\OrdersPortal.NET Framework 4.8ASP.NET MVC 5IIS 10https *:443 orders.corp.local
OrdersApiD:\inetpub\OrdersApi.NET Core 3.1.32ASP.NET CoreIIS 10 (ANCM)https *:443 /api

Background services

ServiceRuntimeServed byPath
order-syncJava 11.0.22Apache Tomcat 9.0.83D:\apps\tomcat9\webapps\order-sync

Network interfaces

InterfaceDriverAddressMTUMiB/s p99
Ethernet0vmxnet310.20.14.37/2415001.9
DatabaseEngineEditionSizeStatusBindings
OrdersDBD:\MSSQL\DATASQL Server 2016 SP3MSSQLSERVER, 13.0.6300Enterprise184.2 GiBOnline*:1433
EdiArchiveD:\MSSQL\DATASQL Server 2016 SP3MSSQLSERVER, 13.0.6300Enterprise41.0 GiBOnline*:1433
OrdersStagingD:\MSSQL\DATASQL Server 2016 SP3MSSQLSERVER, 13.0.6300Enterprise22.7 GiBOnline*:1433
ReportCacheD:\MSSQL\DATASQL Server 2016 SP3MSSQLSERVER, 13.0.6300Enterprise9.4 GiBOnline*:1433
OrdersDB_2019D:\MSSQL\DATASQL Server 2016 SP3MSSQLSERVER, 13.0.6300Enterprise6.3 GiBOffline*:1433

SQL Server Enterprise features

FeatureIn useEnterprise edition
Table partitioningNoNot needed
Online index operationsNoNot needed
Always On availability groupsNoNot needed
Transparent data encryptionNoNot needed
Memory above 128 GiBNoNot needed
VendorTypeVersionStatusLast used
Microsoft.NET FrameworkC:\Windows\Microsoft.NET\Framework64\v4.0.303194.8.04161In use by IISToday
MicrosoftASP.NET Core RuntimeC:\Program Files\dotnet\shared\Microsoft.AspNetCore.App\3.1.323.1.32Running (1)Today
Microsoft.NET RuntimeC:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.366.0.36Installed, not runningNever
Eclipse AdoptiumJava JDK (default)C:\Program Files\Eclipse Adoptium\jdk-11.0.22.711.0.22Running (1)Today
OracleJava JREC:\Program Files\Java\jre1.8.0_2021.8.0_202Installed, not running11 Mar 2024
CPUp99 63%
Memoryp99 65%
Networkp99 1.9 MiB/s
Disk IOPS, summedp99 4,649 IOPS

High fidelity utilization: one sample every 60 seconds, 10,080 per metric over the week. Dashed navy line is the 99th percentile, orange is the sizing buffer above it, 20 percent on CPU and 10 percent on memory.

Migration readiness

Ready
Supported by the migration engineWindows Server 2016 boots on every current EC2 family. All nine disks are SCSI and replicate at full speed.
Ready
Dependencies mapped10 peers across 7 applications. Moves in the Orders wave with REPORT-SQL-01 and EDI-GW-01.
Review
Windows Server 2016Extended support ends 12 Jan 2027.
Action
SQL Server 2016Extended support ended 14 Jul 2026.
Action
.NET Core 3.1Out of support since 13 Dec 2022, still serving OrdersApi.
Review
Oracle Java 8 installedUnused since March 2024. Remove it before it becomes a license question.
Ready
SQL Server licenseEnterprise installed, no Enterprise feature in use. Standard is enough.

Reclaimable before migration

Total
31.4 GiB before migrationSafe to clear 13.9 GiB, review 17.5 GiB first.
Safe
IIS logs, 6.1 GiBC:\inetpub\logs\LogFiles, 18,442 files
Safe
Page file, 7.8 GiBC:\pagefile.sys, recreated at boot
Review
SQL Server backups, 17.5 GiBJ:\MSSQL\Backup, 14 files

依赖关系映射

这是一个示例环境，绘制方式与 CloudHound 根据您服务器之间的网络流量绘制您的环境相同：145 台服务器、780 个连接，按应用分组。拖动服务器，悬停查看它与谁通信，点击应用可单独显示。

迁移批次规划

CloudHound 识别哪些服务器相互通信，并根据这些流量将它们分组为应用。随后每个应用与其依赖的数据库放入同一个迁移批次，因此不会有系统脱离它所需的系统单独迁移。此示例跟踪 1,000 台服务器从发现到十个批次的计划。拖动可旋转。

1 of 6

Illustrative estate of 1,000 servers in 41 applications.

迁移内容与去向

CloudHound 以两种方式之一迁移每台服务器。它可以将整台服务器作为经过验证的精确副本重新托管到 AWS、Azure、Google Cloud 或 Oracle Cloud。在 AWS 上，它还可以将服务器的数据库直接平台重构到 Amazon RDS for SQL Server、PostgreSQL、MySQL 或 MariaDB。

  • 服务器被完整克隆
  • 驱动程序和引导加载程序已针对 EC2 转换
  • 服务器启动前验证每个块
  • 自动健康检查
  • 按工作负载调整规格并优化成本
  • 85+ 项 RDS 兼容性预检
  • 数据库还原到 Amazon RDS
  • 表、行、角色和设置均已验证
  • 按工作负载调整规格并优化成本
  • 凭据保持不变

Database server

Windows Server 2022, SQL Server 2022
Operating system
Applications and services
Databases
Data files
In use

Amazon EC2

r6a.xlarge
Waiting

    迁移支持

    CloudHound 支持 135 种操作系统变体，可迁移我们所见在用企业服务器中的 99.5%。

      迁移后即运行受支持的 Windows Server

      许多迁移到 AWS 的 Windows 服务器运行的是 Microsoft 已不再支持的版本。CloudHound 可在迁移过程中将其升级到 Windows Server 2025，迁移后即获得支持，直至 2034 年 11 月。

      48Out of support34Ending within a year58Supported
      Windows Server

      Example estate of 140 Windows servers. Support dates are Microsoft's end of extended support.

      一块磁盘，从首次同步到上线

      块级迁移复制磁盘的块，因此结果是与源一样启动的精确克隆。源服务器从不被修改。读取原始块以磁盘速度进行：在我们的基准测试中，1 TiB 磁盘在 255 秒内复制完成。之后的每次传输只移动发生变化的块，因此最终同步只包含最近的变化。启动前，目标卷会被回读并与源逐块比对，然后调整磁盘大小。以下数据来自一块示例磁盘。

      1. Initial sync-Blocks in use
      2. Delta-Changed blocks only
      3. Final sync-Moments before launch
      4. Verify-Data blocks checked
      5. Rightsize-Free space trimmed
      Not yet copiedUnusedChanged on the sourceOn the targetVerifiedTrimmed

      启动后自动 QA

      服务器在云端启动后，CloudHound 会检查一切是否已按源端的运行方式恢复：每个服务、端口、数据库、卷和网络路径。

      应用
      • IIS Web 服务器
        W3SVC 正在运行
      • SQL Server
        MSSQLSERVER 和 SQL Server 代理正在运行
      • 应用服务
        2 个业务服务正在运行
      • 监听端口
        80、443、1433 和 135 已开放
      • 网站绑定
        两个 HTTPS 站点均有响应
      • SQL Server 实例
        引擎和版本类型与源一致
      • 数据库
        5 / 5 联机
      存储
      • 卷 C:
        系统，80 GiB
      • 卷 D:
        数据，400 GiB
      • 卷 L:
        SQL Server 日志，100 GiB
      • 映射驱动器 S:
        文件服务器上的共享
      网络
      • 入站 443
        办公用户，路由、ACL 和安全组均允许
      • 入站 1433
        10.20.8.0/24 上的 3 台应用服务器：没有回程路由
      • 支付 API
        HTTPS 443 可达
      • 文件服务器
        SMB 445 可达
      • 邮件中继
        SMTP 25：没有到 10.20.9.0/24 的路由
      • 已配置的地址
        应用设置中的地址可达
      • DNS
        解析器有响应
      系统
      • 地址
        来自目标子网
      • 时钟
        与时间服务器同步
      • Windows 激活
        已在 EC2 上激活
      • 域
        域控制器有响应
      • 核心服务
        防火墙、事件日志、时间、网络
      • 资源
        CPU、内存和磁盘空间均在限制内
      • 重启
        没有意外重启
      • 启动事件
        CD-ROM 驱动程序：EC2 没有光驱
      示例：运行 IIS 和 SQL Server 的 Windows Server 2019 应用服务器
      修复方法

      两个问题都不在服务器上。它在 AWS 中所在子网的路由表缺少到两个本地网络的路由。在 VPC 控制台中打开该路由表并添加：

      • 10.20.8.0/24
        经由 Transit Gateway，用于 3 台应用服务器
      • 10.20.9.0/24
        经由 Transit Gateway，用于邮件中继
      Waiting for the server to boot
      0/26
      Collecting information from the server

      12 分钟完成 125 台服务器

      回放我们 2026 年 9 月的基准测试：125 台服务器，涵盖 94 种操作系统版本和 140 块磁盘，共 9.3 TiB，每一台都完成复制、逐块验证、转换、引导，并在 EC2 上确认。

      14
      GiB/s
      11m
      33s
      100%
      0 queued0 replicating0 launching125 booted

      Ask CH

      Ask CH, the CloudHound assistant, works from the same data as the rest of the platform. One message can produce the assessment pack and then start the migration.

      • PPTXA board readout in your own template: headline figures, end-of-support risk, right-sizing, the business case and the waves.
      • XLSXA workbook of real tables and live formulas over named assumptions, so the term or discount can be changed.
      • DOCXA written report with a contents page, numbered sections, figures and tables.
      • RUNThe migration itself. It lists the servers it will replicate and waits for your approval before anything moves.

      The estate, the figures and the documents shown are illustrative.

      Most AI assistants
      ›
      ‹1,164 servers
      That's a database query.
      Ask CH
      Readiness assessment · 1,164 servers
      Cost estimate · 6 pricing strategies
      Regional pricing · 7 regions compared
      Utilization · 7 days, 95th percentile
      End-of-life data · 208 near end of support
      Licensing · 226 SQL Server instances
      Dependency map · 89 application groups
      Wave plan · 7 named waves
      Composing the readout, workbook and report
      PPTXmap-assess-readout.pptx15 slides
      XLSXbusiness-case.xlsxlive formulas
      DOCXboard-report.docxyour template
      business-case.xlsx  ·  Excel
      D6fx=SUM(Servers[Annual cost on AWS]) * (1 - Discount)
      ABCDEF
      1Aldermont Health · AWS business case
      2Every figure below is a formula over the Servers and Assumptions sheets
      3Cost line (USD a year)TodayOn AWSSavingShare of AWS billAssumption
      4Block storage3,510,0002,310,0001,200,00035%gp3, used data
      5Backup2,640,0001,930,000710,00029%30-day retention
      6EC2 compute3,100,0001,180,0001,920,00018%3-yr savings plan
      7Windows and SQL licenses1,420,000550,000870,0008%License included
      8Network and support790,000650,000140,00010%Business support
      9Total11,460,0006,620,0004,840,00042% lower5 years: 24.2M
      10
      11Term3 yearsDiscount0%Regionus-west-2
      SummaryServersAssumptionsPricing
      board-report.docx  ·  Word
      FileHomeInsertDesignLayoutReferencesReviewView
      Calibri11Heading 1Normal

      Navigation

      1. Executive summary

      2. Assessment approach

      3. Estate overview

      4. Platform composition

      5. Utilization and right-sizing

      6. Licensing

      7. The business case

      7.1 Where the money goes

      7.2 Pricing strategy

      8. End-of-support exposure

      8.1 Hotspots

      8.2 Remediation by wave

      9. Region selection

      10. Dependency mapping

      11. Migration waves

      12. Recommendations

      Appendix A. Assumptions

      Appendix B. Server inventory

      ALDERMONT HEALTH · AWS Migration AssessmentBoard report

      7. The business case

      Running the assessed estate on AWS is estimated at USD 6.62M a year against a current run cost of USD 11.46M, a reduction of 42%. Over five years the difference is USD 24.2M. The estimate uses live AWS price lists for US West (Oregon), a three-year compute savings plan with no upfront payment, and right-sizing on 7 days of high fidelity utilization.

      USD 11.46Mcurrent annual run cost
      USD 6.62Mannual cost on AWS
      USD 24.2Msaved over five years

      7.1 Where the money goes

      Figure 7.1 Annual cost on AWS by component (USD)
      Block storage2.31M
      Backup1.93M
      EC2 compute1.18M
      Windows and SQL licenses0.55M
      Network overhead0.31M
      AWS Business support0.28M

      Storage and backup make up 64% of the AWS bill. Tiering file-server and backup data to S3 and FSx is the largest saving still available after migration.

      7.2 Pricing strategy

      Table 7.2 Annual cost by commercial strategy
      StrategyAnnual costvs on-demand
      No right-sizingUSD 8.94M+20%
      On-demandUSD 7.48M-
      1-year savings planUSD 6.84M-9%
      3-year savings plan (selected)USD 6.62M-11%

      7.3 Five-year view

      Figure 7.3 Cumulative saving against the current run cost (USD)
      4.8M9.7M14.5M19.4M24.2M
      Year 1Year 2Year 3Year 4Year 5
      1. Prices from AWS price lists. 2. Right-sizing at the 95th percentile plus 20% CPU and 10% memory headroom.
      AWS Migration AssessmentPage 7 of 24
      ALDERMONT HEALTH · AWS Migration AssessmentBoard report

      8. End-of-support exposure

      36 servers already run software past vendor end of support and a further 172 reach it within twelve months, 18% of the estate. Migration is the point at which that risk is retired: each wave replaces or upgrades the unsupported software it carries.

      Windows Server 2012 R2 and SQL Server 2012 to 2016 are the most urgent: 50 servers already past support. All of them are scheduled into waves 1 to 3.

      8.1 Hotspots

      Table 8.1 Software at or near end of support
      SoftwareServersSupport endsRisk
      Windows Server 2012 R214Oct 2023Critical
      SQL Server 2012 / 2014102022 / 2024Critical
      SQL Server 201626Jul 2026Critical
      CentOS / Red Hat 719Jun 2024Critical
      PostgreSQL 9.3 - 13172018 - 2025Critical
      Windows Server 2016168Jan 2027Warning
      SQL Server 201727Oct 2027Warning
      Windows Server 2019452Jan 2029Watch

      8.2 Remediation by wave

      Wave 1 (50 servers) retires every Windows Server 2012 R2 host and moves its workloads to Windows Server 2022 on EC2.

      Waves 2 and 3 carry the SQL Server estate, re-platforming 2012 to 2016 instances to supported versions or to RDS.

      8.3 If the estate stays where it is

      Staying on premises means buying extended security updates each year from 2027, and leaves 208 servers without vendor patches for part or all of that period.

      OptionSecurity updatesCost trend
      Migrate in waves 1 to 3Current on arrivalFalls 42%
      Extended supportPaid, time-limitedRises yearly
      Do nothingNoneFlat, risk grows
      3. Counts are servers except PostgreSQL (instances). 4. Windows Server 2019 extended support ends January 2029.
      AWS Migration AssessmentPage 8 of 24
      Page 7 of 246,412 wordsEnglish (United States)
      Then the migration
      Nothing moves until you approve it.
      Approve these changes?
      Start replication for novadesk-vda-01US West (Oregon) · initial sync
      Start replication for novadesk-vda-02US West (Oregon) · initial sync
      Start replication for novadesk-vda-03US West (Oregon) · initial sync
      47 more servers in wave 1
      ApproveCancel
      Throughput
      Transferred
      vda-01
      vda-02
      vda-03
      vda-04
      vda-05
      + 45 more
      Discovery to board pack to replication, in one conversation.
      Ask CH, the CloudHound assistant
      Statue of a dog sitting on a stepped pedestal surrounded by tall trees and plants in soft sunlight.
      AWS 合作伙伴

      “CloudHound 让我们对复杂环境一目了然 - 从发现到批次规划 - 帮助我们为客户更快、更有把握地交付成果。”

      迁移负责人
      AWS Premier Partner

      联系我们
      首页平台关于我们客户案例联系我们计算器
      AWS Partner logo with a white background and orange border.AWS Partner certification badge for AWS Microsoft Workloads Software.AWS Partner Migration & Modernization Software badge with orange border.AWS Partner AI Software Competency badge with AWS logo and orange borderAWS Qualified Software badge with the AWS logo and text.AICPA SOC logo with text 'AICPA SOC', website link, and 'SOC for Service Organizations | Service Organizations' around the edge.5.0★★★★★
      © 2026 CloudHound，保留所有权利
      简体中文