Salesforce Is Buying Braze. Protect Your Email Templates Now
Salesforce has agreed to acquire Braze for about $5.66 billion. Nothing changes for Braze senders today, but it is a good moment to make sure your email code is portable.
Salesforce has signed a definitive agreement to acquire Braze for $47.50 per share in cash, about $5.66 billion in enterprise value. The deal was first announced on October 20, 2026, and coverage and regional releases kept rolling out through the last week of October. It isn't done yet. Salesforce expects it to close in its fiscal year 2028, and it still needs Braze shareholder approval and regulatory sign-off.
If your agency or brand sends through Braze, nothing changes today. Your account, your templates and your sends work exactly as they did last week. But a big platform change is a good reason to check how portable your email code really is, before anyone forces the question.
What we actually know
Here's what the official announcement says, and what it doesn't:
- Price and timing: $47.50 per share, about $5.66 billion, expected to close in Salesforce's fiscal 2028.
- Where Braze fits: Salesforce says Braze is expected to "strengthen Marketing Cloud's cross-channel personalization" and connect with its customer data and Agentforce.
- The brand: Braze co-founder Bill Magnuson said "we'll continue building as Braze." That suggests the name stays, but neither company has confirmed any long-term product plan.
- Contracts, pricing and roadmap: The release doesn't address any of these. Anything you read about price rises or forced migrations right now is speculation.
Both companies talk about "an open, composable approach." In Digiday's coverage (October 26), marketers said they want to see what that means in practice: data access, interoperability, and how easy it stays to move campaign assets and logic elsewhere.
Why I'd act now anyway
After 12+ years of building emails, I've seen what happens when a platform changes hands. It rarely breaks overnight. What hurts is finding out, months later, that your templates only exist inside one editor, nobody knows which modules are live, and the personalization logic is undocumented.
That's a risk whether or not anything changes at Braze. The acquisition is just a good reminder to deal with it.
A portability checklist for Braze senders
1. Keep a master copy of your HTML outside the ESP. Every live template and module should exist as a file you control, ideally in version control. If your only copy lives in the Braze editor, export it now.
2. Document your Liquid. Braze personalization runs on Liquid. Write down which templates use which variables, custom attributes, Connected Content calls and fallbacks. Salesforce Marketing Cloud uses AMPscript, so if templates ever needed to move there, that logic would have to be rewritten. Nobody has said that will happen. Documentation just makes any future move cheaper.
3. Separate structure from platform code. Keep layout, styles and modules clean, and keep ESP-specific tags in clearly marked spots. Email code built that way can be re-wired to a new platform in hours, not weeks.
4. Take a QA baseline. Run your core templates through your rendering tests now and save the screenshots. Include dark mode and a screen reader pass. If anything changes later, you'll have a clear before-and-after.
5. Know your sending setup. Note your sending domains, IPs, and SPF, DKIM and DMARC records. In Digiday's report, keeping deliverability intact was one of marketers' main worries about any platform move, and good records make that much easier.
For agencies managing several Braze clients
If you run Braze for clients, you'll likely get questions. A short, calm note helps: what's known, what isn't, and that you're keeping their templates portable either way. It shows you're on top of things without adding to the noise.
This is also exactly the kind of work I take on white-label: auditing a template library, pulling it into clean, documented, ESP-agnostic HTML, and setting up a QA baseline your team can reuse.
Bottom line
Don't panic and don't migrate. Just make sure your email code, logic and test results belong to you and not only to a platform. That's good practice regardless of who owns Braze next year.
Related on the Journal
If you'd like a template library audited and moved into clean, documented, portable HTML, white-label or direct, get a quote.
Sources
- Salesforce Signs Definitive Agreement to Acquire Braze (opens in a new tab), Salesforce Investor Relations, October 20, 2026
- Salesforce Signs Definitive Agreement to Acquire Braze (opens in a new tab), Salesforce India newsroom, October 27, 2026
- Salesforce's $5.7 billion Braze deal puts marketers at an ecosystem crossroads (opens in a new tab), Digiday, October 26, 2026