Map Document Migration

Instructions for use

Map migration consists of two parts: one is data migration. For details, please refer to Data Migration; the other is map document migration, which mainly involves creating, writing, and setting corresponding objects such as layers, features, labels, and symbols in MXD through the iObjects Java component interface provided by SuperMap, thereby completing the conversion from ArcGIS MXD to SuperMap SMWU.

The map migration feature requires licensing for related ArcMap products.

Function Entry

  • Data Migration选项卡->Data Migration->Migrate MXD.

Parameter description

  • Source Dataset: Supports migrating multiple MXD data simultaneously. Use the Add File or Add Folder button in the toolbar to select the MXD project files to be converted.
  • Import Settings:
    • Contains map: Checked by default and cannot be changed.
    • Containing data: Checked by default to export data from MXD. If data migration has already been performed, this checkbox can be unchecked.
    • Import map-related data only: Unchecked by default. This option can only be selected if Containing data is checked. If selected, only data associated with the map (i.e., data used for cartography) will be imported, while other data will not. Only supports source data of types FileGDB(*.gdb), ArcGIS Personal GeoDatabase files (*.mdb), and ShapeFile files (*.shp). Support for source data in SDE databases is available starting from SuperMap iDesktopX 2025 version.
    • Contains layout: Unchecked by default. Check this to import layouts from MXD.
    • Check Data: Supports checking migration data before data migration to verify if data information such as data category and layer type meets migration conditions. After checking, a result info list will be output, allowing users to view errors in detail and handle problematic data based on provided solutions. If multiple MXD files are added, data inspection will not be performed.
    • Generate Migration Report: Check this to generate a migration report (*.xlsx file) in the same directory as the result data after migration, displaying migration status. The report includes five subtables: Overview, Data, Map, Symbols, and Data Sampling, where users can view migration success counts, pre-and post-migration comparisons, and failure reasons.
    • License Verification: Data migration requires licenses for relevant ArcMap modules. The program provides a Check button to verify if the current selected license is valid. If the required license is missing, it will prompt: "ArcGIS license loading failed. Please check the license status." It is recommended to select Default. The Default license scenario is as follows:
      • If the ArcMap version on the computer is 10.4, 10.6, 10.7, or 10.8, the Default option will use ArcServer licenses for verification.
      • If the ArcMap version is 10.2, 10.3, or 10.5, the Default option will use Advanced licenses for verification.
    • Charset: Set the corresponding Charset type based on the character set of the source data files associated with MXD.
  • Result Datasource: Sets how migrated result datasource is stored, providing local UDBX and database datasource types:
    Notes:

    If the MXD to be converted contains data from a PostGIS database, it can be read directly without separate migration.

    • Text: Stored in a text-based datasource UDBX by default. During migration, the program will create a new UDBX datasource in the result folder to store migrated data.
    • Database: Supports storage in database datasources, with types such as SQLPlus, OraclePlus, MySQL, PostgreSQL, PostGIS, MongoDB, and DMPlus. For detailed instructions on creating a new database datasource, please refer to New Datasource page.
  • Result Workspace:
    • Path: Sets the export directory for result data.
    • File Name: Sets the file name for the migrated SuperMap Workspace.

After migration is completed, a pop-up will prompt whether to open the migrated workspace, and the path to the migration log file will be output in the output window. You can view detailed migration information in this file. The figure below shows a comparison of effects before and after migration.

Related Topics

Data Migration

Symbol Migration

Label Migration

Thematic Map Migration

Raster Image Stretch Matching