Customer Insights – Journeys vs HubSpot

If you run Dynamics 365 Sales and need marketing automation, the shortlist almost always comes down to two names: Microsoft's own Customer Insights – Journeys, or HubSpot Marketing Hub connected to Dynamics through an integration. Both are serious products. The decision is not about which has more features — it is about where you want your marketing data to live, who will operate the tool, and how much integration you are willing to own.

This guide walks the difference the way it surfaces in real evaluations.

The architectural difference, which is the whole difference

Journeys runs inside your CRM. It is a Dataverse app: it reads and writes the same Account, Contact, and Lead tables as Sales. A segment can filter on any CRM column — opportunity stage, owner, custom tables, case history — with no sync, because there is nothing to sync. When marketing qualifies a lead, the sales team sees it on the record they already work.

HubSpot runs beside your CRM. It is its own platform with its own contact database, and it talks to Dynamics through a connector — HubSpot's native Dynamics integration, or middleware. The connector maps fields, syncs on a schedule or near-real time, and inevitably becomes a small system of its own: someone owns the field mappings, resolves sync conflicts, and answers "why does this contact exist twice?"

Everything else in the comparison is downstream of this one fact.

Where HubSpot wins

• Ease of use. This is HubSpot's brand for a reason. A marketer can build an email, a landing page, and a nurture flow on day one without training. Journeys has improved a lot since the outbound era, but it still feels like a Microsoft business app — capable, denser, more configuration before the first send.
• The content and inbound toolkit. Blogging, SEO recommendations, social publishing and listening, ad management, a built-in CMS, chatbots. Journeys has none of this — it is marketing automation, not a marketing platform. If your strategy is inbound content, HubSpot ships the whole toolchain.
• Time to value. A HubSpot instance sends its first campaign in days. Journeys typically lands inside a broader Dynamics programme, with consent model, deliverability setup, and Dataverse security to configure first.
• Reporting out of the box. HubSpot's funnel and attribution reporting is ready on day one. Journeys gives you analytics per journey and per email, but cross-programme reporting usually means Power BI work.
• Operating without IT. HubSpot is genuinely runnable by a marketing team alone. Journeys assumes somebody nearby understands Dataverse.

Where Journeys wins

• One database with Sales. No connector, no field mappings, no duplicate contacts, no sync lag between a lead scoring action and the seller seeing it. In regulated industries, also one security model and one audit surface instead of two.
• Segmentation depth. Because segments query Dataverse directly, you can target on anything your CRM knows — custom tables included. HubSpot can only segment on what the connector syncs, and every new attribute is a mapping change.
• Trigger-based journeys on CRM events. A journey can start the moment any Dataverse record changes — case closed, contract signed, custom business event fired. Reproducing that in HubSpot means pushing events through the connector or API first. The real-time model is built for exactly this.
• Events and webinars. Journeys has real event management with native Teams webinar integration — registration to attendance data flowing straight into journeys. HubSpot's marketing events object is thinner.
• Licensing at CRM scale. Journeys is priced on interacted people and includes attach pricing for existing Dynamics customers. HubSpot Marketing Hub Professional/Enterprise plus the contact-tier pricing plus the integration effort frequently costs more than teams expect once the database grows — though pricing changes on both sides, so model your own numbers rather than trusting anyone's blog post.
• The Microsoft roadmap. Copilot features, Dataverse, Power Automate, Customer Insights – Data for profile unification — betting on Journeys is betting on the stack you already bought.

Where the differences don't matter

Email builders, A/B testing, dynamic content, lead scoring, forms, basic nurture flows, consent management — both do all of it competently. No evaluation should turn on whether one of them "can send a newsletter." If a vendor demo spends its time here, it is avoiding the real question.

How the decision actually gets made

In practice this is rarely a feature bake-off. Three questions settle most evaluations:

Who operates it? A standalone marketing team with no Dynamics admin support will be happier on HubSpot, full stop. A team embedded in a Dynamics-centric organisation, with admins who live in Dataverse, gets more from Journeys than HubSpot could deliver through a connector.

How CRM-entangled is your marketing? If campaigns key off CRM state — pipeline stages, service events, custom-table data, B2B account motions — the shared database wins and Journeys is the right call. If marketing is mostly top-of-funnel content and capture, feeding leads over the wall, HubSpot's toolkit wins and the connector is good enough.

Is HubSpot already there? Many evaluations are really "should we migrate off HubSpot now that we're on Dynamics?" Usually not immediately: a working HubSpot instance plus the native connector is a fine state, and forced migrations burn goodwill. The switch case appears when connector maintenance grinds, contact-tier costs climb, or CRM-triggered automation demand outgrows what syncs.

One thing not to do: run both as peers long-term with marketing contacts split across them. Pick a system of record for marketing consent and engagement history, or reporting and compliance both turn to soup.

The bottom line

HubSpot is the better standalone marketing platform. Journeys is the better marketing layer for a Dynamics CRM. Decide which of those you are actually buying, and the product choice makes itself. If you land on Journeys, the marketing learning path takes you from orientation to running real campaigns.