Yes, you can run both New Exalate and Classic simultaneously during your transition period. This parallel operation allows organizations to maintain existing production integrations in Classic while testing and configuring new connections in the unified console. Teams can evaluate the new experience, train users on updated features, and validate configurations without disrupting current operational integrations.
Why run both during transition?
Running both versions enables phased migration strategies where you move connections incrementally rather than all at once. Organizations can start with less critical integrations to build confidence with the new interface, Aida AI assistance, and Test Run functionality before transitioning to business-critical synchronizations. This approach reduces risk and allows teams to develop expertise gradually.
Importing connections from Exalate Classic
When you import existing connections from Exalate Classic into the new Exalate console, you can choose which integrations to migrate. Connections not yet imported continue operating normally in Classic with full support maintained for both experiences during the transition. Your subscription and licensing accommodate this dual operation period, ensuring no interruption to service.
What stays the same (scripting, concepts, support)
The same scripting logic and sync patterns work across both environments, so knowledge gained while using Classic applies directly to the new experience. Teams familiar with Groovy scripting, replica concepts, and helper functions can leverage that expertise immediately when working in the unified console. Support is available for both versions to assist with migration planning and any technical questions during the transition.