Migrate from Salesforce to Braze

Most teams that migrate successfully start evaluating 12–18 months before their contract expires. Some overlap between contracts is unavoidable — but teams that give themselves that runway use the migration as a chance to reset and improve their marketing operations, not just lift and shift. We can help you think through the sequencing and build the internal business case well before you need to make a decision.

It’s worth understanding what you’re actually being asked to do. Marketing Cloud Next is a rebuild of Marketing Cloud inside the core Salesforce platform, which means it runs on different UI patterns, has a different data model, and currently supports a fraction of the features most teams rely on in the legacy product. AMPscript, Content Builder, and mature journey logic are all either stripped down or absent. The brands we’re aware of who have evaluated it have largely deferred or stayed on legacy MC in parallel. If you’re being asked to pay for a migration regardless, that’s the moment to ask whether the destination is actually better. We don’t recommend it, and we’ll tell you why in as much detail as you need.

From the “migrations” and proofs-of-concept that our team has done in former roles, the biggest differences are that Content Builder is gone, replaced by a drag-and-drop editor that’s less mature than most mid-market tools. AMPscript support covers only basic functions — a fraction of what the language can do. The platform is now natively inside Sales Cloud and Service Cloud, which is great for a sales team but a significant context shift for a marketing team. Most clients who have piloted it still run their legacy Marketing Cloud instance alongside it, which means it’s less of a transition and “running two platforms at once.” The honest truth is that the feature parity gap between Next and what you’re used to is substantial, and Salesforce hasn’t provided a clear roadmap for closing it.

Data Cloud has real technical capabilities — identity resolution, streaming ingestion, and a zero-copy connector to Databricks are legitimately useful. The challenge is the gap between the pitch and the implementation reality. Most large enterprises using Data Cloud today are primarily using it as a pipeline to activate data into Marketing Cloud — not unlocking the more sophisticated use cases. Onboarding is a significant undertaking even for straightforward scenarios, and it requires your marketing team to operate across two platforms with two learning curves. If you’re in a Salesforce renewal and being presented with Data Cloud as the answer to your data problems, we’d encourage you to evaluate whether your data problems actually require a second Salesforce platform — or whether they’d be better solved by connecting a best-in-class engagement tool to where your data already lives (like Databricks or Snowflake).

Easier, actually. If you’re already activating customer data in Data Cloud, you’ve already done the hardest part — you’ve built a unified view of your customer. Braze’s user profile architecture mirrors Data Cloud’s unified profile concept closely, so the data model work translates. And if you’re on Databricks, the zero-copy connector means you can activate that same data layer directly into Braze without replicating it. The segment and identity work you’ve done doesn’t go to waste — it becomes the foundation of how Braze personalizes.

They’re not really comparable — Data Cloud is a data layer, Braze is an engagement platform. But if the question is whether Braze can replace the activation use cases you’ve been told Data Cloud solves: yes, in many cases it can. Braze ingests data natively from your warehouse, supports real-time behavioral triggers, and has its own identity resolution capabilities on the roadmap. The meaningful difference is speed: Data Cloud’s activation into Marketing Cloud is a batch process — data takes hours to move. Braze fires in seconds. For lifecycle marketing, that gap matters more than most teams realize until they’re on the other side of it.

The idea is that sending at the exact right moment — not necessarily the fastest moment — is what drives results. We don’t disagree with the principle. Where we’d push back is on whether the Salesforce platform actually delivers on it. “Right time” requires rich, real-time behavioral data and the ability to act on it immediately. Braze processes behavioral signals in seconds and fires journeys in response. The ability to send at the right time depends on having the data infrastructure to know what that moment is — and for most brands, Braze + Databricks gets you there faster, with less technical overhead, than the Salesforce stack.

It’s real, and it’s worth factoring into renewal decisions — particularly if you’re in healthcare, financial services, or any regulated industry. In late 2025, a zero-day exploit targeting Marketing Cloud was disclosed, followed by a disruptive Salesforce patch in early 2026 that caused significant operational issues for many clients. The exploit method was subsequently published publicly. Salesforce’s response posture has been reactive — forced API credential rotations, sudden multi-factor auth rollouts — rather than proactive. That’s not a reason on its own to make a platform decision, but it’s a meaningful input for security and IT stakeholders who are part of your evaluation.

