Start here — pick your source

You almost certainly already have something running your jobs. RunWisp is built to read that config rather than make you retype it — so pick where you’re coming from and skip straight to the one command that matters.

Whichever route you take, the shape is the same: your existing config keeps working, RunWisp takes over the running of it, and you get run history, captured output, and failure alerts on top.

Where are you coming from?

From cronOne command reads your crontabs in place and retires cron. Nothing rewritten, nothing fires twice, crontab -e still works.

From supervisordEvery [program] becomes a supervised RunWisp service — restart policy intact, logs now streamed and indexed.

From docker-composePoint RunWisp at an existing docker-compose.yml. Every service becomes observable without touching a line of YAML.

From nothing yetNo scheduler to migrate? Start with the quick start instead — install, scaffold a config, run your first task.

Which cron page do I want?

Cron gets three pages because there are genuinely two different routes, and they lead to different places:

• Take over — RunWisp runs your crontabs where they sit. You don’t own them as TOML, and crontab -e keeps working. This is the one-command path, and on Linux with systemd it’s the whole migration.
• Converting crontabs — turn a crontab into a runwisp.toml you own and edit. Use this when you want the jobs in version control, or when you’re on macOS or a box without systemd, where takeover can’t retire the system cron for you.
• How cron maps to TOML — the field-by-field reference behind both routes. Reach for it when you want to know exactly what a given crontab line becomes.

If you’re not sure, start with take-over. You can graduate any single job into your own TOML later without redoing the migration.

Before you switch anything

Two things worth knowing regardless of route:

• Nothing fires twice. RunWisp won’t run a job that the old scheduler is still running. Each guide covers how that’s enforced for its source.
• Config reload is explicit. RunWisp never watches files. After you edit runwisp.toml, run runwisp reload to pick it up.

---

Tasks vs ServicesWhich one your migrated job should be — the one-line rule.

Configuration overviewEvery key in runwisp.toml, once your config is your own.

TroubleshootingMigrated, but something isn't firing? Start here.

CLI referencetakeover, import, promote — every flag on the migration commands.