The ObjectTerritory2Association object does not get populated in the target org for accounts that are manually assigned to territories. This object is used by Territory Management 2.0 and holds the association between accounts and territories. After the deployment, I can see that this bridge object did get populated with the territory linkage for accounts that are automatically assigned to territories. This is expected because an insert of a new account with proper firmographic information will result in the account getting tagged to the correct territory (i.e. if the Account’s “Exclude From Territory” flag is not set to True).
However, there is no option that I can see to include this object in the list of objects to deploy. We need this to carry over the manual territory assignment information to the target org.
A common use case is to populate a sandbox with current territory information so that users can do "what if" territory realignment scenarios using current data without impacting production.