Inside JUMP: A Look at JAMS Scheduler's Free Migration Tool from Dry Run to Full Conversion
·
Darrell Walker, Managing Solution Engineer, JAMS Software
JUMP (JAMS Universal Migration Platform) is a free, standalone tool that reads your existing scheduler’s job definitions and converts them into JAMS Scheduler jobs. It works in two stages: a Dry Run that previews the conversion, and a Full Conversion that completes it inside a live JAMS Scheduler instance. If your team runs Tidal, Control-M, ActiveBatch, VisualCron, AppWorx, Cron, Windows Task Scheduler, or SQL Server Agent, this is built for exactly that kind of move. This post covers how each stage actually works, what a Dry Run report shows, and which schedulers convert with the least manual cleanup.
Rebuilding Jobs by Hand Slows Down Every Migration
Teams stay on an aging or unsupported scheduler less because it still works well and more because migrating means rebuilding every job by hand. That work carries real risk:
Manual rebuilds introduce errors into workflows that production depends on.
Job logic often lives inside the scheduler’s own configuration, not in separate documentation.
A migration that should take weeks can stretch into months once every job needs individual attention.
A cutover attempted without a clear scope tends to land during business hours, which turns a routine change into an incident.
JUMP removes the rebuild step. It reads the job definitions your current scheduler already has and converts them directly.
JUMP Converts a Scheduler in Two Stages
JUMP runs as a standalone desktop application against your current scheduling environment. Point it at your scheduler, and it converts job definitions into a format JAMS Scheduler can run.
Stage One: the Dry Run
A Dry Run previews your converted environment without connecting to JAMS Scheduler at all. JUMP scans your existing jobs and produces a report showing how each one will translate, and nothing in your live environment changes.
A completed Dry Run gives IT directors and operations managers a concrete report to work from instead of an estimate: how many jobs convert cleanly, and how much manual work remains before cutover. Because the Dry Run has no connection to your production scheduler, it carries no risk to jobs that are already running. Teams can generate and review the report on their own timeline, then decide when to move to Full Conversion.
Stage Two: Full Conversion
Once a team is ready, JUMP connects to a live JAMS Scheduler instance through the JAMS REST API and completes the conversion, turning the same job definitions previewed in the Dry Run into working jobs. The decision to commit happens after seeing the outcome, not before it.
What Converts on Its Own, and What Needs a Second Look
Conversion completeness depends on the source scheduler.
Converts automatically in most environments:
Windows Task Scheduler, importing tasks from a local or remote instance
Cron (crontab), importing jobs from crontab files or live Linux/Unix servers via SSH
SQL Server Agent, importing jobs directly via a connection string
Converts most of the way automatically, with manual review needed to finish the job:
Tidal Enterprise Scheduler, via a CSV export
BMC Control-M, via a Control-M XML export (DEFTABLE/FOLDER/JOB format)
ActiveBatch, via a Redwood ActiveBatch XML export (Plans, JobPlans, Jobs, schedules, and dependencies)
VisualCron, via a settings export (Jobs.xml, plus optional Connections and Credentials)
Broadcom AppWorx, via Applications Manager
JUMP also imports DAGs from Apache Airflow 2.x and 3.x through its REST API.
Job definitions with more elaborate dependency chains, calendars, or custom scripting, common in platforms like Control-M and ActiveBatch, benefit from a manual pass after conversion.
What Usually Needs a Manual Pass
These are the categories that most often need a person, regardless of which scheduler a job is coming from. None of it is a surprise; a Dry Run report flags each one by name before Full Conversion, so it shows up on the report, not for the first time in production.
Credentials and connections. No scheduler exports usable passwords. Credentials, database connections, FTP logins, and mail settings come across with the account identity intact and the password blank. Someone re-enters those before the first production run.
Calendars. Holiday, fiscal, and custom business calendars usually live outside the primary job export. The job says “run on WORKDAYS.” If there is no calendar export to automatically create them, the calendar behind that name gets rebuilt in JAMS Scheduler and re-pointed.
Event and condition-based triggers. Predecessor chains convert cleanly. File watchers, resource gates, and OR-style “run if any of these finished” conditions need a decision about intent.
Conditional branching. If/else paths, failure branches, and jumps between steps don’t translate directly. Anything that forks on a runtime result gets rebuilt rather than converted.
Runtime variables and vendor macros. %%ODATE, ${DateAdd()}, Jinja templates, and calculated variables are evaluated by the source scheduler’s own function library. The values convert. The expressions behind them generally don’t.
Job types without a direct equivalent. Not every source job type maps one to one, most often where a scheduler ships its own library of built-in point-and-click actions. Those arrive with the original definition preserved in the job’s description, then get built or scripted.
Notifications, SLAs, and documentation. Alert destinations, escalation rules, attached-file emails, deadline definitions, and runbook docs typically live in a separate subsystem from the jobs, so they come across partially or get flagged for manual setup.
This is exactly what our migration team is for. When a Dry Run flags something in one of these categories, that’s a scoped, known piece of work our team handles alongside you, not an unpleasant surprise you find on your own after cutover.
What Happens After Jobs Land in JAMS Scheduler
Converted jobs run in JAMS Scheduler alongside anything else already scheduled there. JAMS Scheduler supports execution methods including PowerShell, Python, SQL scripts, SQL stored procedures, SSIS, SSRS, batch scripts, console applications, z/OS, IBMi or AS/400, and Azure Data Factory pipelines. JAMS Scheduler also integrates with enterprise ERP and data systems like SAP, JDE, Banner, PeopleSoft, Informatica, and Oracle EBS, so teams often gain more execution options than their previous scheduler offered.
Migrated jobs tend to be the same kinds JAMS Scheduler already runs well: ETL and data transformation, FTP and SFTP transfers, scheduled reporting, and file or folder management. Teams moving from a scheduler with a narrower execution footprint typically don’t need to re-platform those jobs again to take advantage of the wider set of execution methods; the jobs land in JAMS Scheduler ready to run as is, with the option to expand later.
What We Hear From Teams Running These Migrations
Working with IT teams on scheduler migrations, the question we hear most from operations managers isn’t whether JUMP can convert a job. It’s whether the converted job will behave exactly like the old one once it’s live. That’s what the Dry Run report is built to answer before anyone touches production, and it’s usually the point where a migration stops being a leap of faith and starts being a scoped project with a known outcome.
Questions We Hear About JUMP
Is JUMP free to use?
Yes. JUMP is free, and the Dry Run carries no cost or commitment.
Does JUMP need a connection to JAMS Scheduler?
Only for Full Conversion. The Dry Run runs standalone.
How much of the conversion is automatic?
Windows Task Scheduler, Cron, and SQL Server Agent convert automatically in most environments. Tidal, Control-M, ActiveBatch, VisualCron, and AppWorx need manual review to finish.
Start With a Free Dry Run, and Our Migration Team Takes It From There
If you’re running jobs on Windows Task Scheduler, Cron, SQL Server Agent, Tidal, Control-M, ActiveBatch, VisualCron, or AppWorx, JUMP scans your environment and converts most of it into JAMS Scheduler automatically.
Run a free Dry Run of JUMP to preview your converted jobs. No setup and no commitment. From there, our migration team can walk through anything flagged for manual review and help scope the rest of the project with you.
Darrell Walker is a Managing Solution Engineer at JAMS Software, where he works directly with IT teams planning and executing scheduler migrations.
