Dynamics 365 Real-Time vs Outbound Marketing: 2026 Migration Framework

The Clock Is Ticking: Why IT Leaders Can No Longer Defer This Decision

Microsoft has made its intentions unmistakably clear: Outbound Marketing in Dynamics 365 is being deprecated, and Real-Time Marketing (now officially branded as the marketing engine within Dynamics 365 Customer Insights – Journeys) is the only path forward. For IT leaders who have spent years building sophisticated outbound journeys, complex lead-scoring models, and tightly integrated event management workflows, this is not a routine software update — it is a platform-level architectural shift that demands a structured migration decision.

The challenge is that most vendor communications frame this as a simple "upgrade." The reality, as any Dynamics 365 architect who has worked through the data model differences will confirm, is considerably more nuanced. Segments behave differently. Profiles replace contacts as the primary entity. Licensing tiers have shifted. And running both engines in parallel — while tempting as a safety net — introduces its own operational and compliance risks.

At CRMONCE, we have guided multiple mid-market and enterprise clients through this transition. This post consolidates that field experience into a practical decision framework: a feature parity scorecard, a migration risk assessment, a licensing cost analysis, and a 10-question go/no-go checklist designed specifically for IT leaders and CTOs who need to act in 2025–2026.

Feature Parity Scorecard: What Real-Time Marketing Can (and Cannot) Do Today

Before committing to a cutover date, your team needs an honest, capability-by-capability comparison. The table below reflects the state of both engines as of mid-2025, with Microsoft's publicly stated roadmap factored in where relevant.

Key takeaway: The highest-risk areas are event management portals, consent data migration, and segment rebuilding. Teams that have invested heavily in custom Dynamics 365 Portals for event registration should plan for the longest runway — budget at least 8–12 weeks for that workstream alone.

Migration Risk Assessment: What Actually Breaks on Day One

The Contact vs. Profile Data Model Shift

This is the single most misunderstood aspect of the migration. Outbound Marketing is fundamentally Contact-centric — every journey, every segment, every interaction record hangs off the Contact entity in Dataverse. Real-Time Marketing introduces the concept of Customer Profiles (unified through Customer Insights – Data), which can represent Contacts, Leads, or custom entities.

In practice, this means:

• Segments built on Contact attributes must be re-mapped to Profile attributes, even if the underlying data is the same Contact record.
• Any Power Automate flows that trigger on MarketingEmailClicked or JourneyCompleted events reference different Dataverse tables in Real-Time Marketing.
• Custom entities used as journey participants in Outbound (a common B2B scenario using Account-based triggers) require explicit configuration in Real-Time Marketing's audience settings.
• Interaction history (email opens, clicks, form submissions) does not automatically migrate — your analytics baseline resets on cutover day unless you export and archive historical data proactively.

Running Both Engines in Parallel: The Double-Edged Safety Net

Microsoft does allow both Outbound and Real-Time Marketing to run simultaneously within the same org during the transition period. Many clients treat this as a risk-free option, but there are hidden costs:

• Consent conflicts: If a contact opts out via a Real-Time Marketing form, that opt-out may not immediately propagate to Outbound Marketing consent records, creating compliance exposure under GDPR or CASL.
• Duplicate journey firing: Contacts enrolled in legacy Outbound journeys can inadvertently qualify for Real-Time journeys targeting the same audience, resulting in over-communication and unsubscribe spikes.
• Reporting fragmentation: Your marketing team will be managing two sets of dashboards, two engagement models, and two suppression lists — operational overhead that compounds weekly.

Our recommendation: treat parallel operation as a maximum 90-day bridge, not an indefinite state. Establish a hard cutover date and work backwards from it.

Licensing Cost Impact Analysis for 2026

The commercial dimension of this migration is often underestimated in technical planning sessions. Here is what CTOs and finance stakeholders need to understand about the 2026 licensing landscape:

The New Licensing Model at a Glance