The short answer: we don’t know. The long answer: probably not any time soon. But, Salesforce has made clear that their focus for product investments will be in their data and AI infrastracuture, and they will stop reporting on marketing earnings as its own line item. So that tells us they will no longer be evolving their legacy Marketing Cloud tools, and will likely funnel any future marketing product investments into Marketing Cloud Next. We’re assuming that you’re here because you want to invest in marketing, so we recommend taking into account whether or not your martech vendors will push you forward or hold you back.

The framing that tends to work: “Our current setup is limiting what marketing can deliver, and here’s the cost of that.” Leadership needs to see quantified gaps — the revenue impact of 2–3 programs you can’t run or can’t run well, the full cost of ownership beyond the license fee, and a phased approach that shows business-as-usual is protected during the transition. We help clients build this case. Present it as a series of smaller decisions, not one enormous lift.

Generally yes — modern marketing platforms have open APIs and data is extractable. We’ve pulled down large client instances with hundreds of automations running and used AI to audit which ones were actually driving value. The more important question is what to bring vs. what to leave behind. Not everything in your current instance belongs in Braze — some of it belongs in your data warehouse. Migration is the right moment to sort that out.

The honest range is 3 to 18 months, depending on the complexity of your business and how many platforms you’re integrating. The most common pattern: teams that expect 18 months land in 9. The single biggest variable isn’t campaign volume — it’s whether your data already lives in a modern warehouse. If you’re on Databricks or Snowflake, you’re connecting Braze to where your data already lives. That’s a significant lift off the project.

The goal is always to keep sends running, and we structure migrations to run both platforms in parallel during IP warming — sending from both simultaneously during the transition. Our approach to scoping a migration is to take a “zero risk” approach — starting with careful, thoughtful planning for resourcing, integrations, seasonality, and other internal initiatives, then activating that plan with tight project management and clear communication.

Existing CRM integrations — Sales Cloud, Service Cloud — hold. Braze connects to the same APIs, so your customer service agents typically don’t see a difference. Our preferred approach is a Lightning component inside your CRM that pulls engagement data from Braze or your warehouse on demand, giving agents a richer, more timely view than most teams had before.

Not necessarily, but if you already have one — Databricks, Snowflake, Redshift, BigQuery, Microsoft Fabric — Braze is built to work with it natively. You can query your warehouse directly, sync data into Braze profiles on a cadence you control, or use zero-copy triggers to fire a journey based on warehouse data without ever moving it into Braze. Whether you need a CDP depends on your stack and use case — a separate conversation we’re happy to have.

Yes — all channels in Braze run off a single customer profile and a single data model. Email, SMS, push, in-app messages, content cards — one profile, one place to build and measure. As new channels emerge, they’re fast to stand up because the infrastructure is already there.

More than you’d expect. The core principles of lifecycle marketing don’t change — audience segmentation, journey logic, KPIs, campaign strategy all carry over. What changes is the tool. A lot of the Stitch team has deep backgrounds in Salesforce AND Braze, and have found that transitioning from focusing on Salesforce to focusing on Braze didn’t result in lost momentum for them — but rather, has helped them learn new platforms quickly.

The biggest signal is specificity. Vague answers about “best practices” usually mean a vendor hasn’t actually done the work. Look for a partner who can get granular about how things will function post-migration, not just how the migration itself will run.

What happens to my data architecture, not just my data?

A real migration partner redesigns your data model for how Braze thinks about users, events, and canvases, rather than lifting and shifting your SFMC structure as-is. If a partner can’t explain how your data model changes, expect personalization problems to show up months after cutover.

How do you decide what not to migrate?

Every SFMC instance accumulates dead journeys and segments nobody remembers building. A partner who migrates everything 1:1 is avoiding a harder conversation about what’s actually driving revenue. Ask for a prioritization framework, not a promise to “migrate it all to be safe.”

Who owns the Braze instance 30 days after cutover?

Cutover day gets all the attention, but the month after is usually where migrations succeed or fail. A strong partner builds in enablement and knowledge transfer so your team has real ownership, not a handoff doc nobody opens.

What’s the plan if a journey breaks in production?

Speed and care can conflict in practice. Ask what happens when a critical lifecycle journey misfires mid-migration. The answer reveals whether their methodology is a real operating discipline or just a talking point.

How do you sequence migration around an active campaign calendar?

Your team doesn’t get to pause marketing during a migration. A good partner plans around your always-on flows and campaign calendar instead of treating the project like a clean greenfield build.