Agreed – CLI is a good way to go.
I wrote a Perl script to import the database from two other applications and that worked reasonably well.
One was a CSV export and the other was a MSSQL database we just connected directly to (two different cases that I munged into a single script)
I ran the importer against our test RT environment so I could continue to tweak it (and blow it away to start fresh) a number of times before going to prod – I highly recommend doing that!
Of note: Importing into RT will automatically create new ticket numbers for the old data. In our case, it was imperative that I kept the original ticket numbers from the one database import, so I ran it first (against an empty RT install) and set the ticket number, knowing it wouldn’t overwrite anything in a blank RT instance.
I have not looked at or updated the scripts for a long time now, but this may be helpful to get you started anyway:
http://parishnetworks.blogspot.com/2014/10/importing-into-rt-from-another-helpdesk.htmlFrom: rt-users [mailto:firstname.lastname@example.org] On Behalf Of Eierschmalz, Bernhard
Sent: Monday, April 04, 2016 4:01 AM
To: Dave Florek email@example.com
Subject: Re: [rt-users] Easy way to import a CSV file into ticketing?
I import many kinds of CSV-files with bash scripts and rt-cli – maybe this would be an idea for you!
Mit freundlichen Grüßen,
Von: rt-users [mailto:firstname.lastname@example.org] Im Auftrag von Dave Florek
Gesendet: Donnerstag, 31. März 2016 21:22
Betreff: [rt-users] Easy way to import a CSV file into ticketing?
If I have a CSV file full of information that I need to import into RT that’s not an asset, is there an easy way to do this? I’m looking at the information posted in Postgresql for the database, and it looks doable, however I’m not sure if I can do it with the UIDs that RT generates.