Request tracker to Zammad migration scripts

Find a file

Michal Čihař b3383c542a Share code for creating tickets		2020-12-30 13:30:22 +01:00
.gitignore	Download and cache rt data	2019-05-25 11:01:10 +02:00
LICENSE	Initial commit	2019-05-25 10:07:42 +02:00
README.md	Document caching	2020-12-30 09:47:15 +01:00
requirements.txt	Remove not needed dependency	2019-05-27 12:05:42 +02:00
rt2zammad.py	Share code for creating tickets	2020-12-30 13:30:22 +01:00

README.md

rt2zammad

Request tracker to Zammad migration script. This is not an out of box solution for everybody, you will probably have to customize it.

Known issues

Disabled users from RT can not be accessed by API, thus will lack email address and will fail to be created. Enable all users prior to the migration.
Timestamps are not preserved. The Zammad API doesn't seem to allow this.
Zammad will send notification for all actions, you probably want to disable outgoing mail for time of import:
- Disable all triggers sending mail (Manage / Trigger
- Disable notifications for all existing users (seems like every user has to do this)
- Safer approach might be to use own SMTP server and temporarily discard all mail from Zammad for the migration run.

Maintenance status

No further development is expected there. This was used once to migrate Weblate and I have no intent to improve this script myself. Pull requests are still welcome though.

Usage

Prepare virtualenv and install dependencies: virtualenv .venv --python python 3; . .venv/bin/activate ; pip install -r requirements.txt
Start rt2zammad.py, it will display template for configuration file.
Fill in the template and save it as rt2zammad.json.
Start rt2zammad.py to perform the migration.
Verify the migration results.
In case you need to roll back Zammad, please follow https://community.zammad.org/t/reset-database-to-start-from-zero/326

Note: The RT content is cached in rt2zammad.cache. In case the RT is still receiving updates, you might want to delete the file for consequent runs.