Choose a Dassault Systèmes licensing partner on its role-mapping arithmetic, because that is the conversion every estate now faces: legacy CATIA and SOLIDWORKS seats run as concurrent licenses on the DSLS license server — shared pools where the binding number is peak simultaneous use — while the 3DEXPERIENCE platform licenses named users through roles tied to an individual identity. The migration between those two worlds converts shared capacity into per-person entitlements, and the ratio at which it happens is negotiable arithmetic, not a fixed conversion. The firm you want derives that ratio from your own license-server logs — and earns nothing from the vendor whose proposal it is testing.
Published 19 March 2026 · Last reviewed 19 March 2026
Dassault Systèmes spans CATIA, SOLIDWORKS, ENOVIA, SIMULIA and DELMIA, with the 3DEXPERIENCE platform as the declared destination for all of it. In licensing terms the portfolio splits cleanly in two. The legacy estate — above all CATIA in aerospace, automotive and industrial-equipment engineering — runs as concurrent network licenses served by DSLS, where a shared pool covers a larger population and the cost driver is peak simultaneous use. The platform estate licenses named users through roles — app-and-capability bundles such as 3D Creator assigned to a person’s 3DEXPERIENCE ID — with casual-access options for occasional users. SOLIDWORKS sits between the worlds: from November 2025 the offering consolidated around SOLIDWORKS Design Standard, Professional and Premium with cloud services powered by the platform included on new seats, while perpetual, subscription and network licenses persist throughout installed estates.
The engagement work follows from that split. Migration economics — what your measured concurrency is worth in named-user roles, which users genuinely need full roles and which are casual, what happens to perpetual entitlements and their maintenance in the move — dominate negotiation and renewal mandates, all of it standing on the right-sizing analysis that reads DSLS logs before the vendor’s proposal does. Compliance posture matters too, but differently than with the audit-led publishers: enforcement has historically been trigger-driven rather than telemetry-led, in part because concurrent estates report little usage back to the vendor — and the identity-based platform is closing exactly that gap as adoption grows, which is a structural reason to get the estate defensible now. The Dassault Systèmes vendor hub maps the products, metrics and firms; the timing logic in when to bring in help applies with the migration proposal as the clock.
General information for buyers, not legal or licensing advice; no firms are named here. The directory, filtered to Dassault Systèmes, lists the firms covering this vendor — alphabetical, balanced pros and cons, listed not ranked.
Dassault Systèmes licensing depth is concentrated in two places, and neither is neutral by default. The vendor’s own channel — value-added resellers and platform partners — carries the deepest catalog knowledge: roles, configurations, the deal desk, the migration tooling. Most license fulfilment runs through it, which is exactly why its advice needs the conflict question asked first; a leaner estate rarely serves a reseller’s pipeline. Independent licensing boutiques approach from the buyer’s side: those with concurrent-to-named-user conversion experience from other engineering publishers transfer well, because the underlying discipline — measure peak use, map real users to real tiers, argue the ratio — is the same arithmetic in different clothes. The Big Four appear where PLM rides inside a wider transformation program, with the alliance-disclosure question attached. Law firms enter if a compliance dispute formalizes, and engineering-focused SAM tooling reads DSLS concurrency well — it is platform-side usage and entitlement records where estates usually go dark.
Fee shapes follow the standard menu — fixed-scope baseline studies, day-rate advisory, renewal-cycle retainers, gain-share on negotiated outcomes — with the trade-offs unpacked in fee models explained; no prices are published on this site. Red flags, Dassault Systèmes edition: a role-mapping ratio accepted from the migration proposal without independent DSLS measurement; undisclosed vendor-linked revenue at the advising entity; a platform business case that never models staying put for another cycle; entitlement records left unreconciled before a negotiation; and any advisor who treats the migration date as the vendor’s to set rather than yours to negotiate.
DSLS log fluency. Concurrent estates are measured at the license server; a partner who cannot name the utilization metrics it would pull — peak draw by product and time, idle reservations, departmental patterns — intends to size your migration from headcount, which is how shared capacity gets repriced into shelf-ware.
Role-mapping arithmetic with a record. The concurrent-to-named-user ratio, and the tiering of full roles against casual access, are the consequential numbers in a platform negotiation. Ask for an engagement where the candidate’s measured ratio differed from the proposal’s assumption, and what that difference was worth.
Entitlement reconciliation. Installed SOLIDWORKS and CATIA estates accumulate decades of perpetual, subscription and network seats under shifting product names — the November 2025 renaming being only the latest layer. A defensible negotiating position starts from a clean record of what each seat is and under which terms it runs.
Migration judgment in both directions. The platform suits some estates now, others later, some not yet at all. The independence test, in one question: has the firm ever advised a client to defer the move — or to keep a concurrent estate — when the measurement said so? The fuller framework is in the independence test, and the same conversion logic in a neighboring estate is examined in choosing a Siemens licensing partner.
1. “Do you, or any affiliate, earn revenue from Dassault Systèmes — resale, referral or partner-program incentives — today?” In writing, before anything else is discussed.
2. “Walk us through a DSLS utilization study you have run. What did peak concurrency show against owned seats, and what did that change?”
3. “How do you derive a concurrent-to-role conversion ratio — and how do you tier occasional users against full-time designers?” The answer should name data sources, not adjectives.
4. “Have you ever advised a client to defer a 3DEXPERIENCE migration, or to negotiate staying on concurrent terms another cycle? On what evidence?”
5. “Our estate mixes perpetual SOLIDWORKS, concurrent CATIA and a platform pilot — how do you sequence the renewal so one layer’s repricing does not cascade into the rest?”
6. “Who exactly will work our engagement, and how many live Dassault Systèmes matters does that person carry?” Engineering-software licensing fluency is rarer than office-stack fluency; the broader vetting sequence in how to choose a software licensing consultant comes before any vendor-specific question.
Adjacent guides and the working pages for this vendor, plus the directory filtered to Dassault Systèmes.
The full vendor landscape on this site →
The firms doing migration-era renewal work →
DSLS measurement and role right-sizing →
The other half of the PLM estate →
Fixed, day-rate, gain-share — the trade-offs →
Every field guide on the site →
Historically its compliance activity has been trigger-driven — a tip, a dispute, purchase patterns visible through the reseller channel — rather than a telemetry-led program, partly because concurrent DSLS estates generate far less usage data back to the vendor than cloud licensing does. The 3DEXPERIENCE platform changes that arithmetic: it is identity-based and cloud-connected, so the vendor’s visibility into actual use grows as adoption grows. Buyers should treat the compliance posture as tightening structurally, not because of any announced campaign.
Legacy CATIA and related products are typically licensed as concurrent network seats served by the Dassault Systèmes License Server, where a pool of licenses is shared and the binding number is peak simultaneous use. The 3DEXPERIENCE platform instead licenses named users through roles — bundles of apps and capabilities assigned to an individual identity. Moving between the two converts shared capacity into per-person entitlements, and the ratio at which shared seats become named roles is the central commercial question of any migration.
From November 2025 Dassault Systèmes consolidated the naming around SOLIDWORKS Design Standard, Professional and Premium, with new seats including cloud services powered by the 3DEXPERIENCE platform, and the store framing license choices as device licenses or single-user licenses tied to a 3DEXPERIENCE ID. Perpetual, subscription and network options continue to coexist in installed estates, which makes the entitlement record — what each seat actually is, under which terms — the first thing worth auditing internally at renewal.
It is a disclosed trade-off, not an automatic disqualifier. The partner channel knows the role catalog, the configurations and the deal desk, and most license fulfilment runs through it; its economics, however, generally sit on the vendor side of the transaction, and a leaner estate rarely serves a reseller’s pipeline. Ask in writing whether the advising entity earns Dassault Systèmes-linked revenue — resale, referral or program incentives — and weigh the answer.
Six to twelve months before renewal as a baseline, and earlier the moment a 3DEXPERIENCE migration proposal, a role-mapping exercise or a contract consolidation lands on the table — the usage measurement that anchors those negotiations takes months. A verification request or a compliance assertion from the vendor or its channel also justifies immediate help, before any deployment data is shared.
Tell us which Dassault Systèmes situation you are in — a migration proposal, a CATIA renewal, a role-mapping exercise or a compliance assertion — and we will route your brief to firms that genuinely cover it, with each firm’s independence status stated on its profile. Free for buyers, no vendor ever sees your brief, no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.