JIRA project copy sandbox to production checklist
Asked by Benjamin D:

I have created a project in our company's JIRA sandbox environment.

What checklist items should be considered before copying a sandbox project into production environment so that it will not affect the production instance in any way.

1. [Backup the JIRA (cloud)](https://support.atlassian.com/jira-cloud-administration/docs/export-issues/) production environment
2. Project KEY and Project name do not conflict
3. Issue type scheme is its own scheme
4. Workflows scheme is its own scheme
5. Screens scheme is its own scheme
6. Fields configuration scheme is its own scheme
7. Project permissions scheme is its own scheme
8. Issue security level scheme is its own scheme

If all these steps are confirmed, will there be any interference with production at all?

Will the custom fields I have created copy over with the project or will they need to be setup first or copied over somehow?

A checklist would be a great KB for Atlassian


Answers:
author: Trudy Claspill
body: Hello [@Benjamin D](/t5/user/viewprofilepage/user-id/5538033)

Welcome to the Atlassian community.

What method are you going to use the copy the project from the sandbox to production?

As per this unresolved Suggestion, there is not currently a method specifically for copying data from a sandbox to its production instance.

<https://jira.atlassian.com/browse/CLOUD-11150>

There are work-arounds suggested, including Cloud to Cloud migration, but in [this document](https://support.atlassian.com/organization-administration/docs/copy-production-data-to-sandbox/) it specifically says that Atlassian does not recommend that method.

If you are going to use that method anyhow, then you should review all the data on Cloud to Cloud migrations of Jira data, and make sure you review what does and does not migrate.

<https://support.atlassian.com/organization-administration/docs/copy-product-data/>

comments: author: Vish Reddy _Revyz_
body: Hi [@Benjamin D](/t5/user/viewprofilepage/user-id/5538033)[@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)

I am from Revyz, if you are trying to copy your configuration from the work you have done in a sandbox to your production site the Revyz apps could help you do that. We help address the following use cases:

- Comparing configuration changes done across sandbox \& prod sites (or more generically across any two sites) to understand what has changed

- Granularly copy specific configuration objects from sandbox to prod

- Copy entire project config from sand box to prod

The above functionality is available in two of our app:

- [Revyz Data Manager for Jira](https://marketplace.atlassian.com/apps/1228694/revyz-data-manager-for-jira-backup-restore-analyze-optimize?hosting=cloud&tab=overview)

- [Revyz Configuration Manager for Jira](https://marketplace.atlassian.com/apps/1231935/revyz-configuration-manager-for-jira?hosting=cloud&tab=overview)

Ofcourse we are heavily dependent on the API's that Atlassian has published.

We would love for you try our app and get your feedback.

Thank you

Vish


author: Luka Hummel - codefortynine
body: Hi [@Benjamin D](/t5/user/viewprofilepage/user-id/5538033)

If you are willing to try a third-party app for migrating projects between your production and sandbox environment, you could try our [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2748084).

We have even a detailed writ up on that use case [here](https://documentation.codefortynine.com/deep-clone-for-jira/how-to-clone-issues-from-sandbox-to-production-jir?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2748084).


Tags: cloud

jira-cloud