Deploy local packages

After a local package has been created, it can be deployed to a target tenant. That means that all the resources associated with the package are imported to the target tenant. Instructions and guidance for deploying a local package are provided in this topic.

Some applications require steps to be performed in the application before a deployment or after a deployment. See the "Deployment" topic in the application-specific guides for details. These guides are included in the CloudSuite documentation libraries and the application-specific documentation libraries.

The deployment does not complete successfully in these cases:

  • Another package deployment to the same target tenant, local or global, is currently INPROGRESS.
  • A data refresh involving one or more of the target environments is INPROGRESS.

Wait for these events to complete before launching a deployment.

Caution: Deploying a local package overwrites the existing resources in the tenant. Ensure that you understand the implications of deploying a local package to an existing tenant before proceeding.
  1. Sign in to CSSP.
  2. Select Configuration Management > Local Packages.
  3. Select the package to go to the Local Package Details page.
  4. Click Deploy Package.
  5. Select Local Package Details > Target Tenant. The PRD tenant can only be selected if the Deploy to PRD label for the selected package version is set to Yes. See the Deploy to PRD section of this guide.
  6. Select Available Package Version.
  7. Click Deploy.
  8. In the Deploy Package Wizard select the target tenant from the list.
  9. Optionally, select the Generate Compare Report check box to generate a report previewing the changes to the target tenant before the changes are deployed.
  10. Optionally, select the Create Tag Upon Deployment check box to create a tag automatically on the target tenant. The tag contains all resources that the source package deploys. You can use the created tag later to recreate the same package from the target tenant. As of release 2026.10, this capability applies to the M3 product.
  11. Click Next to go to the Target Apps Organization page.
  12. For each application, select the target organization from the list.
  13. Click Next to go to the Review Package Options page.

    Each application has a tab labeled with the application’s name. For each tab, review the selected options and organization.

  14. Click Submit. The deployment starts immediately when no conflicting activity exists on the target tenant. If another deployment or action is in progress on the same target tenant, the system places the deployment in a queue. The system starts the queued deployment automatically after the conflicting activity completes.