IT & sysadmins
Hundreds of PST files, cutover weekends, and scripts that must behave the same on every host.
WholeClear CLI
Move mailboxes and archives from the Windows command line when volume, repeatability, or unattended runs matter more than clicking through a wizard. Windows-only—not Linux or macOS. Demo (25 items) or Full with CLI Automation.
Windows 10 / 11 x64 (same build can run on Server hosts) · Demo capped at 25 items · Scripting guide
The desktop GUI still fits one-off jobs. Use the CLI when you need volume, a Windows Server host, Task Scheduler, or the same run tomorrow morning.
Hundreds of PST files, cutover weekends, and scripts that must behave the same on every host.
Repeatable playbooks across clients—change the config, keep the command.
Controlled exports, naming rules, HTML/JSON reports, and a clear audit trail of what ran.
CI jobs, Task Scheduler, RMM hooks, PowerShell pipelines, exit codes you can branch on.
Same conversion engine as the GUI—without click fatigue on long runs.
Prefer numbers over flags? Open the interactive menu and walk through convert, batch, or IMAP download.
Built for unattended batch runs on Windows—low babysitting, clear exit codes, same engine as the desktop tools.
Point Task Scheduler or an RMM script at convert, batch, or migrate. No interactive desktop session required for headless runs.
Batch jobs keep checkpoints. Interrupt a cutover, then continue without starting from zero.
IMAP downloads, IMAP-to-IMAP, and Microsoft 365 via user Graph/IMAP credentials—next to classic file conversions. Not domain-admin impersonation or native Exchange.
Start with the numbered menu on an RDP/console session, then move the same job into a script. Both paths hit the same engine.
Call wholeclear from PowerShell, Python, CMD, or a scheduler. Parse -o json and exit codes—no separate SDK.
Full CLI unlocks with the CLI Automation edition ($1,499)—includes Enterprise desktop rights. May share licW.db with the GUI on the same PC.
Common mailbox and archive formats, plus the operations admins actually schedule.
*NSF / Notes routes need the 32-bit (x86) build and a working HCL/IBM Notes environment on Windows—not on Mac/Linux. No OLM, Office-doc, or image destinations.
Flag lists and samples live in the CLI documentation. This page covers platform fit, licensing, and how jobs behave in production.
Same binary as CMD. Loop files, or call batch once over a folder with --resume.
Get-ChildItem "D:\PSTs\*.pst" | ForEach-Object { wholeclear convert -s $_.FullName -t "E:\EML\$($_.BaseName)" --from pst --to eml if ($LASTEXITCODE -ne 0) { Write-Error "Failed: $($_.Name) ($LASTEXITCODE)" } }Three steps from installer to report—menu for learning, scripts for production.
Run the Windows Setup on a workstation or Server host, open the Start Menu shortcut, and confirm wholeclear version.
Type wholeclear for the guided menu, or call convert / batch / migrate from PowerShell, CMD, or Task Scheduler.
Collect output under your target folder and open WholeClear-Reports\latest-report.html for a readable summary.
Migration JSON should reference environment variables for passwords and tokens (for example $env:WC_IMAP_PASSWORD / WC_GRAPH_TOKEN) so credentials are not stored as plain text in the config file. See Migration JSON and Samples.
After every run, check $LASTEXITCODE (PowerShell) or %ERRORLEVEL% (CMD). Full detail: Errors & Exit Codes.
| Code | Meaning | Typical action |
|---|---|---|
0 | Success | Job finished cleanly. |
1 | General error | Inspect console / report; unexpected failure. |
2 | Invalid arguments | Fix flags or config path before retrying. |
3 | License / activation | Activate Full key or use Demo within the 25-item cap. |
4 | Source missing / empty | Check input path; nothing discovered to process. |
5 | Conversion failed | Hard job failure—read report before re-queue. |
6 | Partial success | Batch mixed results; some files OK—review failed count, then --resume. |
7 | Cancelled | Ctrl+C / cancel; resume later if checkpointed. |
Same Windows CLI binary: Demo evaluates with a 25-item cap; Full unlocks after CLI Automation activation ($1,499). Business/Enterprise GUI licenses do not include the CLI.
Evaluate on real data
$1,499 one-time · unlimited after activation
licW.db with the GUI on the same PCWholeClear CLI ships only with the CLI Automation edition of WholeClear Migrator ($1,499). Business and Enterprise cover the desktop GUI only.
Workloads admins actually schedule—overnight archives, cutovers, and multi-tenant packs.
Hundreds of PSTs to EML or PDF on a Server host with parallel batch workers and resume after a network blip.
Pre-stage IMAP→Microsoft 365 or IMAP→IMAP JSON, run during the window, resume if auth flakes.
One script, many tenants—swap config paths and env secrets, keep the same exit-code checks.
For a single small file and an operator who only wants a mouse, use the desktop GUI. Use the CLI when volume, Server hosts, or unattended runs matter.
Windows-only binary. Works on Server when you install the same Win-x64 build and drive it from scripts or Task Scheduler.
wholeclear from Task Scheduler or your own wrapper.wkhtmltopdf helper packaged with Full/Demo installers.licW.db must be valid on the machine that runs the job (typically under AppData).What you get on disk after Setup—installer, reports, activation, and docs.
Short answers. Deep flag references stay in the docs.
Yes—install the same Windows x64 build documented for Windows 10/11, then run convert / batch / migrate from Task Scheduler, PowerShell, or CMD. We do not certify every Server SKU separately. Not Linux/macOS, and not a built-in Windows Service.
Same conversion engine; different interface. The GUI suits interactive one-off work. The CLI suits batch, scripts, and unattended Windows hosts. Business/Enterprise buy the GUI only; CLI needs CLI Automation (or Demo).
Yes. Call wholeclear like any Windows process, use -o json for machine-readable results, and branch on exit codes 0–7. There is no separate Python SDK—your script is the wrapper. See the scripting guide.
Keep passwords and tokens in environment variables referenced from the JSON (for example IMAP password / Graph token env fields)—not as plain text inside the file on disk. Details: Migration JSON.
Use batch with a checkpoint database and --resume (or jobs resume). Already finished files can be skipped on the next run.
Yes. Interactive IMAP download is available from the menu; scripted migrations use JSON configs for IMAP brand presets and Graph/IMAP Microsoft 365 with user credentials or tokens—not domain-admin impersonation or native Exchange.
Order the CLI Automation edition ($1,499 one-time) on the Migrator order page. It unlocks WholeClear CLI 11.0 on Windows and includes Enterprise desktop rights. Business/Enterprise alone do not include the CLI.
The evaluation build processes up to 25 items per job so you can validate formats and workflow. CLI Automation removes that cap after activation.
Install on a Windows 10/11 lab host (or a Server host with the same x64 build), run a small batch or menu convert, then wire the same command into Task Scheduler for production.