Import Artisan roast profiles and machine settings into Rostoc.
Rostoc supports two practical Artisan migration paths: import an Artisan .alog roast file as a reference curve for a plan, and import an Artisan .aset machine settings file when setting up a Machine. These are separate workflows; machine compatibility still depends on the exact roaster model, controller, protocol, and validation test.
Updated June 15, 2026 | Rostoc
What Rostoc can import from Artisan
Artisan files can help a roastery move from a logger-centered workflow into a production record, but the file type matters. A roast profile file and a machine settings file solve different problems.
Use the import path that matches the job: reference curves belong with roast plans, while .aset machine settings belong with machine setup and compatibility review.
| Artisan file or workflow | Use it for | Rostoc result |
|---|---|---|
| Artisan .alog roast file | Bringing a selected roast curve into a plan as a reference. | The curve can become the plan reference so future Roast Batches can be compared against it. |
| Artisan .aset machine settings file | Understanding machine connection parameters such as protocol, registers, labels, and controller setup. | Rostoc reads the settings into a Machine setup flow, then the connection still needs review and testing. |
| Historical spreadsheets or production notes | Preserving green lots, production quantities, and operational context outside the roast curve. | Use Rostoc inventory, plans, and batch records rather than treating the roast file as the whole history. |
Import Artisan roast profiles as references
In Rostoc, the plan detail view includes an Import reference action with an Artisan option. This is useful when a roastery has a known-good Artisan roast and wants to use that curve as a reference for a future plan.
Start with representative roasts, not every file in the archive. A reference curve is most valuable when it is connected to the coffee, charge weight, machine setup, notes, and production intention for the next roast.
This workflow fits Rostoc's roast profile and plan tools, where the imported curve becomes part of a broader production plan instead of a loose file on disk.
Import .aset files for machine setup evidence
An Artisan .aset file can be useful when adding a Machine because it often carries protocol, register, channel label, and connection details that would otherwise need to be retyped from memory or manuals.
That does not mean every .aset file becomes a production-ready Rostoc connection automatically. Treat the import as a starting point, then confirm the exact model, support status, protocol, BT/ET readings, and event timing before relying on it.
If the machine is planned or coming soon in the machine compatibility guide, send the .aset file through the support flow so the setup can be evaluated safely.
Migration checklist before switching workflows
A clean Artisan migration is less about moving every old file and more about preserving the records the team will actually use during production.
- Choose the representative Artisan .alog files that should become reference curves.
- Collect the .aset file for each machine setup you want Rostoc to evaluate.
- Check the current machine support status before assuming live connection support.
- Compare BT and ET readings during a short test batch before using the setup in production.
- Move green lots, inventory quantities, notes, and production context into Rostoc records instead of burying them in filenames.
When Artisan still makes sense
Artisan remains a strong option for roasters who want a free, flexible, deeply configurable logger and are comfortable with technical setup, device configuration, and occasional debugging.
Rostoc is the better fit when the problem is broader than curve capture: the team wants roast profiles, green inventory, machines, plans, batches, notes, and production history in one workflow.
The practical path can be gradual. Keep Artisan where it is still useful, import the curves and settings that matter, and evaluate whether Rostoc should become the main production workspace over time.
FAQ
Can Rostoc import Artisan roast profiles?
Yes. Rostoc can import selected Artisan .alog roast files as reference curves for roast plans, so future batches can be compared against a known profile.
Can Rostoc import Artisan .aset machine settings?
Yes. Rostoc has a machine setup path for importing an Artisan .aset file so connection settings can be reviewed and turned into a Machine entry.
Does .aset import mean my roaster is supported?
No. An .aset file is useful setup evidence, but compatibility still depends on the exact model, controller, protocol, support status, and successful connection testing.
Should I import every historical Artisan roast?
Usually no. Start with representative reference curves and the files tied to active production. Large historical imports are most useful when the surrounding coffee, lot, machine, and notes are also preserved.
Can Rostoc replace Artisan?
Rostoc can replace Artisan for teams that want roast data connected to inventory, plans, batches, and production records. Artisan may still be the better fit for highly technical users who prefer configuring and debugging a flexible logger directly.