Tenant splits facilitate the separation of data and operations for entities undergoing legal or organizational changes, ensuring isolated access and management.

Tenant splits are for customers who are undergoing a legal entity separation, divestiture, and Mergers & acquisitions. This results in a requirement to isolate data between entities and stringent separation of access and operations.

Corporate carve‑out / spin‑off

A business unit or legal entity is being divested or separated from a group and needs its own Zuora tenant. The goal is to isolate accounts, billing operations, payment flows, and reporting for the spun‑off company.

The goal is to isolate accounts, billing operations, payment flows, and reporting for the spun‑off company.

Group restructuring / M&A realignment

Post‑acquisition or internal reorg, customers want to re‑partition tenants so that specific brands/lines of business live in their own environments, or move out of a group tenant into a new standalone tenant.

Align Zuora operations with the new org structure, simplify governance, and hand off control to the right finance/IT teams.

Operational and configuration isolation

An entity within a multi‑entity tenant wants autonomy: separate product catalog, workflows, integrations, and release/change cadence, without being constrained by shared settings or object sharing from the parent.

Cost / complexity rationalization of a multi‑entity setup

Over time, a multi‑entity tenant can become an awkward grouping; splits are requested to either:

• Simplify a too‑complex hierarchy (one entity pulled out into its own simpler tenant)

• Prepare for eventual consolidation/deactivation of low‑usage entities/tenants elsewhere