[rt-users] Migrating RT3.8 database to RT4.2

Jim Brandt jbrandt at bestpractical.com
Wed Feb 10 10:59:19 EST 2016

Hi Lee,

The typical upgrade path is to take a backup of your database (I think 
that's what Matt was pointing out), restore it on the new machine, then 
follow the steps in 6b in the README:


(It's good to read the whole README, but those are the key bits that are 
different for upgrading an existing instance.)

The upgrade scripts will then upgrade your database to be compatible 
with the new version of RT.

The serializer and importer tools are typically used in special cases 
where a DB upgrade won't work, like moving from one brand of DB to 
another or doing other things like joining two RT's together.


On 2/10/16 10:48 AM, Lee Wiscovitch wrote:
> Thanks, that looks like it could be an option too.
> Digging through the docs more, I see that there are two utilities that 
> could be more useful:
> rt-serializer
> rt-importer
> If I'm reading it correctly, I can use rt-serializer to export the 
> contents of the RT3.8 database and then take that and feed it into the 
> rt-importer on the RT4.2 instance.
> But, it doesn't look like they existed in RT3.8...So maybe not really 
> an option? I wonder if I could still point the RT4.2 rt-serializer to 
> the RT3.8 mysql database and still use it?
> On 02/08/2016 04:44 PM, Matt Zagrabelny wrote:
>> On Mon, Feb 8, 2016 at 3:35 PM, Lee Wiscovitch 
>> <lwiscovitch at monetra.com> wrote:
>>> There is no import/export feature that I can use right?
>> https://www.bestpractical.com/docs/rt/4.2/backups.html
>> -m
> ---------
> RT 4.4 and RTIR Training Sessions 
> (http://bestpractical.com/services/training.html)
> * Hamburg Germany  March 14 & 15, 2016

More information about the rt-users mailing list