For stations already tagged in Haystack 3, a migration
action adds Haystack 4 items that are equivalent to the Haystack 3
versions.
- To invoke the migration action, under TagDictionaryService, right-click Haystack4 and select .

The
Migrate Haystack3 Items window
opens.

The migration action accepts
a customized namespace. By default the
module://haystack/com/tridium/haystack/data/haystack3MigrationConfig.csv configuration file path is selected. You can find the config file
under the
Haystack module.

If desired, you can make changes to the
configuration file. The configuration file consists of the following
columns: haystack3 name, type (tag, tagGroup, or relation), optional
NEQL query, corresponding h4 name(s), and h4 type (tag, tagGroup,
or relation).

- Click OK to execute the migration
action.
The migration action kicks off a job that logs the actions
taken on each component in the station. Any errors are also logged.
Once you take action to correct these errors, they can re-run the
job as required until the migration is complete.
