Migration Guide
This guide covers what O.D.I.N. replaces, what it does not replace, what data you can bring over, and how to run O.D.I.N. alongside existing tools during the transition.
What O.D.I.N. Replaces
O.D.I.N. is a fleet management layer — it sits above your printers and slicers. The comparison below maps common OctoPrint and Repetier features to their O.D.I.N. equivalents.
OctoPrint Feature Mapping
| OctoPrint Feature | O.D.I.N. Equivalent | Notes |
|---|---|---|
| Printer dashboard | Dashboard — printer cards with live telemetry | All protocols: Bambu, Klipper, PrusaLink, Elegoo |
| File upload and print | Model Library + Job Scheduler | Upload .3mf or .gcode, schedule to any printer |
| Temperature graphs | Telemetry chart on printer detail panel | 90-day retention |
| Webcam streaming | Camera System (go2rtc WebRTC) | RTSP, MJPEG, USB; Camera Grid page |
| Plugin ecosystem | Native integrations | MQTT republish, Prometheus, webhooks, OIDC |
| Print history | Print Archive | Auto-captured with filament usage, thumbnails, notes |
| User access control | RBAC — admin/operator/viewer roles | 200+ endpoints enforced |
| API | REST API with Swagger UI at /api/docs | Bearer token + scoped tokens |
| Notifications | Alerts — browser push, email, Discord, Slack, ntfy, Telegram | Per-user preferences |
Repetier Server Feature Mapping
| Repetier Server Feature | O.D.I.N. Equivalent | Notes |
|---|---|---|
| Multi-printer dashboard | Dashboard + Printer cards | Up to unlimited printers (Pro/Enterprise license) |
| Print queue | Job Scheduler with queue management | Color-match scoring, drag-and-drop reorder |
| Filament tracking | Filament & Spool Inventory | QR labels, AMS integration, Spoolman sync |
| User management | Users & RBAC | Admin/operator/viewer roles with org scoping |
| Print archive | Print Archive | Thumbnails, filament used, duration, notes |
What O.D.I.N. Does Not Replace
| Tool | Why | Recommendation |
|---|---|---|
| Slicers (OrcaSlicer, Bambu Studio, PrusaSlicer) | O.D.I.N. does not slice files | Slice first, upload the .3mf or .gcode to O.D.I.N. |
| Klipper firmware | O.D.I.N. uses Moonraker/Klipper via REST — it does not manage firmware | Run Klipper + Moonraker as normal; add the Moonraker URL to O.D.I.N. |
| OctoPrint plugins | O.D.I.N. has no plugin API | If you need a specific OctoPrint plugin's function, check if O.D.I.N. has native support first |
| Bed slinger firmware | O.D.I.N. does not push firmware updates | Manage firmware through printer manufacturer tools |
Data You Can Import
Filament Spools
Enter your spool inventory manually under Inventory → Spools, or use the CSV import feature. Required fields: material, color, brand, starting weight.
If you use Spoolman, O.D.I.N. can link to your Spoolman instance via spoolman_spool_id on each spool record. See Filament & Spool Inventory for details.
Slicer Profiles
Upload your OrcaSlicer .json, PrusaSlicer .ini, or Klipper .cfg profile files to the Profiles library under Models → Profiles. Profiles support revision history and tagging.
3MF and GCode Files
Drag-and-drop your existing .3mf and .gcode files into the Model Library. O.D.I.N. will parse 3MF metadata automatically (print time, filament usage, thumbnail, object list).
Print History from OctoPrint
O.D.I.N. does not import historical OctoPrint print records. Going forward, O.D.I.N. auto-captures every print in the Print Archive when it completes (success, failure, or cancellation).
Step-by-Step Migration Path
Step 1: Install O.D.I.N.
Follow the Installation guide to deploy the Docker container. Complete the onboarding wizard (admin account, organization name, network settings).
Step 2: Add Your Printers
Add each printer in Settings → Printers → Add Printer. O.D.I.N. supports four protocols:
- Bambu MQTT — X1C, A1, P1S, H2D (serial + access code)
- Moonraker REST — any Klipper printer (Moonraker URL)
- PrusaLink REST — MK4/S, MK3.9, MINI+, XL, CORE One (host + API key)
- Elegoo SDCP — Centauri Carbon, Neptune 4, Saturn (IP address)
Step 3: Add Your Filament Inventory
Under Inventory → Spools, add your active spools. For each spool:
- Set material, color, brand, batch
- Set starting weight and current weight
- Set cost per gram (used in cost calculations)
Step 4: Upload Your Models
Drag your .3mf files into Models → Library. O.D.I.N. extracts metadata automatically.
Step 5: Create Users
Under Settings → Access, create accounts for each team member. Assign roles:
- Viewer — read-only, submit jobs (with approval if enabled)
- Operator — day-to-day production (create jobs, manage spools, process orders)
- Admin — full system control
Step 6: Run in Parallel (Optional)
You can run O.D.I.N. alongside OctoPrint during a trial period. Note the Bambu exclusivity warning below.
Coexistence Notes
Bambu printers connect to exactly one MQTT client at a time. If O.D.I.N.'s Bambu monitor is connected, Bambu Studio's cloud link may be disrupted (and vice versa). You cannot run O.D.I.N.'s Bambu monitor and Bambu Studio cloud simultaneously on the same printer.
Recommendation: Decide upfront whether you want O.D.I.N. or Bambu Studio cloud as the active monitor. For self-hosted print farms, O.D.I.N. is the intended primary monitor.
For Moonraker/Klipper printers, O.D.I.N. polls the Moonraker REST API. Multiple clients can poll Moonraker simultaneously, so running O.D.I.N. alongside Mainsail or Fluidd is fully supported.
For PrusaLink and Elegoo SDCP printers, O.D.I.N. polls via REST/WebSocket. Coexistence with PrusaSlicer Connect or other tools is generally safe.
See Also
- Installation — Docker setup and first run
- Adding Printers — connecting all four printer protocols
- Filament & Spool Inventory — spool management and QR labels