"Work on the back end" is a scary phrase to me though, it sounds like you might be thinking of touching the database outside Jira (with SQL).
Do not do this. Jira uses the database as a data store, and most of the logic that keeps the data coherent is in the application, not the database. This makes it very hard to get any SQL completely right and I've spent years cleaning up the messes made by people using SQL without fully understanding what they are doing in the Jira database.
Instead of worrying about data loss (right thing to worry about, but SQL is the best way to pretty much guarantee you will incur loss), could you explain what you are trying to achieve? We can probably tell you the best and safest way to do it.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event