How do I export my product catalogue from Fusion Operations?

Open Inventory and use the Excel whole list button. That single export gives you the product catalogue with current stock in one file, which covers most of what a migration needs. If you use configurable products, choose Excel whole list with Parameters instead so the variant parameters come with it.

Can I get transaction history out of Fusion Operations?

Only in one-month slices. The Inventory Movements report has a mandatory Period filter that will not span more than a month, so you cannot reconstruct years of history from it. Take current balances from the inventory list instead, and use movements only around the cutover window.

Does Fusion Operations have an API?

Yes, a genuine documented REST API, which makes it one of the few systems where an ongoing sync is realistic rather than aspirational. An admin copies the API Key and Secret from their user profile, exchanges them for a token that expires after two hours, then reads the products, inventory, purchase-orders and sales-orders endpoints. Check the current API version before building anything lasting.

Home/Guides/Fusion Operations

Migration guide

How to export your data from Autodesk Fusion Operations

Fusion Operations — formerly Fusion Production, and before that Valk Production Manager — is Autodesk's cloud MES for small and mid-size manufacturers. It's the closest system we write about to what AegisSwift itself does, so the migration is less about translation and more about grain: getting the product/variant decision right the first time.

Disambiguate before anything else. "Fusion" is badly overloaded, and three of the collisions are Autodesk's own. Confirm you mean Fusion Operations — you sign in at fusionoperations.autodesk.com — and not Fusion 360 (CAD/CAM), Fusion 360 Manage (PLM), Oracle Fusion Cloud ERP, or a club-management product called Club Fusion. Asking for the sign-in URL settles it immediately.

1.Three routes

Route A — Inventory list to Excel (start here)

The fastest complete pull. Open Inventory and use the Excel (whole list) button — or Excel (whole list) Parameters if you use configurable products, so the variant parameters come too. This gives you the product catalogue with current stock in one file, which is most of a migration already.

Route B — Reports (for everything else)

Reports in the side menu; every report exports as Excel or PDF. The three worth pulling:

Cost Report — the source for cost.
Purchase Orders Report — suppliers and what they supply, filterable by product and product family. Your best route to the vendor list and to vendor / vendor_sku links.
Inventory Movements — transaction history, but see the one-month cap below.

Route C — REST API

Fusion Operations has a genuine documented API, which makes it the one system here where an ongoing sync is realistic rather than aspirational.

An admin edits their user profile and copies the API Key and Secret.
Exchange them for a token: POST /api/v1/authorization with Authorization: Basic base64(API_KEY:API_SECRET). Tokens expire after 2 hours — renew rather than caching one.
Then read GET /api/v1/products, /inventory, /purchase-orders, /sales-orders. Base URL https://fusionoperations.autodesk.com/.

The v1 endpoints above are documented but flagged deprecated — check the current reference on Autodesk Platform Services before building anything lasting. There's also a stock_updated webhook firing on receive, ship, consume and produce, which is the hook to use if this becomes a live integration.

2.Field mapping into AegisSwift

Fusion Operations' own Bulk Inventory Import template (Inventory → Inventory Movements → Import) is the most reliable statement of its internal field names — worth opening even though you're exporting, because it tells you what to look for.

Fusion Operations field	AegisSwift column	Notes
Product Code	`sku`	Required.
Product name / description	`name`, `description`
Unit of measurement	`uom`
Quantity (inventory list, current balance)	`quantity`	From Route A.
Cost (Cost Report, or Cost column on movements)	`cost`	From Route B.
Supplier on the Purchase Orders report	`vendor`, `vendor_sku`	From Route B.
Product family	item tags, or derive `item_type`
Product Parameters (configurable products)	Variant axis	See the grain gotcha.
Warehouse / Warehouse Location	AegisSwift locations	If launching multi-location.

3.Gotchas

Configurable products decide your grain — and this one isn't reversible

A product with parameters expands into variants. Decide whether the AegisSwift item is the base product or each variant, and export with Excel (whole list) Parameters accordingly. This is the expensive mistake on this page: it is not fixable by re-import, because the two shapes have different SKUs and different stock.

Inventory Movements is capped at one month per run

The Period filter is mandatory and won't span more than a month, so don't plan to reconstruct years of history. Current balances come from Route A; use movements only around the cutover window.

It's an MES, not an ERP

Products, stock, POs and SOs are strong. Customer and vendor master data is thinner than in NetSuite or SAP. Expect to enrich party records from your accounting system — often QuickBooks, in which case use our native QuickBooks integration for parties and Fusion Operations for items.

Lot and batch tracking carries across

If you rely on it, capture lot numbers during the export rather than discovering afterwards that traceability broke at the cutover. AegisSwift traces lots forward and backward, but only for lots it was told about.

Bulk imports cap at 1,001 lines and read only the first worksheet

That's an import limit rather than an export one, but it's a fair signal of the batch sizes the platform is comfortable with — chunk API pulls similarly.

4.What happens on our side

Items and parties as two spreadsheets, matched on sku and name. Because Fusion Operations is an MES, the item side arrives in good shape and the party side usually needs a second source — plan for that rather than treating a thin vendor list as a problem with the export.

5.Questions people ask

How do I export the catalogue?

Inventory → Excel (whole list). One file, catalogue plus current stock.

Can I get full transaction history?

No — one month per run. Take balances from the inventory list instead.

Is there an API?

Yes, a real one, with a stock_updated webhook. Check the current version first.

Written from Autodesk's documentation and our onboarding experience. Autodesk renames this product regularly and the API is versioning — if something here is out of date, tell us at hello@aegisswift.com.

Bring it into AegisSwift

Multi-level BOMs, work orders, lot traceability, and QuickBooks sync from $69/month. 14-day free trial, no credit card, and we'll walk the grain decision with you before you import.

Start a free trial