Continuum is the next generation of OpCon: a cloud-native, AI-ready platform built from client feedback gathered over many years, and includes a new interface, replacing Enterprise Manager and Solution Manager with a single, modern user interface. Below are answers to the questions we hear most often. If you don't see your question here, reach out to your Continuous account team or post in the Community. (Replies are not allowed within this article, so please create a post in the OpCon Discussion area.)
Is on-prem being phased out? Will we be forced to move to the cloud?
No. There is no forced migration and no cutoff date for on-prem customers. OpCon on-prem (“OpCon Classic”) is fully supported through at least 2031, including ongoing maintenance, patches, bug fixes, and security updates.
Continuum is where all new research and development is focused going forward. Moving to this cloud-native, AI-ready platform benefits you today and prepares your automation for the future. But moving to Continuum is optional and happens on your timeline. Nothing about your on-prem environment changes unless and until you choose to move.
How much control do we keep? Is there a hybrid option, or is it all-or-nothing cloud?
Continuous hosts and manages the OpCon Continuum platform in the cloud, so the OpCon server no longer runs on your own systems. What stays in your control is your environment: your agents, the servers they run on, and your data. This works the same as OpCon Cloud: job execution, files, and data movement all happen locally, and your files and data are never stored in or routed through the cloud. (See question 8 for how Continuum connects to your environment.)
There is no hybrid option. Ask your Continuous account team about on-prem options if you are an enterprise customer.
Can I run both side by side until I get used to Continuum?
No, there is no way to run OpCon Classic and OpCon Continuum in parallel. Migrating to Continuum requires leaving OpCon Classic.
What’s changed in the Continuum interface?
Continuum is a single, modern, web-based interface replacing both Enterprise Manager and Solution Manager. Highlights include: one canvas to build, edit, and manage entire workflows without switching screens; global search across jobs, logs, and configurations; the ability to move between environments (dev and production) without separate logins; full version history with rollback; and zero-downtime upgrades.
Feedback from clients who've previewed Continuum through webinars and live demos has been strongly positive, particularly from long-time Enterprise Manager users who were hesitant about Solution Manager. Many describe the new workflow builder and global search as meaningful time savers for day-to-day job building and troubleshooting.
Do our existing jobs, schedules, APIs, agents, and notifications carry forward, or do they need to be rebuilt?
They carry forward. Existing jobs, agents, connectors, and integrations are backward compatible, and the migration team handles the underlying data conversion, this is not a rebuild from scratch. The full functionality available in the UI is also exposed through REST APIs.
As part of every migration, your configuration is loaded into a dedicated test environment where it's reviewed and validated before go-live. That review sometimes surfaces small adjustments specific to a given environment (custom integrations, notice/output routing, and similar edge cases), but it is a validation step, not a rebuild.
Does Enterprise Manager or Solution Manager go away, and how abruptly?
Continuum replaces both Enterprise Manager and Solution Manager with one unified interface, but that only happens as part of your own move to Continuum. There is no separate, abrupt cutoff of Enterprise Manager or Solution Manager outside of your migration.
If you remain on OpCon on-prem, Enterprise Manager and Solution Manager continue to be supported through at least 2031. Solution Manager reached feature parity with Enterprise Manager as of the recent releases, so nearly all new capability going forward is being built there first.
What does it mean when you say OpCon Classic will be supported for the next 5 years?
It means, through at least 2031, you can expect: 1) Maintenance and security releases for OpCon Classic. 2) Our support, services and MAS teams to answer calls and cases for customers using OpCon Classic.
- Is SM still being developed? OpCon Classic, including Solution Manager, continues to receive security updates, fixes, and refinements, with support through at least 2031. New capabilities and features are built in OpCon Continuum. Keep submitting ideas in the Community; we route each one to the product where it fits.
- Will EM be supported also for next 5 yrs? EM is part of OpCon Classic and so it will receive the same support and services above. Security and maintenance releases.
What does the conversion or transition process actually look like: phased, or a single cutover?
The typical pattern: our team reviews and migrates your existing configuration into a dedicated test environment, you validate it there, and then we schedule a cutover once you're comfortable. End to end, migrations typically run about six to eight weeks, with most of the heavy lifting on our side. Your team's time is mainly needed for network and connectivity setup and for validation testing.
Cloud customers are being moved to Continuum in cohorts, with outreach and scheduling communicated well in advance. On-prem customers move at their own pace, at any time within the support runway described above; there is no requirement to convert on a fixed schedule. You also don't need to wait for your current contract to end: you can move mid-contract, and the move to Continuum is made under a new contract. When you're ready, contact your Continuous account representative.
When will Continuum be generally available, and ready for production use?
Continuum is targeted for general availability in Q4 2026. An early adopter program is happening now ahead of general availability to give a subset of clients hands-on access first, and that feedback will be incorporated before the broader release. Customers can begin adopting Continuum in early Q1 2027.
How does Continuum reach our on-prem assets, and how do files actually flow through the cloud?
Continuum's scheduling and orchestration engine runs in the cloud, but the actual work, including all file movement, still happens on-prem, executed by your existing agents (or the newer universal agent) connected through a lightweight relay component installed in your environment.
Your files and data never move to or through the cloud. Only scheduling instructions and status or log information travel between your environment and Continuum, over a secure, outbound-only connection initiated from your environment.
What training will be available for Continuum, and when?
Continuous Learning (learning.continuous.com) is our training platform. It includes free self-paced courses (including a 6-hour OpCon 101), instructor-led sessions, role-based learning paths, and a certification track.
OpCon Classic to Continuum training: A dedicated course to help customers move from OpCon Classic to Continuum is now available on Continuous Learning. It’s an instructor-led class held about every three weeks, with sessions scheduled around our other training offerings. Check Continuous Learning for upcoming dates and to register.
Webinars: We also have conducted a series of webinars on specific Continuum capabilities, including the workflow builder, deployments and versioning, and troubleshooting. Recordings are posted to catch up on Continuum features and functionality in our past webinars.
What happens if we lose internet connectivity, or the cloud has an outage? How resilient is the platform?
If your connection to Continuum is briefly interrupted, anything already running continues to run to completion. New jobs pause until the connection is restored, then everything automatically syncs and picks back up, no work is lost. Multiple relays can be configured for automatic failover at the local level, covering scenarios like planned maintenance or a single machine going down.
On our side, Continuum runs across multiple, geographically distributed cloud availability zones and regions with built-in redundancy, and we maintain a documented disaster-recovery process for regional-level failover.
If your organization loses all internet connectivity entirely, that's a broader business-continuity event, not something any cloud-connected system can route around. We'd recommend factoring that scenario into business continuity planning alongside Continuum architecture.