Hybrid Implementations in Salesforce: A Technical Flaw or a Smart Transition Strategy?
For enterprise architects and IT leaders, a new Salesforce product launch usually brings a mix of excitement and skepticism. The arrival of Marketing Cloud Next (MCN) is a perfect example.
MCN introduces a powerful new paradigm built directly on the Salesforce Core platform, designed to transform how we implement marketing automation features that previously relied on Marketing Cloud Engagement (MCE). However, we face an immediate technical hurdle: this new version does not yet support 100% of legacy functionalities. Essential backend setups—such as sender configuration (including Sender Authentication Packages and IP provisioning)—as well as the core configuration of mobile delivery channels like SMS and WhatsApp, must still be managed within the traditional MCE infrastructure.
At first glance, this looks like a product gap—an unwelcome scenario where clients are forced to maintain hybrid architectures and duplicate their management efforts. But if we look at the history of Salesforce, this overlap between the old and the new is not a design flaw. It is actually a deliberate, strategic mechanism for a low-risk, gradual transition.
Pros and Cons of the Hybrid Approach
Adopting a dual-platform architecture involves tradeoffs that every leadership team must balance:
Pros
Immediate Innovation:
Controlled Obsolescence:
No "Big Bang" Risk:
Cons
Operational Overhead:
Learning Curve:
Transition Costs:
A Proven Pattern: Lessons from SCAPI, OCAPI, and Composable Storefront
This situation with MCN and MCE is a pattern we have seen before in the Salesforce ecosystem. In Commerce Cloud, we faced the exact same uncertainty when transitioning from legacy APIs (OCAPI) to the new Salesforce Commerce API (SCAPI), and again when moving from SFRA to Composable Storefront (PWA Kit).
Back then, the partial transition caused a lot of friction because the new features lacked parity with the old ones. However, forward-thinking brands turned that friction into a competitive advantage by using hybrid deployments. They kept critical processes like the checkout on the stable SFRA architecture while migrating the user experience (PLP, PDP, and Homepage) to PWA Kit. The result? They drastically improved their site performance (Web Vitals) and prepared their teams for headless commerce without stopping their business operations.
A Silver Lining for Every Decision
New Customers can jump straight into a mature, native ecosystem from day one, skipping the legacy headache entirely.
Conclusion
The coexistence of Marketing Cloud Next and Marketing Cloud Engagement should not be viewed as a technical limitation, but rather as a smart transition strategy. In enterprise architecture, progressive maturation is the safest way to unlock innovation without disrupting business continuity. Ultimately, every organization will find a solid reason to justify its past decisions or confidently back its future tech investments.
Spread the knowledge.
Author Details
