Download Sample Assessment Report
Learn about non-production environment licenses, entitlements, and resources.
Your account owner or admin will receive an in-app notification to migrate your sandbox to a new environment named sandbox_migrated.
During the migration, all integrations, integration apps (IAs), flows, exports, imports, connections, and other resources are automatically migrated to the new non-production environment.
Use the Assessment Report provided during the migration to review the resources requiring further action.
After migration, resources won’t be shared between environments. Whether a resource is migrated or recreated depends on the resource type and how it's shared between your Production and legacy Sandbox environments.
Legacy production and sandbox licenses
In legacy Production and Sandbox environments, changes in one environment affect both environments. The Production and Sandbox environments share the same underlying resources. Any resource you create, edit, or delete in one environment is immediately reflected in the other.
This includes connections, imports, exports, flows, scripts, and API tokens. Use caution when editing resources in either environment.
This behavior doesn't apply to accounts on the multi-environment license, where each environment maintains its own isolated resources.
Migrations from the legacy Production/Sandbox license to the new multi-environment license are underway. Your account has not migrated to the new multi-environment license if you can toggle between environments.
The Celigo platform will prompt your account's owner or administrator to migrate your original sandbox environment to a new environment called sandbox_migrated.
-
Click Get started in the banner at the top of the Celigo platform.
-
Download the Assessment Report to review the resources being migrated.
-
Click Start migration to begin.
Tip
You can safely close the Migration in progress window, since the migration will continue in the background.
-
After the migration is complete, click the Environment dropdown to switch to your new environment.
-
Review your environment resources to ensure that they were successfully migrated.
-
Update any external systems that use your resources.
-
Click → to review, rename, and enable the new environment.
Integrations, integration apps (IAs), flows, exports, imports, connections, and other resources are automatically migrated. The following resources require further action post-migration.
Important
You must update any external accounts that reference your resources. Guidelines for resources that require further action are available in the assessment report or in this article.
When API tokens are migrated:
-
Full scope tokens are recreated in your new environment, but the original token is still available in your Production environment.
-
Custom tokens with access to both Production and Sandbox are recreated in your new environment, including permissions to specific integrations and resources. The tokens in Production are updated to remove the references to non-production resources.
-
Custom tokens in Sandbox only are moved to your new non-production environment.
-
Custom tokens in Production only are not moved and do not require action.
See also Managing API tokens for more information.
When an iClient is:
-
Shared between production and sandbox – a new iClient is created in the non-production environment and added to the resources using it.
-
In a sandbox environment – the existing iClient is moved to the new non-production environment.
-
In a Production environment – no changes are made.
When an on-premise agent is:
-
Shared – a new OPA is created in the non-production environment.
-
In sandbox only – the OPA is moved to the new non-production account.
-
In production only – no changes are made.
See Integrate data through firewall with Windows on-premise agent for more information.
When stacks are shared between production and sandbox resources, Celigo will create a new stack in your non-production environment. See also Run operations on different servers in stacks or Set up a wrapper connection for more information.
Review the assessment report before you confirm migration. When you initiate migration, an assessment report is generated. Review it carefully — it lists resources (such as agents or stacks) that you'll need to reconfigure in your non-production environment after the move.
Plan your migration window thoughtfully. All flows are disabled during and after migration. If your Sandbox has flows running on a frequent schedule, plan the migration for a time when disruption has the least impact on your team's work. Migration typically completes within 10 minutes, though accounts with a large number of resources or errors may take longer.
Pause active work in Sandbox before migrating. Any active work in your Sandbox environment will be interrupted while migration is in progress. Coordinate with your team before you begin.
This section answers common questions about migrating your legacy Sandbox environment to a multi-environment setup. It covers eligibility and how your flows and integration apps are affected.
Q: Who is eligible for migration?
A: Customers on the Platform 2024 license type are eligible for migration. If you're on an Endpoint model, you'll need to upgrade to Platform 2024 before you can migrate.
Q: What entitlements will I have in my new non-production environment?
A: Your non-production environment includes the same entitlements you have in Production — no additional licenses are required. One exception: because non-production environments are fully independent from Production, you'll need to configure a new On-Premise Agent (OPA) for your non-production environment after migration if your account uses one.
Q: What happens to expired or disabled integration apps in my Sandbox?
A: Expired and disabled integration apps are migrated along with the rest of your Sandbox. They retain the same status in your new non-production environment.
Q: What happens to flows that are running when migration starts?
A: Before migration begins, the system checks for any in-progress flows. If any are found, you're notified and given the option to cancel the flow or wait for it to finish before proceeding.
Q: Are my flows automatically re-enabled after migration?
A: Flows are disabled after migration. As part of your post-migration setup, you can choose to enable all flows that were enabled before migration — or enable them individually, one at a time. Flow schedules are preserved and remain unchanged.
Q: If I use Enable all, will it enable every flow in my non-production environment?
A: No. Enable all only re-enables flows that were active in your legacy Sandbox before migration. Flows that were already disabled before migration remain disabled.
Q: Can I still use ILM after migration?
A: Yes. Integration Lifecycle Management (ILM) works the same way after migration. You can continue using ILM to sync changes between related integrations and revert changes to previous revisions.
Accounts with expired Sandboxes are not included. If your account previously had a Sandbox that is no longer active, there is no migration for that environment.
Accounts with certain IA configurations need assistance from Celigo. If your account has a complex IA setup — for example, accounts with CAM/VPM integration apps, or mismatched licenses between Production and Sandbox — please reach out to your Celigo account team to coordinate migration.