---
sourceDocument: Australia Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/de-DE/it-business-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Start migration of SAFe data to EAP

# Start migration of SAFe data to EAP {#ariaid-title1}

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

Submit a SAFe-EAP migration request and start the migration of data between the tables of Scaled Agile Framework and Enterprise Agile Planning.

## Vorbereitungen

Role required: sn_apw_advanced.eap_admin

## Warum und wann dieser Vorgang ausgeführt wird

## Prozedur

1. Navigate to AllStrategic PlanningEnterprise Agile PlanningSAFe Migration requests.
2. Select New.
3. On the form, fill in the fields.  
   For field information, see [SAFe-EAP migration request form](https://www.servicenow.com/docs/qKuDrSd5Fo7EkAvocUecoQ "Learn about the fields of SAFe-EAP migration form. Use this form to submit a request to migrate Scaled Agile Framework data to Enterprise Agile Planning.").  
   Hinweis:  
   * Planning intervals, formerly known as program increments, can only be migrated one time per team. Planning intervals falling before the selected date in the migration request and those created after the migration is complete, cannot be migrated through the automated migration (Guided Setup).For example, submit migration requests in the sequence of PI 1 \> PI 2 \> PI 3 and so on.

   * If the composition of a SAFe ART has been changed any time after it is created, it is suggested to migrate only those PIs that have the current composition of the ART.
   * For a Portfolio SAFe migration, if a SAFe Epic is associated with SAFe Features but is not linked to any Portfolio, then this Epic will not be migrated by the automated migration.
   * Migration can be run multiple times for the same criteria. In such case, any newly created records will be migrated to EAP.
   * If changes are made to already migrated SAFe records, these changes will not be synched with the EAP records.
   {#migrate-safe-data-to-eap__ul_km5_vsl_zbc}
4. Select Submit.  
   Wichtig:  
   Submitting the request does not trigger the migration. Open the submitted recorded from the SAFe Migration requests list and select Start migration.

## Ergebnisse

Monitor the progress of data migration:

* If the migration is successful, the Import Requests related list shows the details of the data migration such as failed count, insert count, and total count of records moved from SAFe to EAP.
* If the migration encounters any error, the Migration Errors related list shows the details of records that failed to migrate from SAFe to EAP.
{#migrate-safe-data-to-eap__ul_lbv_qwx_dcc}

## Nächste Maßnahme

[Add Agile Team type to SAFe groups for EAP migration](https://www.servicenow.com/docs/tkNxOQo15aVbL7L3Pc4dxw "Add Agile Team in the Type field of existing SAFe groups to so that these teams are visible for your EAP users in the workspace.").