---
sourceDocument: Australia Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/service-management-for-the-enterprise

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Service Management

ft:clusterId :

    - sm4e

bundleId :

    - sm4e

workflow :

    - Technology


---

# Migrate facilities data to new space definition tables

# Migrate facilities data to new space definition tables {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

To continue using the image-based floor plans with the new space definition, migrate
your data from the old tables to the new space definition tables.

## Vorbereitungen

Role required: facilities_admin

## Warum und wann dieser Vorgang ausgeführt wird

The migration process only migrates complete data. A space that is not in a level or a level not in a building is not migrated. This behavior can be changed by updating the migration script include. Floors that are not connected to a building are not migrated, nor are spaces that are not part of a floor or building. As part of the migration process, the legacy spaces, floors, and buildings are marked as migrated.  
The migration path for the old tables to the new are:

* \[cmn_building\] migrates to \[alm_building\]
* \[fpv_floor\] migrates to \[fm_level\]
* \[fpv_element\] migrates to \[fm_space\]
{#t_MigFacDataToNewSpaceDefTable__ul_gpx_f3n_lt}

## Prozedur

1. Navigate to AllFacilitiesAdministrationMigrate.
2. Click Migrate.

## Ergebnisse

The following results can be expected:

* Data is migrated to the new facilities management tables for buildings, floors, and spaces.
* After a building, floor, or space is migrated, it is marked as migrated, and is not able to be migrated again.  
  Hinweis:  
  Any object that is marked as migrated does not get migrated again, so you can safely run through the migration process multiple times without creating duplicated objects in the space tables. This behavior can be modified in the migration script include or by resetting the migration flag on the original objects.
{#t_MigFacDataToNewSpaceDefTable__ul_kfh_m1g_lt}