[rt-users] RT unification (merging multiple RT instances)

[Vetter, Isaac A]

Hi All,

Within my sub-organization, there were recently four distinct RTs running in
various departments. We're making an effort to unify these. So far,
departments have been willing to abandon their ticket databases to move.

This is no longer the case. So, I'm looking at "unifying" two separate RTs
by merging their data. We need a script that could migrate tickets from one
RT to another without losing data.

Considering the three options of using bin/rt, the API, or native db dump
and a data massage tool, I think that the API is the better (re-usable,
smaller chance of horribly breaking stuff, etc) route.

Is there an option that I'm missing? Is there a (small) chance that someone
already has an excellent perl script that Google doesn't know about? Any
words of advice?

Much Thanks,

Isaac Vetter
Purdue University

P.s. This project would be much, much easier if the API was even minimally
documented. Yes, I appreciate the POD documentation, but that's module
documentation. The fact that something like this:
<http://www.cpan.org/authors/id/A/AH/AHARRISON/scripts/rt-class-map-1.3.pl>
Is necessary at the end-user level is pretty intimidating.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2426 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20081107/1932f4b0/attachment.bin>