Migrate Freshdesk support to Zammad
Plan Freshdesk-to-Zammad migration with ticket and article mapping, private-note preservation, attachment checks, mailbox cutover and reply reconciliation.
Last updated
In short
- Ticket headers, conversations and attachments require separate extraction checks.
- Private notes must remain private after migration.
- Only one system should own inbound and outbound support traffic at cutover.
On this page (7)
Migration plans · Part of Zammad
Move the conversation and channel behavior together
A support migration must preserve who asked for help, what agents replied, which notes were private and what still needs action. Copying ticket titles and statuses is not enough. Mail routing and automation also need a controlled transition so customers do not receive duplicate replies or lose responses during cutover.
This is an API-assisted reference plan, not a claim of a tested native Freshdesk importer. Verify the chosen migration tool or script against the actual Freshdesk plan, Zammad release and available API permissions. Keep the source service accessible until ticket fidelity and channel behavior have been accepted.
Separate extraction of tickets and conversations
The Freshdesk API reference documents ticket, conversation, contact, attachment and related resources. Follow pagination, time filters and rate limits deliberately. A default ticket-list response should not be assumed to contain every historical ticket or every conversation article.
| Source object | Target treatment | Acceptance check |
|---|---|---|
| Ticket ID | Retained external reference | Stable source-to-target mapping |
| Subject and description | Ticket title and initial article | Formatting and content fidelity |
| Public replies | Customer-visible articles | Sender, recipients and ordering |
| Private notes | Internal articles | Never visible to customer accounts |
| Contacts and companies | Customer and organization mapping | No accidental identity merge |
| Agents and groups | User and group mapping | Correct ownership and restricted access |
| Status and priority | Approved target state mapping | Open and waiting work remains actionable |
| Attachments | Download and supported upload | Content digest, filename and access |
| SLA and automation | Rebuild separately | Timers, routing and notifications behave as intended |
Preserve original timestamps and authors as supported fields or clearly labelled source metadata. If the target API cannot recreate a historical property faithfully, retain it in the migration archive and document the limitation rather than fabricating native history.
Design customer identity carefully
Email addresses can appear in multiple source contexts, shared mailboxes or inactive contacts. Establish a deterministic customer mapping and review collisions. Do not merge two people solely because a display name matches. Preserve organization membership only where it should grant shared-ticket visibility.
Set up agent groups and roles before importing restricted tickets. The Zammad ticket API states that ticket availability depends on agent and group permissions. Use that boundary in the migration and acceptance design rather than giving every agent access to all imported groups.
Use a temporary migration identity with the required scope, then revoke it after the transition. Store exports and downloaded attachments in restricted storage because support conversations can contain sensitive personal or business information.
Rebuild articles and attachments in order
Create or map customers and organizations, then create tickets and their articles using supported APIs. The Zammad article API is the reference for article fields and attachments. Keep a ledger of source ticket and conversation IDs to avoid duplicating articles after a retry. Zammad explicitly warns that an internal visibility flag does not prevent an email article from being sent; preserve private notes with the correct article type as well as visibility and recipient controls.
Suppress or otherwise safely control notifications and outbound channels during rehearsal using the supported mechanisms for the selected release. Do not rely on one notification flag to prove that every trigger, email channel and integration is inactive. Test the complete target behavior with synthetic recipients before importing real history.
Attachments should be fetched while source access remains valid. Verify byte counts or digests and inspect a sample of different formats. Links to authenticated Freshdesk files will not remain usable merely because they were copied into a Zammad article.
Use a ticket fidelity exercise
Create synthetic cases covering a new request, a closed request, an internal note, a reopened ticket, multiple attachments, a shared organization and a restricted agent group.
| Test | Required result |
|---|---|
| Ticket counts | In-scope tickets reconcile by stable source ID |
| Conversation counts | Articles reconcile or have an accepted exception |
| Private note | Agent sees it; customer cannot |
| Attachment | Authorized user opens matching content |
| Customer identity | Correct requester and organization visibility |
| Open queue | Owner, state and priority match operational intent |
| Search | Known source reference finds the target ticket |
| Notifications | No historical import sends unintended customer mail |
Have agents inspect full threads, not only aggregate counts. Inbound/outbound article types and recipient fields matter to future replies. A misplaced internal note is a security defect even if every ticket was imported.
Cut over mailbox ownership explicitly
Record the last source ticket update and inbound message processed before the final migration window. Pause or redirect intake under a planned sequence, reconcile changes since rehearsal, then enable the target channel. Verify sending identity, reply routing, authentication and threading with a synthetic customer exchange.
Only one system should send automated acknowledgements or consume the same mailbox under the intended design. Review forwarding rules, webhooks, chat widgets, forms and API clients. Keep an exception queue for messages received during the transition so none disappear between systems.
Roll back with reply reconciliation
If the target fails before agents begin work, restore the source channel configuration after ensuring the target no longer consumes or sends messages. Once agents have replied from Zammad, preserve those articles and reconcile them into the source or a readable support record before switching back.
Back up Zammad’s database, attachment storage, configuration and secret material. Retain the source and migration ledger through the acceptance period. Do not delete source tickets simply because target counts match. Completion requires accepted conversation fidelity, private-note isolation, correct mailbox behavior and a recovery process that preserves customer interactions.
Sources and further reading
Use the linked documentation to confirm the version, edition and contract that apply to your project.
