Use the discovery client in a disconnected environment

This page explains how to export asset data from a disconnected environmentusing the discovery client, and how to import it toMigration Center. This feature is particularlyuseful when direct network connectivity between your discovery client instanceand Migration Center is not possible due to security policies, networkconstraints, or other reasons. This method lets you collect asset data offline,and then transfer it to Migration Center for analysis and planning.

Limitations

  • You can run only a single export at a time.
  • The number of existing exports is limited to 3 to avoid unintentionallyconsuming excessive disk space with old reports.
  • In case of a crash, reports that were still running don't resume norrestart, and will be marked as failed. You need to manually delete thereports.

Export asset data from the discovery client

You can export the complete data about your assets from thediscovery client.Both themcdc CLI and the discovery clientuse the same export format.

Export using themcdc CLI

To export asset data using themcdc CLI, use themcdc export command.The following are examples of common usage:

  • Export all collected data:

    Linux

    ./mcdc export mc-frames-zip

    Windows

    mcdc.exe export mc-frames-zip

The command creates a zip file in the working directory.

Export using the discovery client installed mode

Follow these steps to create an export report using the discovery clientin installed mode:

  1. In the discovery client, go toExports, then clickNew exports.
  2. In the pane that appears, enter a name for the export, then selectExport full MCDC data.
  3. To confirm, clickExport data.
  4. In theExports page, you can track the progress of your export withthe progress bar under theCompletion column. When finished, clickGoto export to view the details about your export.
  5. In the dialog that appears, copy the path to the directory where thegenerated export file was created, and open it using your file explorer toaccess the outputs.

Cancel an in-progress export

Depending on the number of exported assets, the report creation might takeseveral hours. If you need to cancel an in-progress export, you must delete thereport from the discovery client.

In the discovery client, do the following:

  1. In the discovery client, go to theExports tab.
  2. From the list of reports, select the in-progress report that you want tocancel, then clickDelete.

Content of the output file

The discovery client exports the asset data in a zip file. Each zip filecontains at least two JSON files:

  • metadata.json: contains metadata information about the export,such as the API version used and the timestamp of the export.
  • data.<n>.json: contains the actual asset data in a human-readableformat. Depending on the amount of exported data, the discovery clientcreates multiple files.

The JSON file contains an array ofAssetFrame objects.

[{object(AssetFrame)}]

Import data into Migration Center

After you have exported the asset data from the discovery client, youcan copy the zip file to a machine with access to Migration Center andmanually import it:

  1. In Migration Center, go toData import.

    Go to Data import

  2. ClickAdd data > Import files.

  3. On the upload page, do the following:

    1. Enter a name for the file import job.
    2. From theFile format list, selectMCDC (ZIP).
    3. ClickSelect files to upload and select the zip file to upload.
  4. To start the upload process, clickUpload files.

  5. You're redirected to the import job page. When the validation of thefile is complete, clickImport data, thenConfirm. The status ofthe import will update automatically toCompleted when the importsuccessfully completes.

  6. To view the imported assets, go to theAssets page.

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.