Build

Migrate

Sirius includes a native migration tool. Point it at the workloads you already run on another engine. In seconds it produces Sirius integrations — idiomatic sirius.* mappings, not a compatibility shell that still thinks in the old vocabulary.

What you do

1. Open Migrate in the console (or call the migration API).
2. Paste or import a script from the engine you use today.
3. Review the native output and the report.
4. Bind connectors, run it against your samples, then cut over.

You can also drive the same flow from CI or an agent. The console is one client.

What the report tells you

Every recognized call site is classified:

• Native — mapped to a sirius.* helper. Migrated automatically.
• Connector — I/O rewritten to Sirius HTTP, database, file, or network calls. You still bind a connector and an allowlist.
• Needs a look — no safe equivalent (arbitrary host interop, a debugger hook, something the analyzer does not recognize). Those lines stay unchanged and are highlighted so nothing is silently invented.

A clean script gets a clean translation. A messy one gets a precise list of what a human should touch.

Why “native”

The goal is not to emulate another product forever. The goal is to keep your logic and express it in Sirius — one API, every language, ready for Studio autocomplete and the rest of the platform.

Task-oriented steps: Migrate a script. The shorter product story is on Migrate.