A pending platform acquisition is a reason to review a renewal, not evidence that a migration is ready. Salesforce’s proposed purchase of Braze puts that distinction on the agenda for CRM and marketing leaders: keep essential customer journeys working while preserving room to change the architecture later.
Salesforce announced the agreement on 20 October at approximately $5.66 billion in enterprise value. It expects closing in its fiscal year 2028, subject to shareholder and regulatory approvals and other conditions. German trade publication HORIZONT revisited the implications on 22 October. An announced transaction and a delivered combined product remain different milestones.
Separate a contract decision from a product forecast
The immediate question is what the business needs to buy for the next service period. That includes the customer journeys already producing value, the capacity needed to operate them and the people required to maintain them. A potential future integration should sit in a separate planning column until there is a documented offer to evaluate.
The announcement does not establish a common price list, a mandatory migration or a retirement date for an existing product. Do not put those assumptions into a business case. Equally, do not count expected integration savings as money available to fund this year’s campaigns. Ask the vendor to distinguish contractual commitments from roadmap intentions in writing.
Audit the dependencies that make switching expensive
Build a compact register of the journeys that would be costly to interrupt: onboarding, replenishment, service messages and reactivation, where relevant. For each, name the owner, event source, customer identifier, consent requirement and downstream channel. This is our suggested operating check, not a migration requirement announced by either company.
Then test portability on a small representative sample. Can the team export the data it is entitled to use, recover message assets and explain the rules that determine who receives what? An export file alone is insufficient if the logic, suppression rules or identity mapping cannot be reconstructed. Keep essential service communications in the review as well as promotional campaigns.
Take specific questions into the renewal
Ask which products, service levels and support arrangements are covered for the proposed term; how usage is measured; and what happens if needs change before the term ends. Request clarity on export assistance, implementation scope and the commercial treatment of any optional future integration. These are procurement questions to resolve with the supplier, not predictions about a contract changing automatically.
A team with a renewal due soon and no validated replacement should price continuity alongside its alternatives. A team already running a replacement evaluation can continue testing against its own requirements. In both cases, assign a decision date and an accountable owner so that waiting for news does not become an unplanned extension.
Budget for continuity and conditional integration separately
Use three budget lines: committed service operation, portability and dependency work, and integration work that needs further evidence. Include internal engineering time, campaign QA and overlapping operation when comparing options. Avoid treating a potential reduction in vendor count as proof that the total operating cost will fall.
The useful next deliverable is a one-page renewal brief: what must keep running, what the supplier has committed to, what can be exported, what remains uncertain and when the decision will be revisited. That gives a CMO something concrete to approve while the proposed transaction follows its own timetable.
Sources
- Salesforce Signs Definitive Agreement to Acquire Braze
- Salesforce übernimmt Braze – was dies jetzt bedeutet
