Salesforce signed a deal to acquire Braze. Your martech roadmap did not sign anything.
On October 20, Salesforce announced a definitive agreement to buy Braze for about $5.66 billion in enterprise value. The companies expect the transaction to close in Salesforce's fiscal year 2028, subject to shareholder approval, regulatory review, and the other conditions that live in merger documents for a reason.
That timeline matters. A signed deal is a real event. A combined product is still a promise about the future.
Salesforce says Braze would strengthen Marketing Cloud with real-time customer behavior, mobile and app engagement, cross-channel messaging, and AI decisioning. Those are plausible areas of fit. The announcement uses the careful words “expected to complement” for a reason. The companies have not published a finished integration map, packaging plan, migration schedule, or post-close price book.
So skip the emergency replatforming meeting. Do something less theatrical and more useful: make sure your stack can move when the evidence arrives.
A merger announcement is a reason to document your options, not surrender them.
Start with the facts that exist today
The transaction documents give buyers a clean boundary between confirmed facts and roadmap talk.
- Salesforce agreed to pay $47.50 in cash for each share of Braze Class A common stock.
- The transaction is expected to close in Salesforce's fiscal year 2028.
- Closing still depends on Braze shareholder approval, regulatory approval, and customary conditions.
- Braze would continue as the surviving corporation and become a wholly owned Salesforce subsidiary after the merger closes.
Those details appear in Braze's Form 8-K and the filed merger agreement. Save those sources. Then put every product claim you hear into one of three columns: available now, contractually committed, or proposed.
“The account team said” belongs in a fourth column marked follow up in writing.
Run the 45-minute keep-your-options-open review
Use this as a quick exposure check for the system you already run. Save the vendor bake-off for later.
1. Draw the live data path
Start with one important customer action, such as a purchase, application, renewal, abandoned cart, or booked consultation. Trace it from the source system into the customer profile, through the audience rule, into the message, and back to reporting.
Name the system that owns each field. Note the direction of every sync. Mark any transformation that changes an ID, consent state, timestamp, revenue amount, or channel eligibility.
If your diagram ends with three arrows labeled “Salesforce,” start again. Sales Cloud, Data 360, Marketing Cloud, Service Cloud, middleware, and a warehouse can hold different versions of the customer. The logo does not settle which record wins.
2. Test the exports you already have
Do not wait for a migration project to discover that “our data” meant “the rows available in this particular subscription tier.”
Braze documents several ways to move data out. Currents can stream granular engagement events into warehouses and analytics partners. Braze's architecture overview also describes Snowflake sharing, export APIs, and dashboard CSVs. Access and completeness vary by feature, entitlement, data type, and implementation.
Pick a recent seven-day period and export it now. Count profiles, campaigns, events, channel outcomes, subscriptions, consent fields, and custom attributes. Compare the export to the source systems and the dashboard. Record what is missing, renamed, aggregated, delayed, or available only through an add-on.
A successful download proves that a file arrived. A portability test proves that the data is understandable and reconcilable somewhere else.
3. Inventory the dependencies nobody put in the contract summary
The platform is rarely the whole platform.
- Which SDKs are embedded in websites and mobile apps?
- Which journeys depend on webhooks, APIs, server events, or reverse ETL?
- Which templates contain custom code, content blocks, or channel-specific logic?
- Which identity rules merge anonymous and known users?
- Which agencies, consultants, or internal teams can actually operate the setup?
- Which consent and suppression rules have to survive any move?
Score each dependency as documented, partially documented, or trapped in somebody's memory. That last category is where replatforming budgets go to die.
4. Put the commercial dates on one page
Write down the renewal date, notice deadline, committed spend, usage limits, data-export entitlements, support level, implementation credits, and any price protection. Add the owner for each negotiation.
Then ask both vendors the same questions:
- Which current products and support commitments remain unchanged before close?
- Which proposed integrations are generally available, in pilot, or still conceptual?
- Will using a proposed connection change data location, subprocessors, consent handling, or contract scope?
- What will the customer receive in writing before any packaging or pricing change?
- What export and transition assistance is included if the customer chooses another direction?
A cheerful roadmap slide will not protect the renewal. Dates, entitlements, and written commitments might.
5. Define the proof that earns a consolidation decision
“Fewer vendors” sounds efficient until one platform bill contains four clouds, three services partners, and a small museum of unused credits.
Choose one business workflow and set a proof threshold. For example: a customer changes subscription status in the source system, becomes ineligible for a promotional journey within 15 minutes, disappears from the active audience, receives no further messages, and appears correctly in the warehouse and campaign report.
Test the current setup first. Later, test any combined Salesforce and Braze workflow against the same standard. Compare labor, latency, failure recovery, permissions, reporting, and total cost. A prettier architecture diagram gets no points.
Three bad reactions to avoid
Do not migrate because the logos moved closer together. The transaction has not closed, and the future product shape is not settled.
Do not assume staying put requires no work. Untested exports, undocumented identity rules, and missed renewal dates reduce your leverage with any vendor.
Do not make the acquisition your data strategy. Your warehouse, consent record, source systems, customer identifiers, and measurement definitions should remain legible outside one vendor's pitch deck.
This is the same basic discipline behind SigServe's tracking-plan audit and marketing measurement check: name the system, owner, evidence, and decision before adding another layer of automation.
The one-page acquisition response
Keep the deliverable short enough that somebody will use it:
- confirmed transaction facts and source links;
- renewal and notice dates;
- one live data-flow diagram;
- export methods, entitlements, and test results;
- critical integrations and their owners;
- open vendor questions and written answers;
- one workflow to benchmark before and after any change;
- migration triggers, hold conditions, and a review date.
The stop rule is simple. Do not approve a consolidation, migration, or early renewal when the team cannot reproduce its data, name the operational dependencies, and compare the proposed workflow against a working baseline.
Salesforce may eventually make Braze easier to buy, connect, and operate. Good. Let the product and contract prove it. Until then, keep the cables labeled.
Can your marketing stack explain itself without the sales deck?
SigServe can help you map the data, dependencies, owners, and proof needed before a major platform decision.