[rt-users] rt2-to-rt3 id question

[Craig Schenk]

Im working on a script which will migrate custom templates, scripactions and
scropconditions. I noticed that when I run rt2-to-rt3 it *does* import rt2
custom scrips which dont rely on custom templates, actions etc. The import
script just seems to reject the scrips which rely on templates etc it cant
find in the database. Theoretically then, if I were to:

1) Initialize RT3 database

2) Run a script that dumps custom RT2 templates, scripactions and
scripconditions then imports them to RT3

3) Run rt2-to-rt3

That should let RT3 migrate over all the custom scrips. Most importantly, the
2nd step should bypass having to sit and manually cut and paste all the
templates etc using the web interface and setting scrips up by hand.

The only potential catch I see is id numbers. Does rt2-to-rt3 preserve Queue
ID numbers when it runs?