If your account uses the legacy Production and Sandbox setup, and you've been notified that your account is ready to migrate, you can migrate your Sandbox into a fully isolated environment. This critical upgrade ensures that development errors or configuration changes never accidentally impact your live production data, allowing your team to build and test with absolute freedom. This article walks you through the migration, explains how each resource type is handled, and answers common questions. During migration, your integrations, integration apps, flows, exports, imports, connections, and other resources move automatically to the new environment. After migrating, resources will no longer be shared between environments.
About legacy environments and the new muti-environment structure
In legacy Celigo setups, Production and Sandbox environments share the same underlying infrastructure, meaning any resource you create, edit, or delete—including API tokens, on-premise agents, stacks, and iClients—is immediately updated in both places. The new multi-environment structure completely decouples this architecture by ensuring that all resources exist exclusively within their designated environment. Isolating resources this way gives your team the freedom to build, test, and troubleshoot safely in development, with the peace of mind that critical failures or configuration changes will never impact your live production data. Learn more about multiple environments.
How do I know if my account has migrated to the multi-environment structure?
If you see the following Production and Sandbox option in integrator.io, your account has not yet migrated to the multi-environment structure.
The Celigo platform prompts the account owner or admin to migrate the original Sandbox to a new environment called sandbox_migrated. Whether a given resource is migrated or needs to be recreated depends on the resource type and how it was shared between your Production and legacy Sandbox environments. You can use the Assessment Report generated during migration to review the resources that need further action.
- Plan your migration window. All flows are disabled during and after migration. If your Sandbox has flows on a frequent schedule, choose a time when disruption is lowest for your team. Migration typically completes within 10 minutes, though accounts with many resources or errors may take longer.
- Pause active work in Sandbox before migrating. Any active work in your Sandbox is interrupted while migration is in progress. Coordinate with your team before you begin.
- Select Get started in the banner at the top of the Celigo platform.
- Download the Assessment Report to review the resources being migrated. Review this carefully — it lists resources, such as agents or stacks, that you'll need to reconfigure in your new environment after the move.
Download a sample assessment report
-
Select Start migration to begin.
Tip
You can safely close the Migration in progress window, the migration continues in the background.
- After migration completes, use the options at the top of the page to switch to your new sandbox_migrated environment.
- Review your environment's resources to confirm they migrated successfully.
- Update any external systems that reference your resources.
- Go to Account
, and then select Environments to review, rename, and enable the new environment. See Create and manage multiple environments.
How resources are handled
Integrations, integration apps, flows, exports, imports, connections, and other resources migrate automatically. You'll want to update any external accounts that reference your resources. The Assessment Report generated during migration lists the resources that need further action, along with guidance.
API tokens
- Full scope tokens are recreated in your new environment; the original token remains 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 Production tokens are updated to remove old, shared references to resources.
- Custom tokens in Sandbox only are moved to your new environment.
- Custom tokens in Production only aren't moved and need no action.
See Managing API tokens for more information.
iClients
- Shared between Production and Sandbox — A new iClient is created in the new environment and added to the resources using it.
- In a Sandbox environment — The existing iClient is moved to the new environment.
- In a Production environment — No changes are made.
On-premise agents
- Shared — A new on-premise agent is created in the new environment.
- In Sandbox only — The agent is moved to the new environment.
- 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 creates a new stack in your new environment. See Run operations on different servers in stacks or Set up a wrapper connection for more information.
This section answers common questions about migrating your legacy Sandbox to a multi-environment structure.
Q: Who is eligible for migration?
A: Customers on the Platform 2024 license type are eligible. If you're on an Endpoint license, upgrade to Platform 2024 before you migrate (see Manage your Celigo subscription).
Q: What entitlements will I have in my new environment?
A: Your new environment includes the same entitlements as Production — no additional licenses are required. One exception: because new environments are fully independent from Production, you'll need to configure a new on-premise agent for your new 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 and keep the same status in your new environment.
Q: What happens to partially installed templates or integration apps during migration?
A: Partially installed integrations and integration apps keep their current status and progress in your new environment. No work is lost.
- Accounts with expired Sandboxes aren't included. If your account previously had a Sandbox that's no longer active, there's no migration for that environment.
- Accounts with certain integration app configurations need assistance from Celigo. If your account has a complex setup — for example, CAM/VPM integration apps, or mismatched licenses between Production and Sandbox — contact your Celigo account team to coordinate migration.