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, HYSYS or DWSIM model?
Drag an Aspen Plus .bkp/.apw, a HYSYS .hsc, a DWSIM .dwxml or a CAPE-OPEN .xml deck 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.
Frequently asked questions
Which file types can I import?
Aspen Plus .bkp and .apw, HYSYS .hsc, and DWSIM .dwxml / .dwxmz. Anything else is refused up front with the list of what is accepted, rather than half-parsed.
Is my file stored on your server?
No. The upload is parsed in memory and the request returns the extracted flowsheet — the file itself is never written to disk or kept. The flowsheet becomes saved data only if you choose to save it as a simulation.
Does an AI read my model?
No. Parsing is deterministic code, with no model call anywhere in the path — which is also why the same file always yields the same flowsheet. The result is then checked by the same validator every AI-generated flowsheet has to pass, so an invalid extraction comes back as errors instead of rendering on the canvas.
How complete is a HYSYS .hsc import?
Partial, and reported as partial. An .hsc is a binary compound file, so what comes out is the list of unit names and types — not stream connectivity or block parameters. Aspen's .bkp and .apw recover more. Either way the migration report tells you exactly what was and was not recovered; we would rather show you a short honest list than a flowsheet that looks complete and is not.
What happens to a block you do not recognize?
It becomes a labelled placeholder carrying its original legacy type, wired in position. Nothing is silently dropped — you fill in the ones that matter and delete the ones that do not, which is a very different job from discovering a missing block after a solve.
Do I need an account to try an import?
No. You can import and look at the result signed out. Saving it, running it repeatedly and sharing it need a free account.
Will the imported model give the same numbers as Aspen?
Not automatically, and any vendor who promises that is selling you something. Property methods, binary parameters and column conventions differ, so treat an import as a head start on rebuilding — then check it against a case you already know. Our thermodynamics are published with their measured deviation against cited experimental data so you can see where the two should and should not agree.