2019-05-25 08:07:42 +00:00
|
|
|
# rt2zammad
|
2019-05-27 11:18:59 +00:00
|
|
|
|
|
|
|
|
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
|
2019-05-27 11:33:04 +00:00
|
|
|
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.
|
2019-05-27 19:20:26 +00:00
|
|
|
* Zammad will send notification for all actions, you probably want to disable
|
2020-12-30 08:39:36 +00:00
|
|
|
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.
|
