No, your existing integrations keep running during migration to New Exalate. Exalate Classic remains fully supported while you transition, ensuring continuous operation of your production workflows. This means you can shift when you're ready without worrying about disrupting critical business processes that depend on your current integrations.
Minimizing Risk with Parallel Operation
The migration process is designed to minimize risk by allowing you to:
- Access New Exalate and import your existing connections.
- Test the new experience while Classic continues operating.
No immediate switch is necessary, giving you the flexibility to evaluate features like the unified console, Aida AI, versioning, and Test Run capabilities before fully committing to the new platform. You control the timing and pace of your migration based on your team's readiness and business requirements.
Test New Exalate Without Disrupting Classic Integrations
This parallel operation approach means you can thoroughly test imported connections in New Exalate without affecting your live Classic integrations. The same Groovy scripting engine and autonomous control on each side remain consistent between platforms, ensuring your sync logic behaves predictably after migration. You maintain flexibility in data transformation and can verify that your complex workflows transfer correctly before switching production traffic.
Easy Transition at Renewal
At renewal, you'll choose a New Exalate plan and can complete the transition with confidence knowing your integrations have been tested and validated. The unified console provides better visibility into connection status, sync statistics, and error handling, helping you identify and resolve any migration issues before they impact operations. This ensures a smooth transition without the synchronization gaps or data inconsistencies that would result from system downtime.
Start a free trial to begin testing your migration to New Exalate while your Classic integrations continue running uninterrupted.