Teams running on a commercial RPA platform (UiPath, Automation Anywhere, Blue Prism) or a stalled OSS one (TagUI, Sakuli) and wanting to migrate to OculiX don’t have to figure it out from scratch. A migration engagement scopes the project, sets a deliverable, and ships it within a written timeline.
We don’t proselytize, but here’s what we’ve heard from teams that made the call:
Cost predictability
Per-bot and per-runtime fees can scale to six or seven figures annually at enterprise volume. OculiX has zero license fees forever (MIT). The TCO conversation becomes “infrastructure + people” instead of “infrastructure + people + license”.
No vendor lock-in
With commercial RPA, if your vendor raises prices, deprecates a feature, gets acquired, or simply collapses (cf. TagUI’s AI Singapore wind-down), your bots are stranded. MIT, source-available, self-hosted means you control the timeline of every change.
Cross-platform parity
OculiX runs identically on Windows, macOS, Linux from a single JAR per platform. UiPath Studio is Windows-only. AA / Blue Prism have similar constraints. Teams with mixed-OS infrastructure stop maintaining parallel workflows.
Real scriptability
OculiX scripts are real Python (Jython) or Java. Versionable in git, diffable, code-reviewable, testable with standard test frameworks. The “visual workflow editor” of commercial RPA is convenient at low volume, painful at high volume.
Pure visual layer
OculiX works on what’s on screen, not on selectors / DOM / accessibility hooks. Apps that change their internal structure but keep their visual layout don’t break OculiX. UI selectors-based RPA breaks every release.
No telemetry
OculiX doesn’t phone home. Nothing leaves your network. For regulated sectors (banking, defense, healthcare, government), this is often the deciding factor — not even an architectural review of the vendor’s cloud helps, since there’s no vendor cloud to review.
We get read access to your current scripts library. We catalog:
Output: a written audit report with categorization, complexity scoring per script, and a migration strategy proposal.
Based on the audit, we propose:
You decide what proceeds. Strategy is collaborative.
We migrate the pilot batch end-to-end:
Output: pilot scripts running in your environment, identical output to the original, plus a written “lessons learned” summary that informs the rest of the migration.
We migrate the remaining scripts in batches, validating each batch before proceeding. Your team is involved in:
Output: full library running on OculiX in production, original RPA platform still warm for rollback.
We run a structured handover:
Output: autonomous team running OculiX in production, complete documentation, time-boxed safety net.
✅ Translates well
⚠️ Requires rewriting
French insurance group
150 RPA scripts on UiPath, mix of customer onboarding and document processing. 8-week migration. Result: license cost went from €280k/year to €0, infrastructure roughly the same, total scripts post-cleanup dropped to 110 (40 were obsolete and no one had noticed).
APAC retail chain
40 TagUI scripts (after AI Singapore wind-down), needed a maintained alternative. 3-week migration since TagUI translates cleanly to OculiX (similar visual model). Result: same workflows, supported runtime, no licensing.
US healthcare provider
60 Automation Anywhere scripts in a Windows-only deployment, wanted to extend to a Linux back-office. 6-week migration to OculiX. Result: same scripts running on both OS, infrastructure consolidation, audit trail (MCP module) plugged in for HIPAA evidence.
German manufacturing
Mix of Blue Prism and custom Selenium for production-floor automation. 5-week migration of the Blue Prism subset to OculiX. Selenium kept for web-specific flows. Result: clean separation between visual automation (OculiX) and web (Selenium), each tool in its sweet spot.
The Phase 1 audit tells you in writing what works directly, what needs rewriting, what should be deprecated. We don’t promise “everything translates magically” — that’s marketing. We promise “every script has a documented destination state before we touch it”.
OculiX scripts run as plain Java processes. They integrate with any scheduler — cron, Windows Task Scheduler, GitHub Actions, Jenkins, Airflow, your existing RPA orchestrator (yes, you can run OculiX scripts FROM an orchestrator’s Run Shell step during a transition period).
OculiX scripts run headless via -r script.py mode in CI. We’ve integrated with Jenkins, GitHub Actions, GitLab CI, Azure Pipelines, TeamCity. Phase 5 handover includes wiring this up for your specific CI.
Phase 5 dedicated session (typically 1 day on-site or 2 half-days remote). Includes: running scripts manually, debugging when one fails, capturing new image anchors when a UI changes, monitoring production runs, escalation flow. Recorded sessions delivered as part of the runbook.
Fixed by scope, not by hour. The Phase 1 audit is the deliverable that lets us quote the rest with confidence. Audit-only engagements are also possible (1-2 week assessment with a written report and migration estimate) if you want to scope before committing to the full project.
Yes, and it’s the recommended approach for Phase 4. The original RPA platform stays warm, the converted scripts run in parallel, output is compared, you decide when to cut over per batch. We’ve supported shadow periods from 1 week to 3 months.
You own all the migrated code. The original RPA platform is untouched throughout. Rollback is abandoning the new scripts and keeping the old platform live. The work done remains yours, no contractual lock-in.
Not as a standard offering — those are web-testing tools with a different scope. OculiX complements them (visual automation alongside DOM testing) more than replaces them. Architecture conversations about combining them are part of the Architecture review engagement.
🦎
