Hi @david.pinn,
Thanks for the question. App Migration doesn’t have to be tied directly to the Jira Projects or Confluence Spaces being migrated. All the migrated data like issue ids or content ids are available in subsequent migrations between the same server and cloud site for (up to) 14 days.
One option is to keep a diff of sent data, because ultimately you may find data drift between migrations that you also need to keep up to date.
You can use the feedback channel documented here to keep track of what’s been successfully migrated and what still needs to go
- https://developer.atlassian.com/platform/app-migration/rest/api-group-feedback-channel-api/
- How automated migration works | App migration platform
You can use the feedback channel to send a message back to server to request a re-migration of specific data (or anything, as it’s just an object of any type that you send.)
When you send the data, you can use labels to help identify there data, or send a manifest file first to indicate what will be sent.
So, in answer to the question
What if the customer then runs a second migration for project C? Should our app re-attempt to migrate the project-B-related data that failed earlier?
I would say yes, your app should try and re-send the data for project B using the feedback channel to help identify what needs to be sent.
Hope this helps.
Regards,
James,