Jira Project Migration with Plugin Data Preservation (Sandbox to Production)

nboreddy

Hi Team,

We have a Jira project available in the Sandbox instance, and we need to migrate this project to the Production instance, including all associated plugin data. The migration must ensure that there is no disruption or loss of configuration for the following project-related components:

1. Automation Rules
2. Xray Custom Settings
3. Xporter Templates
4. Table Grid Editor (TGE) Tables
5. Workflow Post Functions associated with Xporter
6. ScriptRunner Behavior and Listener Scripts

Please recommend a migration approach that preserves all project configurations, plugin settings, and dependencies while ensuring a seamless transition from the Sandbox environment to Production.

 

Regards,

Nihanth

Arkadiusz Wroblewski

Hello @nboreddy 

I’d be very cautious about using a generic migration plan here

This isn’t a simple project copy, it’s a complex deployment across multiple marketplace apps that handle data uniquely. Atlassian’s native Sandbox Configuration Deployment (Actually in Beta so still in Testing!!!) can move core settings like workflows, but it completely excludes issue data, app-managed fields, and configurations for tools like Xray, Xporter, Table Grid Editor, and ScriptRunner. You'll need to verify the migration path for each app vendor individually.

Given these heavy dependencies, you should engage an Atlassian Solution Partner to map out your specific data requirements and build a safe, rehearsed cutover plan. The Community can definitely help you troubleshoot specific steps along the way, but drafting a full end-to-end runbook from the current details carries too much risk, and nobody with at least some Atlassian knowledge will advise it to you.

Also look on Limitations Data deployed from sandboxes | Atlassian Support

Best,

Arek 🤠