Hi ,
Thanks for the response, that was helpful!
I do have a couple follow-up questions based on your response. You wrote:
If the three apps are grouped, the primary app's bundle ID can be used for user migration requests—its user accounts will include all of its child app accounts as well.
The three apps are grouped currently, but according to the document Overview of app transfer, we should un-group them prior to the transfer. My understanding is that after ungrouping them, there no longer will be a single primary that covers all three apps. At that point then, will it matter which AppID we use for the transfer?
The reason for that question is that there's one other detail I didn't mention in my original question (to keep it simple), but might now be relevant. Our apps are grouped using a primary App ID that was created manually in the developer portal, but doesn't actually belong to any real app (and therefore won't be transferred). So all three apps are currently grouped using a primary AppID which doesn't belong to any of these three apps themselves, but rather a special AppID that we created solely to act as the primary. (We acknowledge this might be an unusual setup, but there were "reasons" 🙂)
So if, as you suggested, we're need to use the primary AppID (or at least the AppID that was the primary prior to un-grouping), can we use this non-app AppID for the migration requests? Or do the migration requests require that it be an AppID of an app that is actually be transferred? And if the latter, we're back to asking whether will it matter which of the three we use?
Thank you,
Adam
