The Data Labeling APIs help you to label your existing data with organization(s) in Zuora.
Once you turned on Multi Org feature, if you don't label your existing data, they are simply unlabeled, and unlabeled data can be accessed by all organizations in your tenant.
To limit the access of your existing data, you need to label them with organization(s) you defined in the organization hierarchy management setting page. Once labeled, the data can only be accessed by users who have been granted with the labeled organization(s).
Note that you have to enable the "Multi Org" feature before using the Data Labeling APIs.
Firstly, create the org hierarchy and determine the data categorization strategy, for example, by currency, by region, by custom fields etc.
You have to migrate all customer accounts before labeling products in the product catalog
You can leave the users at the root, just so long as you understand that the user would have access to all the Org Units within the Multi-org enabled tenant
Currently, you need to manually label existing Journal Runs, JournalEntry, and AccountingPeriod objects by editing, tell us your use case if you want to automate this process.
Product, there are no dependencies between objects, users can label them in parallel.
But please keep in mind that the data access control ensues from the object labeling. For example, if you label a scheduled
US org, when it's triggered next time, the bill run will only pick up customer accounts of the
US org, not others.
Likewise, labeling a user will change the user's visible data scope, for example, an
EU user won't be able to see
US accounts anymore.