Does an HSMWorks project transfer to a new CAM system?
Not as a one-click, production-ready project conversion. Autodesk support says the HSMWorks CAM data inside a SOLIDWORKS project cannot be imported directly into Fusion. For Autodesk's own path, native geometry, HSMLIB tool libraries, CPS posts, and renamed toolpath templates can be transferred separately. Moving to SOLIDWORKS CAM, CAMWorks, or another CAM system requires a controlled rebuild and validation.
Programmers and managers deciding what to archive, what to reuse, and what must be recreated before HSMWorks access ends.
A guarantee that an imported asset is safe to run. Posts, parameters, geometry selections, simulation, and output code still require qualified review.
The HSMWorks transfer matrix
| Asset | Autodesk Fusion path | Other CAM systems | Production action |
|---|---|---|---|
| SOLIDWORKS geometry | Transferable Autodesk documents upload of native SLDPRT and SLDASM files. AnyCAD can help update imported design changes. | Format-dependent Use the target vendor's supported native or neutral format. | Verify units, orientation, assemblies, stock, WCS, and later design-change behavior. |
| HSMWorks project CAM data | No direct import Autodesk support says the project CAM data is not included when the SOLIDWORKS file is imported. | No direct conversion | Recreate setups and operations in the target environment. |
| Tool libraries | Documented path Export from HSMWorks as HSMLIB and import into Fusion. | Usually rebuild or map | Check holder geometry, gauge length, feeds, speeds, materials, and duplicate tools. |
| Postprocessors | Reusable CPS source Autodesk says HSMWorks and Fusion use CPS postprocessors and documents importing customized posts. | Target-specific | Requalify every machine, controller, rotary mode, probe cycle, and special macro. |
| Toolpath templates | Transferable with changes Rename HSMWORKS-TEMPLATE to F3DHSM-TEMPLATE. Autodesk notes that parameters may differ and geometry may need reassignment. | Rebuild expected | Treat the imported template as a starting point, not validated output. |
| Setup sheets and NC files | Archive as evidence | Archive as evidence | Use proven output to compare intent, tooling, work offsets, notes, and machine behavior. Do not assume old NC proves the new post. |
| Machine and workholding knowledge | Recreate and verify | Recreate and verify | Document travel, rotary direction, limits, safe positions, fixture offsets, holders, probes, and automation interfaces. |
What Autodesk's Fusion path preserves
Autodesk's transition guide uses familiar HSMWorks concepts to reduce the learning and rebuild burden. It documents corresponding 2D, 3D, multi-axis, and turning strategies, similar setup terminology, native SOLIDWORKS geometry upload, HSMLIB tool-library import, CPS post reuse, and template conversion.
The important limitation appears in Autodesk's support article: importing the SOLIDWORKS file does not bring the HSMWorks CAM project data with it. “The same strategies exist” and “the project imports directly” are not the same claim. Plan to reconstruct and review the working setup, even when the destination is Fusion.
What changes when the destination is SOLIDWORKS CAM or CAMWorks?
The SOLIDWORKS-side route keeps CAD and CAM connected in the SOLIDWORKS environment, but it is not a file converter for Autodesk HSMWorks operations. The durable inputs are the part, the machining intent, the proven NC output, the tool and holder definitions, the fixture plan, and the machine-specific requirements. The operations and target-system data must be rebuilt.
Do not measure migration by files copied
Measure it by jobs reproduced safely. A useful milestone is not “the library imported.” It is “the representative job produced acceptable code, setup documentation, simulation, first article, and revision behavior.” Use the representative-part validation method to define that proof.
What to archive before the entitlement disappears
Source and project files
Native SOLIDWORKS parts and assemblies, HSMWorks project files, referenced models, fixtures, stock, and any external setup data.
Programming knowledge
Tool libraries, holders, feeds and speeds, templates, custom scripts, posts, post source, machine definitions, and documented special behavior.
Production evidence
Setup sheets, proven NC files, inspection results, first-article notes, screenshots of critical parameters, revision notes, and known operator adjustments.
Representative job set
Choose repeat jobs that cover normal work plus the hardest post, workholding, multi-axis, probing, turning, or automation requirements.
Frequently asked questions
Can I import an HSMWorks project directly into Autodesk Fusion?
No. Autodesk support says a SOLIDWORKS or HSMWorks CAM project cannot be imported directly into Fusion with its CAM data. The SOLIDWORKS geometry can be uploaded, and several reusable assets can be transferred separately, but the project itself is not a one-click CAM conversion.
What HSMWorks assets can transfer to Autodesk Fusion?
Autodesk documents a path for native SOLIDWORKS geometry, HSMLIB tool libraries, CPS postprocessors, and HSMWorks toolpath templates. Template filenames are renamed from HSMWORKS-TEMPLATE to F3DHSM-TEMPLATE. Autodesk notes that some parameters can differ and some geometry may need to be reassigned.
Do HSMWorks toolpaths transfer to SOLIDWORKS CAM or CAMWorks?
There is no direct HSMWorks-to-SOLIDWORKS CAM or CAMWorks project conversion. Preserve the source geometry and programming evidence, then rebuild the operations, tools, posts, and setup logic in the target system and validate the resulting code on representative work.
What should I back up before HSMWorks access ends?
Back up native CAD, HSMWorks project files, tool libraries, custom posts and source files, toolpath templates, machine and workholding data, setup sheets, proven NC files, screenshots of critical parameters, and a ranked set of repeat jobs. Keep the archive readable without relying on a future HSMWorks activation.
Primary sources
- Autodesk Support: Unable to import HSMWorks CAM data from SOLIDWORKS to Fusion, direct-project-import limitation.
- Autodesk: HSMWorks to Fusion transition guide, geometry, tool library, postprocessor, and template steps.
- Autodesk HSMWorks product FAQ, published retirement and access dates.
Build the migration around one representative job
Inventory the assets first, then prove the target post, tool data, setup, simulation, and output before repeating the process across the job library.