I want to move a non-technical project's tickets to a new project, do I lose any data?

[Kash Sinduria]

Hi there,
I am planning to move a non-technical project's tickets to a new project. I just want to clarify a few things prior to actioning that:

1. Do I lose any dependencies?
2. Do I lose any data - comments / files attached to the tickets?
3. Do I need lose any fields' data (generic fields provided on project initiation) from original project?
4. Does it move all the COMPLETED tickets as well?
5. How long will it take for the ticket's to migrate? Will there be any intermittent affects on the existing project? If this is going to take long, is there a way to COPY all tickets to the new project?

[Fabian Lim]

Hi @Kash Sinduria 

Answers to your questions

1. No.

2. No

3. Data won't be lost, but you need to ensure that the same fields are available in the new project screens for create/edit/view screens in order to view the old data.  

4. When you move the tickets, it will prompt you to map the statuses from the old workflow to the new statuses. If you want to keep the same statuses, make sure that your new project has the exact workflow.  

5. It depends on the amount of tickets and data.  I would try first moving one ticket before you do a bulk move.  

Regards.

[Trudy Claspill]

Hello @Kash Sinduria 

Welcome to the community.

Is the source project a Team Managed project or a Company Managed project? What about the destination project? It will say at the bottom of the navigation pane on the left.

And what type of work is tracked in the source and destination projects; Work Management (aka Business), Software, or Service Management? That will show at the top of the navigation pane below the project name.

Answers to some of your questions depend on the answers to the above. If you are using a Team Managed project as either the source or destination, there can be data loss and dependency loss. If you are moving issues between projects that track different types of work, there may be some data loss.