What comes with you
Your checklists, templates, and statuses come across. A second import does not overwrite lists that are already there. The source audit log stays a record of the old site. It is not written onto the new issues. If a person, a project, or an issue is missing on the new site, that piece is skipped and the log names it.
If the old site still keeps the lists only in Smart Checklists or HeroCoders, import them there first. Then export. If you are choosing the app before the move, Checklist for Jira is the newer one, with more of the daily work and a lower public price. At 200 licensed users that price is $50 a month. Checked October 25, 2026. The comparison has the rest.
How to start
Follow Move Checklist data to another Jira site. This is Jira Cloud to Jira Cloud. It is not a Data Center or Server move, and it does not replace Jira’s own project copy.
Put this on the work item with Checklist for Jira
Templates, automation, workflow gates, and a Rovo agent — free for teams of up to 10 users.
FAQ
How do I move checklists to another Jira site?
Export Checklist data on the source site. Let Jira copy the projects. Import the file on the destination. The docs have the steps.
Will a second import overwrite the new site?
No. Checklist data that is already there stays as it is. A second import fills in only what is still missing.
Can I move checklists from Jira Data Center this way?
No. This is Jira Cloud to Jira Cloud, after Jira has copied the projects.