The subject says it all. I'm not opposed to just installing clean, if there is some way to keep the ticket history.
If upgrading is an options, what is the lowest number of version hops? I'm guessing every sub version upgrade is not required.
Upgrading (or migrating the content) from 2.2.5 to current ver
Moderator: crythias
-
root
- Administrator
- Posts: 4253
- Joined: 18 Dec 2007, 12:23
- Znuny Version: Znuny and Znuny LTS
- Real Name: Roy Kaldung
- Company: Znuny
- Contact:
Re: Upgrading (or migrating the content) from 2.2.5 to current ver
It'll be a long way. You have to take every minor version, just skip the patch level updates:
2.2.5 => 2.3.latest => 2.4.latest =>3.0.latest => 3.1.latest => 3.2.latest => 3.3.latest => 4.0.latest => 5.0..latest
2.2.5 => 2.3.latest => 2.4.latest =>3.0.latest => 3.1.latest => 3.2.latest => 3.3.latest => 4.0.latest => 5.0..latest
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO
Use a test system - always.
Do you need professional services? Check out https://www.znuny.com/
Do you want to contribute or want to know where it goes ?
Use a test system - always.
Do you need professional services? Check out https://www.znuny.com/
Do you want to contribute or want to know where it goes ?