Ecosystem Routes and Collaborative Exchange

A route is more than a file extension. It is a directed exchange between a source environment and a destination environment, with a representation or transfer mechanism in the middle and a job the recipient must complete at the end.

What this category covers

Use these articles to assess whether a proposed route is specific enough to test:

• source and destination products, releases, configurations, and direction;
• direct readers and writers, neutral formats, references, mediated translation, and dependency packages;
• geometry, structure, editability, engineering meaning, visual data, and other information layers at risk; and
• the evidence and acceptance checks needed for the receiving task.

The category deliberately uses bounded route examples. A vendor support table can establish a documented capability boundary, but it does not by itself establish feature preservation, editability, visual equivalence, or fitness for a particular task.

Articles

The category includes nineteen route guides. Start with the dossier and mechanism-choice articles, then use the focused journey that matches the recipient’s task.

1. Route dossiers: how to make and read a defensible CAD exchange claim defines the fields and evidence needed for a route claim.
2. Direct translators are directional: planning native and third-party CAD handoffs explains how to interpret product matrices, reference modes, and conversion modes.
3. SOLIDWORKS to Creo through STEP AP242: a bounded mechanical handoff applies the dossier method to a neutral mechanical-CAD route without promising a product-pair result.
4. DWG collaboration across AutoCAD release boundaries covers release asymmetry, backward saves, dependencies, and recipient checks.
5. CAD to VRED to USD: a visualization-delivery route separates CAD import, scene export, USD composition, and receiver acceptance.
6. Reference, package, or neutral file? Choosing a collaboration route helps choose a mechanism based on authority, updates, dependencies, and downstream use.
7. BIM and Civil Exchange Routes: IFC, Data Exchanges, and LandXML compares building-model and civil-data exchange paths, settings, and receiver checks.
8. BCF Issues and Viewpoints: Sharing BIM Review Context explains how to exchange issue and viewpoint context alongside a separately managed IFC model.
9. AutoCAD Cloud and Markup Collaboration Routes compares drawing links, synced PDF markups, DWF review sets, and cloud-reference recovery.
10. Navisworks NWD, NWF, and NWC: Snapshot, Links, and Cache distinguishes coordination snapshots, linked projects, and caches.
11. Creo JT Delivery: Exact or Faceted, and Who Can View It covers representation, Creo profiles, and viewer eligibility.
12. Managed CAD Sharing: Project State, Access, Packages, and Sync checks whether a recipient can open the intended managed state and how that state updates.
13. Archicad Teamwork Migration: Choose the Path, Check Eligibility, and Plan Recovery compares documented migration paths, their version and BIMcloud prerequisites, collaboration-state losses, and recovery choices.
14. Live Model Review or Coauthoring? Check Edit and Save Authority separates shared views, proposals, edits, and owner-saved results.
15. Altium CoDesigner or IDX: Planning an ECAD–MCAD Coordination Route compares Workspace changes, IDX files, and static geometry for electronics/mechanical work.
16. Inventor to Revit: Deliver a Building Component with Controlled Simplification plans a selected mechanical representation for a building-model task.
17. Design Application to Twinmotion to Unreal: A Datasmith Route compares live synchronization and scene-file delivery for visualization.
18. CAD to Slicer Through 3MF: Model, Settings, or Project? checks geometry, project/settings scope, and the receiver’s slicer state.
19. Autodesk Fusion Hub Migration: Merge, Export, or Change Ownership? distinguishes whole-hub consolidation, file export, and hub ownership changes.

Start with the job, not the route

Before asking whether a route “works,” write the outcome:

source environment and release
→ mechanism and direction
→ destination environment and release
→ information that must survive
→ downstream operation
→ acceptance evidence

For example, “deliver a STEP file” is incomplete. “A SOLIDWORKS 2026 assembly is exported as STEP AP242 and imported into the receiving Creo release so the team can identify components and inspect the required graphical PMI” is a testable starting point. Whether it succeeds remains a route question.

Category boundary

This category covers meaningful source-to-destination relationships and collaboration choices. Format semantics, information-layer analysis, failure recovery, and long-term acceptance are covered in the related categories. This category does not enumerate every product and format permutation or turn a support entry into a universal compatibility promise.