Coexistence of Zuora Multi-Entity and Zuora Multi-Org
Zuora's multi-org. feature is designed to cater to the needs of various customers. These include customers who expect autonomy over settings and require hard segmentation of organizational or business boundaries. Especially when businesses do not need to be intermingled or need to run regionally. And that is why the coexistence of Multi-Org. and the existing Multi-Entity framework becomes indispensable.
Migrating from Multi-Entity to Multi-Org.
There are 3 use cases where a business would want to migrate to multi-org. from their existing multi-entity setup.
- Upgrading a sub-entity in an existing multi-entity setup to Zuora Multi-Org.
- Collapsing all the sub-entities in a multi-entity setup into a single instance of Zuora Multi-Org.
- Disconnecting a sub-entity in a multi-entity setup after it has been upgraded to Zuora Multi-Org. and running it as a standalone tenant.
Each of the aforementioned use cases involves an upgrade to Zuora Multi-org. The two upgrade scenarios are mentioned below:
| Upgrade to Zuora Multi-Org. with existing transactional data | If there is existing transactional data in the sub-entity being upgraded to Zuora Multi-Org., then you would need to upgrade the sub-entity by following the Zuora Multi-org. upgrade process. |
| Upgrade to Zuora Multi-Org. with no transactional data | If the sub-entity to be upgraded is a new sub-entity or tenant then you can upgrade to Zuora Multi-Org. before using the tenant for any transaction. |
Upgrade to Zuora Multi-Org. with existing transactional data
This section explains Use case 1 in detail on how a business having an existing Multi-entity environment can upgrade a sub-entity within that Multi-Entity setup to Zuora Multi-Org.
Here are a few terms and concepts to familiarize yourself before getting started:
| Zuora Multi-Entity | Zuora Multi-Org. |
|---|---|
|
Root The root is referred to as the global entity (By default) but you can select a preferred root name. |
Root Root is referred to as the global organization (default parent) |
|
Sub-Entity Each child entity under the global entity is referred to as a sub-entity. |
Org. Units Each of the children under the root is referred to as an org. unit. |
Points to remember before upgrading a Multi-Entity sub-entity to Zuora Multi-org.
- Only a leaf sub-entity in a Multi-Entity setup can be upgraded to Zuora Multi-Org.
- User access controls and data segmentation will have to be setup separately for Zuora Multi-Org. sub-entity as compared to the existing Multi-entity setup. The user and application behavior may vary for Zuora Multi-Org. from Multi-Entity.
- You must have Zuora Universal User (One ID) activated for a seamless login experience between Zuora Multi-Entity and Zuora Multi-Org. sub-entity.
- The behavior of platform components like custom objects, workflows etc., may vary between Zuora Multi-Entity and Zuora Multi-Org. sub-entity.
- Financial roll-ups will work for Zuora multi-Org. sub-entity and may not be applicable for Multi-Entity.
- Settings including Invoice Numbering, Product in the Product Catalog, Product Rate Plan Changes, Notifications, etc. that exist at a per-entity level will be applied at the tenant level post upgrade and apply to all org. units in Zuora Multi-Org.
- Product sharing across sub-entities in a Multi-entity setup will differ from sharing products in the product catalog in Zuora Multi-Org. setup.
- Any transactional data within a closed accounting period will be subject to the labeling and data segmentation rules of Zuora Multi-Org. The same will apply to any transactional data in the accounting period that closed after the enablement of Zuora Multi-Org.
- Zuora Revenue will exclusively sync 1:1 through the OTR sync with each org. unit defined in Zuora Billing.
Steps to Upgrade to Zuora Multi-Org. Zuora Multi-Org. upgrade through API's
Upgrading a leaf sub-entity of Multi-Entity with existing transactional data to Zuora Multi-Org. is done through the Multiple Organization APIs.
- Create a Zuora Multi-Org. organizational hierarchy
- Label the key objects:
- Customer Accounts
- Products in the Product Catalog
- Users
- Repeat Step 2 to label all the key objects. Any unlabeled object shall be defaulted to the root (Multi-org Parent, but will not be accessible by any of the child Org Units)
- Review the audit log actively for labeling changes to the key objects.
- After thoroughly reviewing, ensure that appropriate internal change management actions are initiated to familiarize your org users with their visibility within the organizational hierarchy.
- Verify and activate Zuora Multi-Org.
In addition to the three key objects specified in Step 2, at least 100+ dependent objects will also be labeled based on the labels created in Step 3.
See the Multiple Organizations API reference for details about data labeling.
Once Zuora Multi-Org. is activated in the sub-entity of the Zuora Multi-Entity setup, data segmentation rules take effect. As a result, any user that had access to all the data within the sub-entity will be restricted to access only the data based on the user's roles in the Multi-org. the setup provided by the IT admin. And the org unit that the user now belongs to.