Yes, your existing integrations continue working without interruption. Classic Exalate remains fully supported and operational, meaning all current synchronizations keep running exactly as they do today. No changes occur to your live integrations unless you actively choose to migrate them to the new experience.
No interruption to live integrations
The introduction of the New Exalate experience does not affect Classic deployments. Your sync scripts, connection configurations, triggers, and data flows maintain their current operation while you evaluate migration options at your own pace. Organizations can continue relying on production integrations for business-critical workflows without concern about disruption from the new platform release.
Import preserves configuration
When you decide to transition, importing connections from Classic to the new console preserves your sync configurations. The import process transfers your existing scripts and settings rather than requiring rebuilds from scratch, maintaining continuity of your integration logic. You control the timing and approach for each connection migration based on operational priorities and team readiness.
Support and updates for Classic
Support teams assist with both Classic and New Exalate during the transition period, ensuring you have resources available regardless of which version you're using. Security updates, bug fixes, and technical assistance continue for Classic installations while you plan and execute your migration strategy. This dual support model gives organizations confidence that business operations remain protected throughout the transition timeline.