Understanding SAFe-to-EAP Re-migration: Why Existing Records Are Not Updated

[AmulyaB]

 

What is SAFe-to-EAP Migration?

SAFe-to-EAP migration is a one-time process that moves your SAFe data like  Portfolios, ARTs, Teams, PIs, Sprints, Epics, Features, Stories, and Tasks into the Enterprise Agile Planning (EAP) workspace, creating corresponding EAP records for each SAFe entity.

What Does Re-migration Do?

Re-migration is designed to pick up only what was missed or added after the initial migration. If you added a new SAFe team, created new stories, or introduced new features after the first migration, re-migration will create those new records in EAP. It does not revisit or update records that were already migrated.

Why Doesn't Re-migration Update Existing Records?

Once a SAFe record is migrated to EAP, the EAP record becomes the source of truth. Users may have already made changes to that record directly in EAP, updated descriptions, reassigned teams, added comments, adjusted story points, linked dependencies, or attached files. These are changes that only exist in EAP and have no counterpart in SAFe.

If re-migration were to overwrite EAP records with SAFe data, all of those EAP-only changes would be silently lost with no way to recover them. The migration is intentionally designed to protect the work done in EAP after migration.

What Should You Do Instead?

Once migration is complete, all ongoing work should be managed directly in EAP. Do not continue making changes in SAFe with the expectation that re-migration will push them to EAP.

Use re-migration only when you need to bring over newly created SAFe records that were not part of the original migration scope.

Key Takeaway

SAFe-to-EAP migration is a one-way bridge, not a sync. Once records cross over to EAP, they live and are managed there. Re-migration opens the bridge again only for new items, it does not go back to update those are already migrated.