DocumentationWorkfrontWorkfront Guide

Use Environment Promotion for Adobe Workfront Planning

Last update: November 12, 2026

CREATED FOR:

  • User
  • Admin

The information on this page refers to functionality not yet generally available. It is available only for select customers in their Production and Sandbox environments since November 12, 2026. At a later date, the same features will also available in the Production, Preview, and Sandbox environments for all customers.

For information about releases, see Product releases .

IMPORTANT
The information in this article refers to Adobe Workfront Planning. Your company must purchase an additional Planning package to access Workfront Planning.
The functionality described here is not available if your organization purchased Workfront Planning as a standalone product.
For general information about Workfront Planning, see Get started with Adobe Workfront Planning.

You can copy Workfront Planning workspaces and their additional objects from one Workfront environment to another using Adobe Workfront’s Environment Promotion capabilities.

Instead of rebuilding everything by hand, you assemble the configuration into a package in the source environment and install it in the target environment.

Using Environment Promotion with Planning is similar to using it for Workfront. For more information, see the “Environment Promotion” section in the article Adobe Workfront testing environments.

Considerations about using Environment Promotion with Planning

  • You must be a Workfront administrator to use Environment Promotion.

  • When you copy a workspace to another environment, the following objects associated with that workspace are also imported through environment promotion:

    • Workspaces

    • Workspace sections

    • Record types

    • Fields

    • Views

    • Hierarchies

    • Sharing settings for all objects

    • Request forms

    • Business rules

    • Connected objects

    • Objects that the workspace depends on or that other objects are shared with, such as groups, teams, job roles, companies, and users.

      The following scenarios exist:

      • If an object with the same name already exists in the target environment, Workfront flags a conflict and you decide how to handle it.
      • If a team or a group that an object is shared with does not exist in the target environment, the promotion creates it.

  • For each object, you can do the following:

    • Create it as a new object
    • Use the existing object but create it with a new name
    • Overwrite an existing object. Overwriting replaces the configuration in the target.

  • You cannot export the following objects:

    • Automations that belong to the workspace you are copying
    • Records
    • Fields that don’t belong to the exported workspaces

  • Cross-workspace connected record types cannot be promoted, unless they already exist in the target environment.

    We recommend first promoting the workspaces that contain the cross-workspace connectable record types, and only after that, promote the workspaces that reference those record types.

  • Installation can take a few minutes. You can roll back an installation from the results page if needed.

  • We recommend to test the process before proceeding, when possible. You can install to a sandbox or Preview environment before promoting it to Production.

Access requirements

Expand to view access requirements for the functionality in this article.
table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 layout-auto html-authored no-header
Adobe Workfront packages

Prime or Ultimate Workflow package with a Prime or Ultimate Planning package
Adobe Workfront license Workflow Standard
Planning license Planning Standard
Access level configuration You must be a System Administrator
Object permissions

Manage permissions to workspaces

System Administrators have permissions to all workspaces, including the ones they did not create

For more information about Workfront access requirements, see Access requirements in Workfront documentation.

Import Planning configuration using Environment Promotion

The following are the main steps to promote Planning configuration to another environment:

Follow the instructions in the following sections to copy a Planning configuration between two Workfront environments.

Create a package in the source environment

  1. Go to a source environment where your desired configuration is in place.

  2. In the source environment, click the Main Menu Main Menu , then go to Setup > System > Environment Promotion.
    The Configuration Packages list shows existing packages with their status, source environment, and where they were deployed.

  3. Click Create package.

    note tip
    TIP
    A package needs at least one object before it can be assembled and installed.

  4. On the Package Details tab, enter a Name and a Description for the package. The source environment is already filled in with the current (source) environment.

  5. In the list of object types on the left, select Planning workspace.

  6. Search for the workspace you want to promote, select its checkbox, and click Add Planning workspace. The workspace appears under Package Contents.

    Workspace selected for Environment Promotion

  7. Click Save and assemble.

    Workfront assembles the package and adds an entry on the package’s Updates tab. You can review what the package includes on the Contents tab.

  8. (Conditional and optional) Click Save and close instead if you want to finish later.

  9. (Optional) Click Contents to review the contents of the package or click Deployments to see if this package has been deployed multiple times.

    Continue to make the package ready to install.

Make the package ready to install

Before installing the package in the target environment, we recommend you test it in a testing environment.

  1. After the package has finished building as described in the previous section, click Package Details, and click Edit, set the Status to Testing, then click Save and close.

    note tip
    TIP
    After building the package its status is set to Draft. The Active status is not available until you have tested the package first.

  2. (Recommended) Click Install and choose one of the testing environments available to deploy it there and test the configuration.

    note tip
    TIP
    The Production environment is not available as one of the options when the status is set to Testing.

  3. After you install it in a testing environment, click Edit again, and set the Status to Active, then click Save and close.

    note tip
    TIP
    Installing the package in a testing environment is similar to installing it in Production, as described in the following section.

    Continue with the following section to install the package in your target environment.

Install the package in the target environment

  1. On the package page, after you have verified it, click Install.

  2. In the Target environment list, select the environment to deploy to (for example, your Production environment), and click Continue. The default target is the current environment.

  3. On the Package info page, confirm the source environment and the environment you are deploying to.

  4. In the Object mapping section, expand each object grouping, such as a Planning workspace, to review the objects.

    note tip
    TIP
    Groups, teams, roles, companies, and users might display here, if any of the workspace objects are shared with them.

  5. For each object, review the Collision and Status columns, then choose a Deployment action from the list. Choose from the following options:

    • Create new: Adds the object to the target. Use this when no collision is detected.
    • Use existing: Maps the object to one that already exists in the target, such as a workspace with the same name.
    • Create with new name: Adds the object under a name you specify.
    • Overwrite: Replaces the existing object in the target with the one from the package.
    note tip
    TIP
    If the system does not find a workspace with the same ID, it tries to find a match based on the workspace name.

  6. (Optional) To change several objects at once, select their checkboxes, choose an action in the Deployment action list at the top of the group, and click Apply to selected. Use the filters above the list, such as Show only errors, to focus on specific objects.

  7. Resolve any error indicators. If you select Use existing for an object, you must also select the object it maps to. Otherwise, the status shows an error and Deploy stays unavailable.

  8. Click Deploy, then Deploy to confirm.

    Workfront shows an installation page with the message This package is being installed. This may take a few minutes.

    When the installation finishes, the page shows a success message, the environment where the package was installed, and a list of the installed objects, with a status for each, such as Used existing or Installed (Create new).

  9. (Optional) Click Roll back installation, if needed to revert the installation and remove the configuration from the target environment.

    Continue to verify the results of the installation.

Verify the results

  1. Go to the target environment > Main Menu > Planning and find the imported workspace.
  2. Open the record types and views to confirm the fields and layout match the source. Records are not included, so tables are empty.
recommendation-more-help
workfront-help-quicksilver