You’ve invested time and effort in your SysML v1 models: system structures, requirements, and decisions are already documented. Which of these will you still need when your organization introduces SysML v2? Before transforming any models, decide which can be archived, which should stay in v1, and which should move to v2.
Back in May 2025, our article “SysML 1.x or SysML v2 Already?” explored when it makes sense to switch. SysML v2 has since been officially released. But one of our assessments from that article still holds: SysML v1 will be with us for several more years. That makes deciding what to do with existing models all the more important. Just because a transformation is technically possible doesn’t mean it makes sense.
Understand Your Starting Point Before Making a Plan
One question is crucial to your plan: does your organization still work primarily with documents, or does it already use MBSE with SysML v1? In the first case, the main task is to introduce model-based systems engineering. Existing documents, tools, and ways of working need to be taken into account. In the second case, you also need to decide how to handle existing v1 models. Your roadmap should reflect these different starting points.
Three Baskets: Archive, Keep, Transform
The practical core of this approach is to sort your existing models into three groups. What matters is how you’ll need to use them in the future.
Archive: Models that will no longer be modified but need to be retained, for example, for traceability. Determine which versions you need and how to keep them accessible and readable.
Keep: Models that remain in use and serve their purpose in SysML v1. Plan for their maintenance and the tool environment they require. If v2 models need to access content from these models, check what your tools and interfaces support.
Transform: Models whose content you need for further development in SysML v2. Determine which content should be transferred and how you’ll assess whether the result correctly represents the intended system.
Archiving models and keeping them in use also take effort. The size of the third basket depends on your existing models and development plans. The benefit of this exercise is a well-founded selection: you can plan the effort required for the models that actually need to move to v2.
It’s About More Than the Language
Migration involves more than transforming models. You also need to assess which modeling methods must be adapted and which tools need to be updated, acquired, or integrated. Each of these tasks has its own lead time.
Also plan how your team will learn to work with SysML v2. Team members need to be able to understand, review, and continue developing the transformed models. You may also need to address method-specific extensions, such as a profile used for SYSMOD. These need a plan, too.
The Current State of the Transformation Specification
OMG provides a specification of more than 600 pages for mapping v1 to v2, along with a pilot implementation. The specification primarily defines rules for developing automated transformations. It also helps you compare concepts in v1 and v2. It is not, however, a guide to your specific migration project.
For planning purposes, distinguish between the rules defined in the specification and their implementation in a particular tool. The specification does not include a mapping for some v1 elements. This does not automatically mean that the corresponding concept cannot be modeled in v2. A user-friendly mapping guide is being developed. If you’d like to contribute, you can join the Transformation Working Group of the OMG Systems Modeling Community.
What About the Diagrams?
Determine early on which diagrams your team will still need for reviews and documentation. Assess two things separately: whether the model content will be transferred and what will happen to its existing presentation, including positions, fonts, and colors.
Don’t assume that carefully designed v1 diagrams will automatically appear in v2 with pixel-perfect fidelity. View Definitions offer an approach for describing the views you need of a model. You’ll need to check with each tool how those views are rendered and which existing layouts can be carried over.
What Can Be Mapped Technically?
Common constructs have counterparts in v2. The following examples provide an initial orientation; the specific mapping depends on the v1 element involved.
Structures map to PartDefinition and PartUsage, linked through Feature Membership. Ports become PortDefinition and PortUsage. Activities are represented by ActionDefinition and ActionUsage, along with Succession, Flow Connection, start and terminate actions, and parameters.
Requirements become RequirementUsage. With Subject and Constraint, SysML v2 offers additional ways to describe requirements more precisely. These capabilities do not, however, automatically make a transferred requirement more precise in its meaning.
What This Means for Your Roadmap
Not all v1 models need to be transformed. For the models you select, look beyond the transfer itself and consider which SysML v2 capabilities you want to use in the future. A one-to-one translation alone won’t answer that question.
Start by taking inventory: who is responsible for each model? What will it still be needed for? Which other models or tools depend on it? Then work with your team to assign the models to the three baskets. This gives you a basis for planning the effort, sequence, and review needs of your migration.