On 15/06/2013 21:27, Nathan Cutler wrote:
Hello everyone.
I'm about to embark on an RT migration from an existing instance
(running 4.0.13) to a new one (also 4.0.13). My use case is somewhat
specific in that:
1. the RT user ID values are different between the two instances
2. I only need to migrate open tickets (<50) so some manual work is OK
So far I'm thinking along these lines: make a user ID mapping table
(old -> new). Do the same for the queues. Export the open tickets as
SQL. Apply the mapping to the resulting text file (simple
search-and-replace). Apply the SQL to the new instance.
The only idea I have come up with (so far) to generate the SQL for a
particular ticket is Shredder. It seems like it might work, but before
I try it (on a copy of the database, of course), I thought I'd ask
here: Is this a reasonable course of action? Is there a better way to
achieve the same end?
Hi, I posted a script on this list that may help you:
http://lists.bestpractical.com/pipermail/rt-users/2010-October/067002.html
--
Easter-eggs Spécialiste GNU/Linux
44-46 rue de l'Ouest - 75014 Paris - France - Métro Gaité
Phone: +33 (0) 1 43 35 00 37 - Fax: +33 (0) 1 43 35 00 76
mailto:[email protected] - http://www.easter-eggs.com
--
RT Training in Seattle, June 19-20: http://bestpractical.com/training
