Can you export your scheduled jobs to another PC?

Yes. In Schedule by Zaweba, File > Export jobs writes all your jobs to a .zschedule.json file, and File > Import jobs reads that file back, on the same PC or on another one. Imported jobs get new ids, the links that make one job run after another are kept, and nothing already in Schedule is overwritten.

Exporting is one of those features you only notice the day you need it, usually a new computer or a rebuilt one. It is worth knowing it is there before then.

Why export at all

A set of scheduled jobs is more work than it looks. Each one carries a timetable you checked against its preview, a program or script with the right arguments and working folder, perhaps a trigger, some conditions, retries, a time limit, a chain to another job. Rebuilding that from memory is slow and easy to get slightly wrong.

An export keeps every one of those decisions in a single file. The file is JSON, a plain text format, so it can sit happily with your other backups, be copied to a USB stick or be kept in a shared folder.

How importing behaves

Three things are worth understanding about import.

Every imported job gets a new id. That means importing never replaces or overwrites a job you already have. Your existing jobs are left exactly as they were, and the imported ones are added alongside.

Run-after links are kept. If one job runs after another succeeds, fails or finishes, that link points at the right imported job afterwards, so chains arrive working.

Importing the same file twice gives you two copies. Since nothing is overwritten, a second import adds everything again, so import once and then check.

Setting the jobs up on a new PC

On the old PC, use File > Export jobs. On the new one, install Schedule, use File > Import jobs, and choose the file. Then look through the jobs, because the new PC may not be laid out the same way. A program installed in a different folder, a script on a different drive letter or a working folder that does not exist yet will all need correcting.

For script jobs, interpreters are found automatically on the new PC, including PowerShell 7 if it is on the path, cmd.exe, a real python.exe and PHP. Settings > Scripts can point at any path if yours are elsewhere. Use Run now on each important job and check the history before trusting the timetable.

What an export is not

It is a copy of your jobs, not of your run history. The history of past runs stays where it was recorded. If you want a record of past runs, look at it on the old PC before you retire it.

It is also separate from Windows Task Scheduler. Schedule's Windows tasks tab lists those tasks read-only in plain English and can copy simple ones into Schedule as new jobs. Once copied in, they are ordinary Schedule jobs and go into an export like any other.

A habit worth forming

Export after any significant change, such as adding a few jobs or reworking a chain, and keep the file with your backups. Because importing never overwrites, restoring from it is safe even on a PC that already has some jobs. Import the file, delete any jobs you do not want, and you are back where you were.

So yes, your jobs in Schedule by Zaweba are portable, and keeping a copy takes one menu command.