Zammad — Migration Support Overview
Role in migrations
- Staff (HD): supported as both (source and target).
- Company (HD): supported as both (source and target).
- Contact (HD): supported as both (source and target).
- Ticket (HD): supported as both (source and target).
- Category (KB): supported as both (source and target).
- Folder (KB): supported as both (source and target).
- Article (KB): supported as both (source and target).
Field-level support migrating FROM Zammad (Ticket)
| Field | Supported |
| Requester | Yes |
| Company | Yes |
| Assignee | Yes |
| Group | Yes |
| Attachments | Yes |
| Comments | Yes |
| Tags | Yes |
| Custom fields | Yes |
| CC | Yes |
| First Response Time | No |
| Created date | Yes |
| Updated date | Yes |
| Closed date | Yes |
Field-level support migrating TO Zammad (Ticket)
| Field | Supported |
| Requester | Yes |
| Company | Yes |
| Assignee | Yes |
| Group | Yes |
| Attachments | Yes |
| Comments | Yes |
| Comment Created date | Yes |
| Comment Author | Yes |
| Tags | Yes |
| Custom fields | Yes |
| CC | Yes |
| First Response Time | No |
| Created date | Yes |
| Updated date | Yes |
| Closed date | Yes |
Field-level support migrating FROM Zammad (Company)
| Field | Supported |
| Domains | Yes |
| Tags | No such field in platform |
| Custom fields | Yes |
| Notes | No |
Field-level support migrating TO Zammad (Company)
| Field | Supported |
| Domains | Yes |
| Tags | No such field in platform |
| Custom fields | Yes |
| Notes | No |
Field-level support migrating FROM Zammad (Contact)
| Field | Supported |
| Tags | No such field in platform |
| Custom fields | Yes |
| Phone | Yes |
| Notes | No |
Field-level support migrating TO Zammad (Contact)
| Field | Supported |
| Tags | No such field in platform |
| Custom fields | Yes |
| Phone | Yes |
| Notes | No |
Field-level support migrating FROM Zammad (Article)
| Field | Supported |
| Inline images | Yes |
| Attachments | Yes |
| Tags | Yes |
| Support multilevel Folder structure | Yes |
Field-level support migrating TO Zammad (Article)
| Field | Supported |
| Inline images | Yes |
| Attachments | Yes |
| Tags | Yes |
| Support multilevel Folder structure | Yes |
Migration options available for Zammad
- Select records for Demo - applies to: source (Ticket), source (Article)
- Inline images in tickets - applies to: source (Ticket)
- Skip ticket attachments - applies to: source (Ticket)
- Add a new tag to tickets - applies to: target (Ticket)
Zammad — Setup & How-To Guide
For more information: https://help-desk-migration.com/help/zammad-migration-guides/
How to create an Access Token in Zammad?
To create an Access Token in Zammad, follow these steps:
- Click the Profile icon located in the bottom-left corner.
- Select Profile from the dropdown menu.
- In the Profile sidebar, switch to the Token Access tab to proceed.
- Click the Create button to add a Personal Access Token.
- Enter a name for your token, expiration date (if needed), and check the following necessary permissions:
- Admin interface (admin)
- Knowledge Base Editor (knowledge_base.editor)
- Knowledge Base Reader (knowledge_base.reader)
- Agent tickets (ticket.agent)
- After assigning permissions, confirm by clicking the Create button.
- Copy the Access Token value displayed on the screen.
How to deactivate notifications in Zammad?
During Zammad data migration, it's essential to disable all notifications to ensure agents don't receive alerts during the ticket import process.
To turn off notifications in Zammad, follow these simple steps:
- Click the Profile icon located in the bottom-left corner.
- Select Profile from the dropdown menu.
- Switch to the Notifications tab.
- Locate the Also notify via email column and disable all notification > options by unchecking the boxes.
- Click the Submit button to save your changes.
Important: Agents can keep their notifications active if import mode is enabled.
How to enable import mode in Zammad?
Before migrating data to Zammad, it’s crucial to enable import mode. Without it, dates won’t migrate properly, and notifications may be sent unless manually disabled in the agent profile.
Follow the instructions below based on your Zammad account type to activate import mode.
Zammad SaaS accounts
- Trial accounts:
If you are using a trial version of Zammad, you will need to contact Zammad support to activate the import mod. Email enjoy@zammad.com and request that they enable the mod for you. - Paid accounts:
For paid Zammad accounts, the process is similar. Contact Zammad support by emailing support@zammad.com, and they will activate the import mod.
Zammad on-premise accounts
If you use a Zammad self-hosted instance, you need to enable the import mod yourself. To do so, access Zammad’s Rails Console and run the following command: Setting.set('import_mode', true)
How can I migrate the knowledge base to Zammad?
The Help Desk Migration service offers an easy way to import your knowledge base articles to Zammad. Before starting the migration process, you need to ensure that a knowledge base exists in your Zammad account.
If you haven't created one yet, follow these steps:
- Navigate to Admin settings.
- Select the Knowledge Base tab.
- Use the toggle button to enable the Knowledge Base.
- Choose the languages/locales where you want to publish the knowledge base. Here, you can also configure additional settings and select a theme, unify the knowledge base with the website's main navigation, or set up a custom URL.
- After configuring your knowledge base settings, click the Create Knowledge Base button.
Zammad Migration Limitations
- There is a size limit on attachments in comments. This limit can be increased — see the guide: https://community.zammad.org/t/e-mail-attachment-size/3282/3
- Tickets with the type Notes are migrated to Zammad without the ability to reply to them, so the client will need to create a new ticket instead.
Comments
0 comments
Please sign in to leave a comment.