# Epic OP-7325 - Enable export / import of configuration between OpenProject environments

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-7325

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2028 Q2 |
| Date |  |
| Votes | 9 |
| List |  |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 350d 0h |

## Description

### User Problem

#### User

*What persona, persona segment, or customer type experiences the problem most acutely?*

  - System admin
  - Project manager

#### Problem

*What problem or job does the user have?*

  - User needs to copy over configuration from one OpenProject environment to another one
      - Example: A user tries out configuration changes on an OpenProject staging environment and (if successful) wants to copy over the changes to the production environment.

#### Pain

*What is the primary workaround that users perform that we could remove or replace? Why is it painful?*

  - Currently users need to keep in mind which changes they performed on their staging environment and then manually perform these changes again on their production environment.
      - This requires manual steps which takes time and can be error-prone

### Solution

*How do we solve the user’s problem. What is our “pain killer”? What must we achieve in the first version of the solution in order to achieve value for the user?*

  - An option to export / import configuration data (without projects or members) would address the problem
  - It should be possible to export / import these settings (as a starting point):
      - Work package types
      - Work package statuses
      - Workflows
      - Colors
      - Enumerations

#### Out of Scope for the MVC

*What should NOT be in the minimal viable change, and can be considered for future iterations? Why? Please order them by importance.*

  - The option to activate / deactive which settings should be copied.
      - While very useful in the future, in the first iteration it would be sufficient to address all the configuration data.

#### Differentiation

*What do you believe will differentiate us from the current experience or competitive experiences?*

  - An import / export between staging / production environment is not available in many other solutions

#### Next iteration

*What is the next solution that would allow us to release meaningful customer value quickly?*

  - Enable export / import of the aforementioned settings between OpenProject environments

### Launch and Growth

#### Measures

*How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?*

  - Users do not request this feature anymore.
  - The feature is used by 10% of all large OpenProject environments (100 or more users).

#### Messaging

*If you were to write a press release, how would you describe the value to customers?*

<figure class="table"><table><tbody><tr><th>Headline</th><td></td></tr><tr><th>First Paragraph</th><td></td></tr><tr><th>Customer Quote</th><td></td></tr></tbody></table></figure>

#### Go to market

*How are you planning on getting this into users' hands?*
