You can install a Marketplace integration app in any environment in your account — Production or non-production — using a single license. This article covers how integration app licensing works across environments, how to access and install into a non-production or original Sandbox environment, and best practices for testing an integration app safely before it goes live in Production.
Prerequisites: Access to the environment you want to install into, and a purchased integration app license.
Integration app licensing across environments
You don't need a separate integration app license for each environment or installation. Purchase one integration app license, and you can install it in any or all of your environments. You're charged based on the number of enabled integration app flows across your account, not the number of installations or environments.
If your account hasn't migrated to the multi-environment structure yet, you're on the legacy Production and Sandbox model, where the two environments share underlying resources instead of keeping them isolated. See Multiple environments overview for how that affects integration apps, and Migrate to a multi-environment structure to move your Sandbox to a fully isolated environment.
Switch between environments
To move between environments, select the environment from the list at the top of the page. Account owners see a list of all their environments; shared users see the accounts and environments they've been invited to (see Invite users and manage access to an account or environment). Switching environments loads that environment's resources.
Install an integration app in a specific environment
- Select an environment to install the integration app.
- Go to Marketplace.
- Browse to the integration app you want to install and follow the steps to install the app.
Best practices for testing in non-production environments
Test an integration app in a non-production environment and validate its configuration before you install it in Production.
- Connect your Sandbox integration app to the corresponding sandbox or test instances of the apps it integrates with — for example, NetSuite, Salesforce, or Shopify.
- Test flows and field mappings in Sandbox, and validate the configuration between Sandbox and Production before you turn on flows in Production, to confirm mappings and request bodies are accurate.
- After your integration app is live in Production, test any further changes in Sandbox first, then migrate them to Production. See Clone integrations and flows.
- For NetSuite sandbox accounts, NetSuite doesn't allow app developers (including Celigo) to push updates to SuiteBundles or SuiteApps. You must periodically upgrade your bundles in your NetSuite sandbox account yourself so your integration app stays on the latest version. Otherwise, Celigo can't keep your integration app updated.
- Multiple NetSuite sandbox instances count as a single endpoint, even if you have multiple connections to the same NetSuite account with different tokens and permissions. This rule doesn't apply to every app: for generic connectors such as the REST API connector, different URIs count as separate endpoints even if they belong to the same app.
Frequently asked questions
Do I need an integrator.io Sandbox license to connect to a NetSuite sandbox environment?
Not necessarily. If you're building a custom integration, you can create an integrator.io connection to a NetSuite sandbox environment without purchasing an integrator.io Sandbox license — specify the Environment setting on the NetSuite connection. This applies to any application, not just NetSuite.
Note: Although you can technically connect a NetSuite sandbox environment to your integrator.io Production environment using an integration app license, Celigo recommends purchasing an integration app Sandbox license instead. It lets you use your integrator.io Sandbox environment to connect to the NetSuite sandbox environment and test entirely within sandbox environments. If you use a Production license to connect to a NetSuite sandbox environment instead, you must uninstall the integration app once testing is done, then reinstall and reconfigure it to connect to Production.
Can I change my Shopify - NetSuite integration app from a sandbox instance to a production instance?
Yes. If your Shopify - NetSuite integration app has multiple stores, you can clone it from the sandbox instance to the production instance. For more information, see Clone integration app flows.
Can I switch a connection within an integration app from a sandbox instance to a production instance?
No, this isn't supported for most cases, and Celigo doesn't recommend attempting it. Integration apps have dependencies on the specific app instance they connect to, so switching endpoints or accounts can affect the stability of the integration app.
The one exception is switching a connection to a different user within the same company (for example, from one employee's login to a shared service account) — that's supported. Switching a connection to a different instance of the same app (a different Shopify store, NetSuite account, or Salesforce org) isn't supported.
To move to a new instance, obtain a new integration app license, or request an uninstall from Celigo Support to free up your existing license for the new environment.
What happens to partially installed templates and integration apps during migration?
Partially installed templates and integration apps keep their current status and progress in your new environment.
Are global licenses for a connector available across environments?
Yes. A global license for a connector can be used across multiple environments. The expiration date for a global license is based on your integrator.io account, not the individual environment.
Learn more
- Multiple environments overview
- Migrate to a multi-environment structure
- Create and manage multiple environments