Legacy Migration Engine
Import your Aspen Plus & HYSYS models
Sitting on years of flowsheets in Aspen or HYSYS? Drop the file — MaximaLabs migrates the unit ops and streams into a live, editable model, so switching is a review pass, not a rebuild.
Have an existing Aspen Plus or HYSYS model?
Drag an Aspen Plus .bkp/.apw or HYSYS .hsc file here — MaximaLabs migrates the unit ops and streams it recognizes into a live, editable flowsheet instead of you rebuilding it by hand.
Deterministic parsing (no AI). You'll review a migration report of exactly what was and wasn't recovered before running it.
How it works
- 1Drop an Aspen Plus .bkp/.apw or HYSYS .hsc file — no re-keying feeds, unit ops, or specs by hand.
- 2MaximaLabs parses it deterministically (no AI, no guessing) and maps the blocks and streams it recognizes onto native unit ops.
- 3Anything it can't confidently map becomes a labeled placeholder block instead of being silently dropped — you configure those before running.
- 4The result loads as a live, editable, solvable flowsheet on the canvas, and a migration report shows exactly what was and wasn't recovered.
Why this matters
An honest, scoped claim — not a magic-import promise.
- ✓Switching simulators normally means rebuilding every flowsheet from scratch — the single biggest reason engineers stay locked into a tool they've outgrown.
- ✓This turns that rebuild into a review pass: import the file, check the migration report, fix the placeholders.
- ✓Runs through the same server-side validation every AI-generated flowsheet goes through — nothing renders on the canvas until it's checked.
- ✓Honest scope: it recovers the topology and specs it recognizes, not a bit-perfect clone of a proprietary binary format — the report always tells you what came through.