Understanding Multi-Org Connect

In a multi-org connect setup, each connected user on the Salesforce side can handle up to 5 business units, according to best practices recommended by Salesforce support. This means that if an organization has more than 5 BUs, they would need to establish multiple connections.

For example, if a company has 12 BUs, they would need to set up 3 separate connections to cover all their BUs, as each connection can support up to 5 BUs. This is crucial for planning and setting up the infrastructure to support the multi-org connect model.

Sharing Components Across BUs

Regarding the sharing of components, such as those managed through a package manager, the main consideration is how these components are referenced and accessed across different BUs. Since the synced data extension names will differ between BUs, any sharing or migration of components must account for these differences.

Teams running Journey Builder or using Automation Studio may need to adjust their workflows and scripts to accommodate the nuances of a multi-org environment, ensuring that components are correctly referenced and shared between BUs.

The root cause of the complexity in sharing components across BUs in a multi-org connect setup is the difference in synced data extension names and the limitation on the number of BUs a single connected user can handle.

Implementing the Solution

To implement a solution that allows for the sharing of components across BUs in a multi-org connect environment, teams should first assess their current component management processes and identify any areas that may be impacted by the move to multi-org.

Next, they should plan their multi-org connect architecture, taking into account the need for multiple connections if they have more than 5 BUs. This planning phase is critical for ensuring a smooth transition and for maintaining the ability to share components effectively.

Example SSJS Script

var buName = "BusinessUnitName";
var deName = "DataExtensionName";
// Adjust the script to account for differing DE names across BUs

Heads up: Always test your scripts and workflows in a sandbox environment before deploying them to production.

Checklist for Migration

Pre-Migration Checklist

• Assess current component management processes.
• Plan multi-org connect architecture.
• Determine the need for multiple connections based on the number of BUs.
• Adjust scripts and workflows to account for differing data extension names.
• Test all changes in a sandbox environment before deploying to production.

Frequently Asked Questions

What is the maximum number of BUs a single connected user can handle?

According to Salesforce best practices, a single connected user can handle up to 5 business units.

How do I share components across BUs in a multi-org connect setup?

You need to adjust your scripts and workflows to account for the differences in synced data extension names between BUs.

Do I need multiple connectors for more than 5 BUs?

Yes, for more than 5 BUs, you would need to establish multiple connections, with each connection supporting up to 5 BUs.

How do I plan for the migration to multi-org connect?

Start by assessing your current processes, planning your multi-org architecture, and testing all changes in a sandbox environment.