• Dynamics 365 Customer Insights – Journeys (formerly Marketing) is now sold on an interaction-based model. The base license includes 10,000 monthly interactions, with additional packs available. This replaces the previous contact-count model that many organizations were accustomed to.
• Customer Insights – Data (the CDP layer that powers Real-Time Marketing's unified profiles) is licensed separately, starting at approximately $1,500/month for up to 100,000 profiles. Organizations that did not previously require a CDP will see this as a net-new cost line.
• Organizations on legacy Dynamics 365 Marketing agreements grandfathered before October 2023 may retain contact-based pricing temporarily, but Microsoft has signaled these will not be renewed on existing terms.

Budget Planning Guidance for CTOs

• Audit your current interaction volumes before negotiating your 2026 renewal. Pull 12 months of email send, SMS, push, and form submission data to project your interaction pack requirements accurately.
• If your organization sends fewer than 100,000 interactions per month, the new model is likely cost-neutral or marginally cheaper than legacy per-contact pricing.
• High-volume senders (500K+ interactions/month) should engage their Microsoft account team for enterprise agreement pricing — interaction pack unit economics improve significantly at scale.
• Factor in professional services costs for the migration itself. Based on CRMONCE project data, a mid-market organization with 15–20 active outbound journeys, two event management modules, and custom Power Automate integrations should budget 200–350 hours of consulting and configuration effort.

The Go/No-Go Checklist: 10 Questions Every IT Leader Must Answer

Before you deprecate a single Outbound Marketing journey, walk your team through these 10 technical readiness questions. A "No" or "Unsure" on any item should trigger a scoped workstream before cutover is approved.

1. Have you inventoried all active Outbound journeys, including recurring batch journeys that may not be visibly running? Shadow journeys in draft or stopped states with active contacts are a common source of cutover surprises.
2. Is your consent data model documented and validated? Can you confirm that every subscription list and topic mapping in Outbound has a corresponding purpose-based consent configuration in Real-Time Marketing?
3. Have all custom Dataverse entities used as journey participants been registered as custom audience entities in Real-Time Marketing?
4. Have you exported and archived historical interaction data (email opens, clicks, journey progression records) that will not be visible in Real-Time Marketing post-migration?
5. Are all custom Power Automate flows that reference Outbound Marketing triggers (e.g., msdynmkt_* tables) updated or replaced?
6. Has your event management portal been assessed for Real-Time Marketing compatibility? Custom Power Pages or legacy Portals built on Outbound event entities require re-platforming.
7. Has your team completed Microsoft's Real-Time Marketing training, and do you have at least one certified practitioner who has built and tested a complete journey end-to-end in the new engine?
8. Have you validated lead scoring model parity? Re-create your top three lead scoring models in Real-Time Marketing and run parallel scoring against a sample segment for 30 days before cutover.
9. Is your 2026 licensing agreement aligned to the interaction-based model? Do not cutover on a contact-based license that is mid-term — coordinate timing with your renewal date.
10. Do you have a tested rollback plan? In the event of a critical issue post-cutover, can you re-activate key Outbound journeys within 24 hours without data corruption to consent records?

Conclusion: This Is a Strategic Decision, Not a Technical Checkbox

The deprecation of Dynamics 365 Outbound Marketing is, at its core, Microsoft's bet that the future of B2B and B2C engagement is real-time, AI-assisted, and omnichannel. The Real-Time Marketing engine is genuinely more powerful for organizations willing to invest in the migration properly. But "properly" is the operative word.

IT leaders who treat this as a routine upgrade and set an aggressive cutover date without the scorecard, risk assessment, and readiness checklist in place will face the same issues we have seen repeatedly: consent compliance gaps, broken event portals, fragmented reporting, and marketing teams that lose confidence in the platform at exactly the moment leadership needs them to accelerate pipeline.

The organizations that will win in 2026 are those that start the assessment now, run a disciplined parallel period, and arrive at cutover with every item on that checklist resolved. If your team needs a structured starting point, CRMONCE's Dynamics 365 Marketing Migration Assessment is designed to get you from inventory to go-live plan in four weeks.

Ready to start your migration readiness assessment? Contact the CRMONCE team to schedule a no-obligation discovery call with a Dynamics 365 Customer Insights specialist.

Sources & Further Reading: Microsoft Learn — Dynamics 365 Customer Insights Journeys Overview | Microsoft Transition Guide: Outbound to Real-Time Marketing