Marketing Cloud Next Business Units: The Mapping Choices You Can't Undo

The short answer: Marketing Cloud Next organizes marketing by business unit, and each business unit sits on a Data 360 Data Space. Salesforce recommends mapping each Engagement business unit 1:1 to a Data Space and connecting only one or two in your first 60 days. Two choices are hard to reverse. You can't uninstall the Marketing Cloud app from a Data Space later. And removing a wrong mapping also removes that business unit's historical Engagement data from the Next side.

Why this matters now

Your admin opens the Setup Assistant on day one. Step four asks which Engagement business units to connect. It looks like a checkbox.

It isn't. Salesforce's 60-Day Action Plan gives business unit strategy its own slide and its own warnings. That makes sense. Engagement business units and Next business units work differently. Salesforce Ben's Spring '26 summary says each Next business unit connects to a corresponding Data Space and gets its own isolated view of campaigns, audiences and reporting. Many enterprises waited for this feature before adopting Next at all.

Your old structure took years to grow. Your new one takes one afternoon to set up. Spend more than an afternoon on it.

How the mapping works

Next features on Lightning run inside their own business unit concept, called a Data Space. You connect your existing Engagement business units so their data syncs and becomes available to Next. Salesforce's default advice is a 1:1 mapping. One Engagement business unit maps to one Data Space.

In Salesforce's example, an Engagement enterprise account maps to the default Data Space, and a child business unit maps to its own second Data Space.

Salesforce Help has a page of recommendations for existing Engagement customers. It adds three points:

• You can add new Next business units at any time without disrupting existing marketing data and content.

• Next business units don't use a formal hierarchy. You can build an informal one by mapping a single Engagement business unit to several Data Spaces.

• If you have Engagement business units you don't use, consider consolidating them in Next.

  
  

The third point matters most. Don't copy years of accumulated structure one for one.

What's easy to change, and what isn't

Action	How hard	Why
Add a business unit mapping later	Easy	Salesforce says you can add mappings easily
Map each Engagement business unit 1:1	Safe	Easier to evolve and avoids unintentional data mixing
Map several Engagement business units to one Data Space	Possible, with risk	Can cause unintended consequences
Remove a mapping	Tedious	Also removes all historical data for that business unit from the Next side, which breaks use cases that depend on it
Uninstall the Marketing Cloud app from a Data Space	Not possible	Salesforce says you can't uninstall it later
Map one Engagement business unit to several Data Spaces	Flexible	Works within one org or across separate orgs

Read the table twice. The easy actions add things. The hard ones undo things.

What to do in the first 60 days

Salesforce recommends connecting only one or two Engagement business units. Pick them on purpose. The first one should hold your first use case.

Follow two rules while you set up:

1. Map 1:1. Each Engagement business unit gets an equivalent Data Space.

2. Install into a production-grade business unit. Choose a Data Space linked to a real Engagement business unit, not a test one. Do your testing in sandbox ors.

Salesforce's Chapter 0 checklist adds one more step. Name your default business unit and the business unit for your first use case before kickoff.

Match your setup to a starting move

If your account looks like this	Start here
One business unit, one brand	Map it to one Data Space and connect it
Several business units by brand or region, with separate data rules	Map each 1:1. Connect only the one or two that hold your first use case
Several business units that exist only because of old sender or permission setups	Ask whether Next needs that split at all before you copy it
Business units used for testing	Leave them out. Use sandbox orgs instead

Salesforce Help backs the third row. It says to consider consolidating Engagement business units you don't use. The rest of that row is our judgment, so test it with your architect.

A second opinion on splitting

A Trailblazer Community post and a longer guide by architect Mateusz Dabrowski argue for starting with a single business unit until a hard requirement forces a split. They say splitting divides segments, flows, content and reporting with the Data Space, and that cross-unit reuse means deployed copies. They also say a Next business unit can't be deleted, that deactivation is permanent, and that business units past the first two need paid add-ons. We haven't verified those points against Salesforce documentation, so check them before you plan around them. They do fit Salesforce's own warning that mapping choices are hard to unwind.

The tension is real. Salesforce's deck says map 1:1. The architect says split only when you must. Both agree on caution. Let your data rules decide, not habit.

Six checks before you install

1. List every Engagement business unit. Mark each one as production-grade or test.

2. Write down what each unit must keep separate. Think data, consent rules, sender domains and who may see what.

3. Choose your default business unit and the unit that will host your first use case.

4. Pick one or two to connect. Write one sentence on why each earns a place.

5. Rehearse in a sandbox org. Salesforce says to test there, not in a test business unit.

6. Get your CRM admin to sign off on the Data Space plan. Data 360 usually sits with them.

   
   

If step 2 turns up a structure nobody can explain, treat that as the real finding. Our rebuild vs. repair framework can help you decide how much to carry forward.

FAQ

1. What is a Data Space in Marketing Cloud Next?

   Salesforce says Next features on Lightning run inside their own business unit concept, called a Data Space. Per Salesforce Ben's Spring '26 summary, each Next business unit connects to a Data Space and gets its own isolated view of campaigns, audiences and reporting.

   
   

2. Can we map several Engagement business units to one Data Space?

   Yes, but Salesforce warns it can lead to unintended consequences. It also says removing a mistaken mapping is tedious.

   
   

3. Can we undo a mapping?

   You can remove it, but it's tedious. Removal also deletes that business unit's historical Engagement data from the Next business unit, which affects use cases that rely on it.

   
   

4. Can we uninstall the Marketing Cloud app later?

   Salesforce says no. Choose the Data Space you install into with care.

   
   

5. How many business units can a Next org have?

   Salesforce Ben's Spring '26 summary says up to 50 per org. A community architect says the ceiling rose to 150 with paid add-ons since Summer '26. Check the current limit and licensing with your account team, because the number of business units can change your bill.

   
   

Next step

Before you click install, have a second set of eyes review your business unit plan. Talk to our Salesforce team. For the wider path, read our Marketing Cloud Next adoption plan.