How do you take only ticket data from the data center production database and move it to non-prod?

Eric Reguin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 16, 2024

I am working on a migration effort to the Cloud. I am developing the new projects in my non-production application and will migrate those new projects and ticket data to the Cloud. How can I copy only ticket data from my Production database and refresh/restore/write that ticket data into my non-production database?

 

1 answer

0 votes
waqas Wilan2026 April 16, 2024

The process of moving only ticket data from a production database to a non-production environment involves several steps to ensure data integrity and security:

1. **Data Extraction**: Use SQL queries or database export tools to extract only the ticket-related data from the production database. This might involve selecting specific tables or using filtering criteria to extract relevant data.

2. **Data Transformation (if necessary)**: Depending on the structure of the non-production environment or any specific requirements, you might need to transform the data format or structure. This could involve data cleaning, formatting, or restructuring.

3. **Data Transfer**: Transfer the extracted and possibly transformed data to the non-production environment. This can be done through various methods such as database backup and restore, data import/export tools, or custom data transfer scripts.

4. **Data Validation**: Validate the transferred data in the non-production environment to ensure that it matches the original data and meets the required criteria. This may involve comparing counts, verifying specific data points, or running tests against the data.

5. **Data Masking (if necessary)**: If the ticket data contains sensitive information, consider masking or anonymizing certain fields to protect privacy and comply with regulations.

6. **Testing**: Test the functionality and performance of the non-production environment with the transferred ticket data to ensure that it behaves as expected. This may involve running integration tests, user acceptance testing, or performance testing.

7. **Documentation**: Document the process followed for moving the ticket data to the non-production environment, including any transformations, validations, or masking performed.

8. **Monitoring and Maintenance**: Monitor the non-production environment to ensure that the ticket data remains synchronized with the production environment. Schedule regular updates or data refreshes as needed.

It's important to follow best practices for data management and security throughout this process to minimize the risk of data loss or unauthorized access. Additionally, consider involving stakeholders such as database administrators, developers, and data governance teams to ensure a smooth and compliant data transfer process.

Eric Reguin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 16, 2024

The part that I am curious about is the production data extraction and then "importing" that data into the non-production database. Like, what would those queries be, and how would I do this?

 

Suggest an answer

Log in or Sign up to answer