You are here:
Recommendations for Existing Marketing Cloud Engagement Customers
For customers who use business units in Marketing Cloud Engagement, we recommend that you create a 1:1 business unit architecture. In other words, for each business unit that you use in Marketing Cloud Engagement, create and map a corresponding business unit in Marketing Cloud Next.
Required Editions
| Available in: Marketing Cloud Engagement Corporate+ and Enterprise+ editions. |
It’s a straightforward process to map a business unit in Marketing Cloud Next. You can also remove a business unit mapping. When you remove a business unit mapping, all the historical Marketing Cloud Engagement data is removed from the Marketing Cloud Next business unit, which can impact use cases that depend on that data.
A fast and flexible starting point is to map the top-level Marketing Cloud Engagement account—that is, the account that has an Enterprise ID (EID)—to the default data space in Data 360. After that, map each child business unit from Marketing Cloud Engagement to a separate data space, if applicable.
When your team is getting started with Marketing Cloud Next, we recommend that you create one or two pairings to begin with, as illustrated in this diagram.
Adding More Business Units
The flexible design of business units in Marketing Cloud Next makes it possible to add new business units at any time without disrupting your existing marketing data and content. As your business grows, add new business units and data spaces in Marketing Cloud Next, as illustrated in this diagram.
Alternate Architecture: Hierarchy
Business units in Marketing Cloud Next don’t use a formal hierarchy in the same way that Marketing Cloud Engagement does. However, you can create an informal hierarchy by mapping a single Marketing Cloud Engagement business unit to multiple data spaces. By using this architecture, you can provide a single view into analytics across all of your business units.
Begin by mapping each Marketing Cloud Engagement business unit 1:1 to its own data space. Next, add mappings to a common data space to create a hierarchy. In this diagram, the red arrows indicate the initial connections from Marketing Cloud Engagement business units to the dedicated data spaces for each Marketing Cloud Next business unit. The blue arrows indicate subsequent connections between the child Marketing Cloud Engagement business units and the consolidated Marketing Cloud Next data space.
Alternate Architecture: Business Unit Consolidation
Your account can create a limited number of business units based on the entitlements in your contract. If you have existing business units in Marketing Cloud Engagement that you don’t use, consider consolidating them in Marketing Cloud Next. Connect the top-level Enterprise account to the default data space, and then connect all the child business units from Marketing Cloud Engagement to a single, separate data space.
Alternate Architecture: Multitenant Consolidation
Business units in Marketing Cloud Next make it possible to bring several Marketing Cloud Engagement tenants together under a unified architecture. Unifying tenants gives you simplified permission management, easier data duplication, and global visibility into metrics across all business units. This diagram illustrates an architecture that combines multiple Marketing Cloud Engagement tenants into a single Marketing Cloud Next org with multiple business units.
Alternate Architecture: Multi-Org Expansion
Alternatively, you can move from a single Marketing Cloud Engagement tenant to multiple dedicated Salesforce orgs. This architecture is useful for situations where you want complete isolation of Salesforce orgs. For example, you can create a sandbox org that is isolated from your production org, as shown in this diagram.
