The discovery client 6.3.13 is available with a new feature and a bug fix.
Preview: Added support for discovery of the following assets from your AWS account:
For more information, see Discover assets on AWS and Directly import asset inventory data from AWS.
Fixed an issue where some supported operating systems from the vSphere guest OS list were missing from the discovered assets. The discovery client now uses the VMware vSphere API to collect all supported OS families.
]]>Preview: When visualizing network dependencies in Migration Center, you can now tag assets and filter the dependency graph based on groups, network, and asset details.
For more information, see Visualize network dependencies.
]]>Migration Center now lets you configure sizing recommendations for your migrated assets. You can define a target sizing strategy, set default utilization estimates for assets that lack performance data, and specify network data transfer out preferences to better estimate your total cost of ownership (TCO).
For more information, see Sizing and network preferences.
When configuring migration preferences for Compute Engine, you can now select between Multi-tenant (default) or Sole-tenant preference modes.
For more information, see Google Compute Engine preferences.
]]>The discovery client 6.3.12 is available with a bug fix.
Fixed a bug in the MCDC guest collection script.
The guest collection process no longer runs Java or application binaries (Tomcat and JBoss) on target servers. Version identification for Tomcat and JBoss now relies exclusively on static configuration and the release notes.
]]>The discovery client 6.3.11 is available with new features and bug fixes.
The Migration Center discovery client CLI (mcdc CLI) now uses
remote WMI collections by default for Windows guest host collections to improve
efficiency. This method replaces the use of local collection scripts.
If script-based collection is required for earlier Windows versions
(such as Windows Server 2008), you can deactivate this functionality
with the --script flag.
For more information, see Collect data remotely over WMI.
Fixed an issue in the Migration Center discovery client CLI where region filtering for S3 assets during AWS inventory discovery failed, resulting in asset collection from all regions instead of only specified regions.
Fixed an issue where adding vCenter credentials in the Migration Center discovery client UI redirected users to the dashboard instead of opening the credentials pane.
Fixed a bug that caused the discovery client not to use the provided proxy when connecting to Migration Center.
]]>Preview: Migration Center now lets you visualize network dependencies between your discovered server assets. You can view a graph of network connections for specific groups or a subset of servers to better understand your infrastructure and plan your application migration.
For more information, see Visualize network dependencies.
]]>The discovery client 6.3.10 is available with a bug fix.
Fixed a bug in the MCDC guest collection script.
]]>Preview: Migration Center now provides more granular storage preferences for Compute Engine. You can now specify your preference for using Hyperdisk Storage Pools to reduce costs and improve operational efficiency.
For more information, see Migration preferences for servers.
If you select sole-tenant nodes as your migration target, Migration Center always recommends Hyperdisk Storage Pools even if they are more expensive than individual Hyperdisk volumes. When migrating to sole-tenant nodes, we recommend that you select Never in the Hyperdisk Storage Pools section of your preferences.
For more information, see Migration preferences for servers.
]]>The discovery client 6.3.9 is available with new features and bug fixes.
Preview: Added support for discovery of the following assets from your AWS account:
For more information, see Discover assets on AWS.
Fixed an issue that caused the collection of data from Linux machines to become unresponsive on systems running JBoss EAP.
Fixed an issue that caused the VMware vCenter status to incorrectly
display the previous status during a new collection, such as
warning or error. The status is now correctly cleared when a new
collection job begins.
Fixed an issue that prevented the mcdc discover ls command from displaying IP
addresses.
C/C++ application migration to Arm architecture assessment. The App Modernization Assessment tool now offers a dedicated assessment for C/C++ applications to facilitate their migration to Arm-based architectures (such as Google Cloud Axion C4A VMs). This new feature helps you do the following:
Enhanced productivity with command-line completion. The codmod tool now
supports shell command-line completion for Bash, Zsh, Fish, and PowerShell,
significantly boosting your productivity. This feature lets you quickly
type commands, flags, and arguments by pressing the TAB key to see and
select the available options.
With this feature, you can discover options and see valid flag values.
Additionally, suggestions are context-aware, meaning completions are tailored to
the specific command.
For example, codmod config set [TAB] suggests config keys,
and file path completion is exclusively available for file and directory flags.
For additional details, see
Command-line completion.
Automatic version check and updates. The codmod tool now includes an
automatic version check feature to help you stay up-to-date with the latest
improvements and fixes. Every 24 hours, the codmod tool checks for the
availability of a newer version. If an update is available, a notification
message appears in your terminal with the new version number and a download
link.
You can disable the automatic check at any time using the following command:
codmod config set disable_version_check true.
To re-enable automatic checks, simply set the value back to false.
You can always view the current state and other configurations by running
codmod config list.
Supporting documents for assessment. The codmod tool can now analyze
a directory containing additional supporting documents to the codebase.
The codmod tool supports documentation in textual, PDF, and image (PNG, JPG,
JPEG) formats.
Provide the directory by passing the --supporting-documents <directory> flag
to the create command.
Preview: Migration Center lets you view detailed total cost of ownership (TCO) information directly in the Google Cloud Console for each asset and migration preference set, without the need to export the TCO report. You can also see AI-powered insights for each allocated Google Cloud asset.
This experimental feature is available only for Compute Engine VMs. VMware Engine, sole-tenant nodes, and database assets are not supported.
For more information, see Generate TCO reports.
]]>Preview: On the Migration Center Summary page, you can now see an aggregated view of the detected software assets.
For more information, see View the collected assets.
You can also group your software assets and see a count of each software instance in the total cost of ownership (TCO) report.
For more information, see Generate TCO reports.
]]>The discovery client 6.3.8 is available with new features and bug fixes.
Preview: Added support for discovery of the following assets from your AWS account:
For more information, see Discover assets on AWS.
Migration Center now collects and displays CPU manufacturer information for discovered assets. You can see this information on the Asset details page.
For more information, see View the collected assets.
To better support large VMware vCenter environments, the maximum time for a single collection job has been increased to 24 hours, therefore reducing timeout issues.
Migration Center Discovery Client user interface now displays a progress bar and asset count for VMware vCenter collections, helping you track long-running jobs.
For more information, see Add vCenter for discovery.
]]>Generally available: Migration Center now provides more granular Google Compute Engine preferences. You can now adjust your recommendations to balance latest technology and cost, or to prioritize the lowest price. Additionally, you can include pre-released SKUs in assessments, and select from a wider range of pricing tracks including on-demand and committed use discounts.
For more information, see Migration preferences for servers.
]]>Generally available: Migration Center now includes AI-powered suggestions for software detection.
For more information, see Detected software.
]]>New quantitative metrics. The report summary section now includes a summary of key quantitative metrics, providing a quick, data-driven overview of the report at a glance.
Added file regex flags. Two new optional flags, --force-include and --force-exclude, have been added to provide user flexibility in file selection.
Added feedback and support links to HTML report. The feedback and support links point to Google Forms that will be used to gather feedback and support requests.
The Migration Center App Modernization Assessment tool version 0.9.0 is available in Preview.
The Migration Center App Modernization Assessment, powered by Google Gemini (via Vertex AI), is a tool designed to accelerate your application modernization journey. It offers automated, AI-powered analysis to understand your entire codebase in hours, not months, uncovering dependencies and complexities. This enables organizations to swiftly transition their existing codebases to the cloud by identifying potential blockers and providing tailored recommendations based on Google Cloud best practices, ultimately de-risking and planning your transformation with confidence.
Create custom report from template. Use a document as a template to create a custom report. The report will attempt to match the outline and style of the template document.
Removed 2.5-flash-lite-exp from Suggested Models. To improve the quality of generated reports, the support for 2.5-flash-lite-exp model was removed.
Smaller Default Report and new Full Report. The default report has been streamlined to 5 sections, reducing generation time and cost. A comprehensive 12-section report can now be generated using the new create full command.
Added a Content Security Policy (CSP) to improve the security of locally viewed HTML reports.
]]>Generally available: Added support for discovery of Amazon Relational Database Service (Amazon RDS) instances and uploading the collected information to Migration Center.
For more information, see Discover EC2 instances and databases on AWS.
Generally available: Added support for discovery of Azure virtual machine (VM) instances and uploading the collected information to Migration Center.
For more information, see Discover virtual machine instances on Azure.
]]>The discovery client 6.3.7 is available with new features and bug fixes.
Fixed an issue that prevented the collection of CPU model names for vSphere ESXi hosts, resulting in missing CPU information for vSphere virtual machines (VMs) in Migration Center.
When you upgrade to discovery client 6.3.7, data collected by earlier versions of discovery client and that was not already uploaded to Migration Center will be deleted.
Fixed an issue in the Linux collection script where the output tar file had insufficient permissions, which prevented access by the original non-root user when the script was run with root privileges.
When you run an inventory discovery on your Amazon Web Services (AWS) account, memory utilization for Amazon EC2 instances is collected by the mcdc CLI if the Amazon CloudWatch agent is installed and configured.
When you run a Linux guest scan, the mcdc CLI now discovers the Btrfs filesystem.
Generally available: You can now export collected data from the discovery client to a file for manual import into the Migration Center.
For more information, see Use the discovery client in a disconnected environment.
Fixed an issue where ZFS partitions not generated by the zpool command were incorrectly included in Linux scans.
Added guidance on the Migration Center user interface to help Active Directory (AD) administrators to resolve potential authentication failures by verifying MCDCUsers group membership.
Fixed an issue that caused floppy disk drives to be incorrectly included in Linux disk scans.
Fixed an issue that prevented parsing of df output on Linux when a mount point name contained spaces.
You can now filter the discovered Amazon Relational Database Service (Amazon RDS) assets by tags.
]]>Generally available: On the Migration Center Data Import page, you can now see short descriptions for connection errors with the discovery client.
For more information, see Review the discovery client details.
Generally available: Migration Center lets you generate a network dependencies report from the data you collect from your infrastructure.
For more information, see Analyze network dependencies.
]]>The Migration Center discovery client v5 and the Rapid Migration Assessment API were shut down on June 30, 2025, and are no longer available.
For more information, see Migration Center deprecations.
]]>Preview: Added support for discovery of Azure virtual machine (VM) instances and uploading the collected information to Migration Center.
For more information, see Discover virtual machine instances on Azure.
]]>Generally available: You can now create asset groups in bulk or update group assignments across many assets simultaneously.
For more information, see Add or update asset group assignments in bulk.
]]>The discovery client 6.3.6 is available with new features and bug fixes.
Added collection and upload of AWS tags to Migration Center. This enables better visibility and easier grouping of your AWS infrastructure.
Fixed an issue where the IP range scan remained in the In Progress state indefinitely after restarting the discovery client service during a scan.
Fixed an issue that caused incorrect primary IP addresses of Amazon EC2 instances to be uploaded to Migration Center. This improves the accuracy of network dependencies reports.
Added an indicative message to alert users of unsupported browsers.
Added upload of disk read and write input/output operations per second (IOPS) to Migration Center. This helps ensure accurate pricing and sizing reports.
Added the --extended flag to the mcdc discover ls command to include location and collection parameters columns.
Fixed an issue in Linux guest collection that omitted filesystem overhead and reservations from total partition size calculations.
Fixed an issue that caused incorrect capacity and storage reporting for Windows RAID partitions.
Fixed an issue where disk space reporting excluded virtual disk partitions for some filesystems (specifically fuse) on Linux machines. This improves the accuracy of storage capacity and usage data.
Fixed an issue on Linux where partition data couldn't be retrieved when mount points contained spaces.
Fixed an issue where system memory swap space was sometimes incorrectly reported as disk storage.
Fixed an issue that caused VMware vCenter collection to take significantly more time to initiate a subsequent collection after a details or credential updates.
Fixed an issue that caused the Win32_Service Windows Management Instrumentation (WMI) query to fail, resulting in Windows guest collection timeouts. This improves the Windows guest collection success rate and reduces execution time.
Preview: Added support for discovery of Amazon Relational Database Service (Amazon RDS) instances and uploading the collected information to Migration Center.
For more information, see Discover EC2 instances and databases on AWS.
Fixed an issue that required an IP address when using the test credentials feature with VMware tools.
Fixed an issue that prevented users from sorting Windows Servers by scan status.
Fixed an issue that incorrectly calculated storage sizes for ZFS file systems.
]]>You can now unregister the discovery client from Migration Center, so that you can register it in a different project without reinstalling.
The discovery client 6.3.5 is available with new features and bug fixes.
View information about the connected Google Cloud project on the settings page.
You can now manually renew the service account key used for authentication with Migration Center.
Fixed an issue where the Migration Center discovery client CLI discover ls command only displayed IPv6 addresses. It now displays only IPv4 addresses.
Fixed the migrate to Google Distributed Cloud (GDC) assessment to issue a warning for VMs with disks larger than 5 TiB, instead of the previous 108 TiB limit, to account for object storage limitations.
Fixed an issue that caused disk input/output operations per second (IOPS) on Linux to be reported incorrectly to Migration Center.
Fixed an issue that caused expired discovery clients to be incorrectly presented as active on the settings page.
Fixed an issue that incorrectly reported procfs and sysfs mounts to Migration Center.
Fixed an issue that caused the architecture fields not to be collected from ARM VMs.
Preview: Added support for discovery of AWS EC2 instances and uploading the collected information to Migration Center.
For more information, see Discover VMs on AWS.
Fixed an issue preventing RedHat operating system (OS) name and version collection.
Fixed an issue where the Migration Center discovery client CLI only reported a single memory usage sample, potentially causing incorrect rightsizing suggestions.
]]>The Migration Center Use Case Navigator now includes MongoDB workload identification and guidance. This enhancement allows users to gain valuable insights into the potential transformation journeys for their MongoDB workloads, and to generate comprehensive reports on their MongoDB workload footprint.
]]>The discovery client 6.3.4 is available with new features and bug fixes.
Reduced potential performance impact of the guest collection script on target Windows VMs by optimizing the collection script.
Reduced potential performance impact of the guest collection script on target Linux VMs by setting scripts to execute with a higher nice level.
Fixed an issue that caused Linux guest collection to report incorrect disk space in some cases by excluding network mounts and temporary file systems, and incorrectly calculating logical volumes.
The discovery client disk usage collection in Linux and Windows VMs has been enhanced for improved accuracy in disk reporting. The system now supports disk partition type discovery. For Linux VMs, discovery client reports the total disk capacity without partitioning it; for Windows VMs, the partitioned structure is reported.
Fixed an issue that caused UDP connections on Windows to not be uploaded to Migration Center.
ESX CPU hyperthreading detection is now supported in the collection of inventory level data from vCenter.
Fixed an issue that caused VMs with a very large number of running processes, services, installed applications, or open files handlers, to be reported incorrectly to Migration Center.
]]>Generally available: Migration Center now detects and surfaces VM hyperthreading enabled or disabled state based on information uploaded on an RVTools file.
Generally available: Added support for Cloud SQL Enterprise Plus for SQL Server.
Generally available: Migration Center now surfaces VM hyperthreading enabled or disabled state based on the information collected by the Migration Center discovery client.
Generally available: You can now authorize Google Cloud engineers to help with your migration by accepting the terms and conditions in Migration Center.
For more information, see Get started with Migration Center.
]]>StratoZone was shut down on September 30, 2024, and is no longer available.
Generally available: Migration Center lets you export the inventory and performance data in CSV and Google Sheets format.
For more information, see Export inventory and performance data.
Generally available: Migration Center is now available in the following additional regions:
For more information, see Migration Center locations.
Generally available: Migration Center lets you view the relationship between a server and a hosted database directly in the Console.
]]>The discovery client 6.3.3 is available with new features and bug fixes.
Fixed an issue that caused Linux guest collections to report the wrong number of CPU cores in some cases.
MSI installer privileges changes: Users are no longer required to run the MSI installer as administrators. Now, standard users with the ability to install software can also run the installer.
Added technical fit assessment for BitLocker encryption as part of "Shift to GCE" and "Shift to GDC" assessment. Added rules IDs: C1W-STO-1 and D1W-STO-1.
For more information, see Offline assessment rules.
Fixed an issue that caused VMs using Windows NLB of the same cluster to be represented as a single VM in Migration Center.
Added a notification that appears when a new version of the discovery client is available.
Reduced the resource consumption of the Windows collection script on the target VMs.
Fixed an issue that caused the discovery client to wrongly classify Java processes as JBoss applications.
]]>Added support for Linux kernel driver information collection required for enhanced technical assessment.
You can now add new guest OS credentials from the vCenter discovery page.
The discovery client 6.3.2 is available with new features and bug fixes.
Fixed an issue that sometimes caused Windows guest collections to report the wrong number of CPU cores.
Added an error tooltip to the upload status in the Scans page.
Fixed an issue that caused the installation to fail if the default PowerShell execution policy is too restrictive.
You can now reset guest OS credentials in the vCenter discovery page.
Improved free disk calculation from vCenter inventory collection.
The discovery client now validates the existence of guest OS credentials before the creation of an IP range.
Fixed an issue that caused a temporary directory created during guest-level collection using VMware Guest Tools to not get cleaned up if the collection times out.
Added technical fit assessment for VirtIO Drivers as part of "Shift to GCE" and "Shift to GDC" assessment rules ID: C1L-APP-2 and D1L-APP-3.
The discovery client now preserves the users in the MCDCUsers group during an upgrade.