The current release of DataHub does not support data migration for Cameo Requirements+ and MagicRQ plugin Data Sources. The current release only supports data migration from DOORS and CSV Data Sources to MagicDraw® and vice versa. Either the source or target must be a MagicDraw® Data Source.
Migrating data in DataHub 17.0.2 - 18.0
If you have created data in DataHub 17.0.2 to 18.0, you must migrate it to the 18.4 version using the Migrate DataHub menu item.
To migrate data in DataHub 17.0.2 - 18.0
- Open a MagicDraw® project (either a local or TeamWork project).
- Start DataHub Explorer. Add all the Data Sources you want to migrate and connect them.
- On the MagicDraw main menu, click Tools > DataHub > Migrate DataHub. The Cameo DataHub Migration dialog opens.
- Choose either the Select DataHub version to migrate or Select DataHub data folder to migrate option. If you choose the first option, select the DataHub version to migrate from the list. If you choose the second option, click Browse to locate the DataHub directory. On Windows, the path directory is C:\Users\userdirectory\.datahub. On Linux, the path directory is /home/userdirectory/.datahub.
- Click Migrate in the Cameo DataHub Migration dialog. The DHLink from the older version of DataHub will be migrated to the current DataHub version.
Migrating data in DataHub 18.1 - 18.5
If you have created data in DataHub 18.1 to 18.5, the data must be migrated to 19.0. The migration to the 19.0 version is performed automatically after DataHub Explorer is open.
Important
- The migration to the 19.0 version is performed only on the open project (main project).
- If the used project also contains the DataHub_Data package, you must open the used project to allow it to migrate to the 19.0 version.
Data in the Containment tree before migrating from the 18.5 to 19.0 version.
Data zipped in the Containment tree after migrating from the 18.5 to 19.0 version.
Tip
- Scope sync relations from previous DataHub versions are migrated to Synchronized DHLink.
- Sync Auto and Sync Manual relations remain the same after the migration.
- Trace relations from previous DataHub versions are migrated as DHTrace.
Related page