Location migration

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Learn how to migrate location data from the ServiceNow Locations table to the Workplace Location table to use them in Workplace Service Delivery applications.

    You can create a hierarchy to be used while migrating location data from the ServiceNow Location table [cmn_location] to the Workplace Location [sn_wsd_core_workplace_location] table.

    You can perform the following actions while creating a location migration record:
    • Configure location migration records by setting a parent location and a child location based on which the locations created in the Locations table [cmn_location] are migrated to the Workplace Location [sn_wsd_core_workplace_location] table.
    • Specify conditions to filter the locations from the Locations table [cmn_location] based on their Location types.

    You can set a location hierarchy configuration as optional depending on the Floor infrastructure. For example, for the Floor > Area > Room/Space hierarchy, you can set the location migration configuration record of Area > Room as an optional hierarchy because some floors might not have areas or only have spaces or rooms.

    When you set a configuration as optional, then the records that don’t match that configuration are matched with the next hierarchy. For example, if there are locations that don’t match the Area > Room hierarchy, then they’re matched with the next hierarchy, which is Floor > Room. If there are Rooms that aren’t assigned to any Areas, then they’re matched with Floors because the Area is optional.

    After migrating the locations, if you create a location in the Workplace Core application, the location is automatically added in the ServiceNow® Location [cmn_location] table. You can configure the type of the location by setting Dictionary Overrides.