Migrate from Cameo or Rhapsody: model and thread without the round-trip

Moving off Cameo, MagicDraw, or IBM Rhapsody is rarely “replace the modeler with nothing.” Specialist MBSE tools are excellent at deep modeling, simulation, and (in some cases) code generation. Teams migrate — or go hybrid — when the pain is round-trip drift: the model in one tool, requirements and tests in another, and an audit that asks you to prove they still match.

Decide what you are migrating

Goal	Pattern
Connected, audit-ready architecture	Import governed SysML into traceunified; keep specialist tools only if you still need deep simulation
Keep simulation / code gen depth	Hybrid: Cameo/Rhapsody for fidelity work; traceunified for the regulated thread
Full tool replacement	Only when native diagrams cover the diagrams you actually baseline for audit

Be explicit before you export. Many successful programs are hybrid on purpose.

What to export

1. XMI from Cameo, MagicDraw, Rhapsody, Enterprise Architect, or Papyrus for the packages you will govern going forward.
2. Diagram inventory — which diagram types you baseline today vs which are working sketches.
3. Satisfy / allocate / verify relationships you already maintain (even if they live as tagged values or separate matrices).
4. Requirement IDs used in the model so you can re-link after import instead of rebuilding the thread by hand.
5. Requirements themselves — if they still live in DOORS/Jama/Polarion beside the model, export ReqIF or CSV/Excel from that ALM in parallel.

Import into traceunified

Architecture and requirements take two complementary paths:

1. Model via XMI

In Import Center, choose Create New (or Update/Smart for re-import) and format XMI (OMG Standard). The Architecture Import wizard then walks Upload → Selection → Destination → Preview (optional Dry Run) → Import → Results. Type mappings resolve automatically against your model configuration and are validated on Preview. Start with one subsystem’s package; confirm element identity, stereotypes, and the diagram fidelity you care about before expanding. Step-by-step: XMI import. See Architecture for how native SysML sits on the thread.

2. Requirements via Import Center

Bring the specification side through the same requirements importer used for ALM migrations:

1. Upload ReqIF, CSV, Excel, or Word.
2. Map fields (and ReqIF Type Mapping when applicable).
3. Enable Import Traceability Links when relationships are in the file.
4. Preview, then commit.

Walkthrough: Import requirements and ReqIF & field mapping.

3. Connect the thread

After both sides are in, link architecture to requirements and tests in-product. Prove suspect-on-change: edit a block or requirement and confirm linked items flag for re-verification. Keep specialist MBSE for simulation if you need it — do not force every analysis into the ALM.

Cutover pattern

Common pattern: freeze the regulated architecture baseline in traceunified; keep Cameo/Rhapsody for simulation campaigns. Retire or shrink modeling seats only when auditors and SE agree the governed thread is complete. Confirm you can export again before you discard source models (Export).

Validation checklist

• Critical blocks / interfaces present with stable IDs
• Satisfy/verify (or equivalent) links to requirements and tests for a known path
• Baselining and review path exercised on a model change
• XMI and ReqIF/CSV exit paths understood
• Clear written rule: what lives in traceunified vs the specialist tool

When staying on Cameo / Rhapsody alone is right

If model fidelity, simulation, or code generation is the product — and requirements integration is already good enough for your assurance case — specialist MBSE remains the right center of gravity. Migration is for programs where drift and evidence cost more than modeling depth.

Related reading

• Cameo and Rhapsody alternatives
• traceunified vs Cameo & Rhapsody
• Cameo & Rhapsody alternative
• Architecture module
• Import requirements