On Thu, Jan 31, 2008 at 12:24:05PM +0300, Konstantin Naryzhniy wrote:
> Hello everyone,
>
> I was hoping you could advise me on the RT migration issue we have
> encountered here at Parallels:
>
> We would like to merge one RT (old one) database in to another RT (new one)
> without losing any tickets or user data.
> These both RTs have about the same number of existing tickets (about 400k)
> and these tickets numbers are conflicting with each other.
> I've scrolled through the Wiki and the Lists, but failed to locate any data
> on the matter.
>
> Does anyone have experience of performing such a merge? I'd appreciate any
> recommendations and solution to make sure we do not lose any old RT data when
> moving to the new RT.
> Tricky issues that I see, apart from the id conflicts are:
> 1) the 'old' RT is 3.6.5 while the 'new' one's 3.4. Don't ask why=)
That's actually unlikely to be a huge issue, actually.
> 2) the conflicts in user emails can exist. Customers could be registered
> in both RT instances prior to merging.
Also, the fact that all of the subsidiary records are going to conflict
as well. We started on a merge tool once, but didn't get far on it since
it was just a thought experiement at the time.
-j
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
