Understanding the Challenge

One of the main difficulties in managing multiple environments in SFMC is dealing with data sources, which must be identical in both business units. This can defeat the purpose of having a separate development business unit. As a result, some teams prefer to manage different environments within a single business unit, using folder structures to define unique environments.

Another challenge is that some elements still require manual intervention, and there is no silver bullet to solve all deployment issues. However, there are tools and strategies that can make the process easier.

Available Tools and Strategies

Package Manager has improved over time, but it still cannot do everything. There are also 3rd party tools available, such as SFMC DevTools by Accenture and BLDR.io. Additionally, teams can create their own deployer scripts using SSJS or API.

Some community members are also working on new tools, such as stashr.io, which aims to tackle some of the pain points around dev/prod environments.

The root cause of the challenge in syncing development and production environments in SFMC is the lack of a single, comprehensive tool that can handle all deployment scenarios. As a result, teams must use a combination of tools and strategies to achieve their goals.

Best Practices

To manage multiple environments in SFMC effectively, teams should have a strong plan in place and leverage the available tools and strategies. This may involve using Package Manager, 3rd party tools, and custom deployer scripts, as well as manual intervention where necessary.

deployer script example

/* example deployer script */
var src = 'source business unit';
var dest = 'destination business unit';
// deploy assets from src to dest

Heads up: when using custom deployer scripts, make sure to test them thoroughly to avoid any errors or data loss.

Checklist

• Use Package Manager to deploy assets between environments
• Leverage 3rd party tools, such as SFMC DevTools or BLDR.io
• Create custom deployer scripts using SSJS or API
• Use folder structures to define unique environments within a single business unit
• Test deployer scripts thoroughly to avoid errors or data loss
• Have a strong plan in place to manage multiple environments

Frequently Asked Questions

What is the best tool for deploying assets between SFMC environments?

There is no single best tool, but Package Manager and 3rd party tools like SFMC DevTools can be effective.

Can I use custom deployer scripts to deploy assets between environments?

Yes, custom deployer scripts can be used, but they require careful testing to avoid errors or data loss.

How can I manage multiple environments within a single SFMC business unit?

Use folder structures to define unique environments within a single business unit.

What are some common challenges when managing multiple SFMC environments?

Common challenges include dealing with data sources, manual intervention, and the lack of a single comprehensive deployment tool.

Are there any new tools or features that can help with SFMC environment management?

Yes, new tools like stashr.io are being developed to tackle some of the pain points around dev/prod environments.