Check what you actually exported
A ticket count does not tell you whether its replies, notes, files, and older history came too.
How To · Updated October 7, 2026
Help Desk Migration Checklist
Move your tickets and customer history, catch missing replies or files early, and switch over without sending new requests to two inboxes.
Before you move everything, make sure you know what “everything” includes. Ticket exports can leave out replies, older records, or attachment files. Check the export, test a few real examples, and only switch over once your team can find the history it needs.
Before the checklist
Why a “successful” import can still feel incomplete
An import can finish cleanly and still leave your team asking, “Where did that reply go?” or “Why is this attachment just a link?” The source export may not contain everything you expected, and the two help desks may use different fields or status names.
There is a second job, too: getting new requests into the right place. Email forwarding, forms, automations, and integrations may need their own cutover. Moving old tickets does not automatically move the way your team works.
Try real examples first
A few familiar tickets will show you more than a green “complete” message.
Give new requests one home
Pick a clear moment to stop the old inbox and start the new one.
The migration plan
Seven stages from inventory to signoff
Work in order. Each stage reduces a different kind of risk.
01
Inventory what must move
Know what your team relies on before you export anything.
- List tickets, conversations, attachments, contacts, companies, agents, knowledge articles, tags, categories, and custom fields.
- Check the export itself: does it include archived tickets, the full reply thread, private notes, and the files attached to each reply?
- Mark which records must remain searchable and which can stay in a read only archive.
- Write down every support address, forwarding rule, form, portal link, automation, and integration that sends work into the current help desk.
02
Choose the right import path
Use a direct connector when history matters. Use CSV when portability matters.
- Choose a direct importer when it can bring over the history and files your team needs.
- Choose CSV when a clean table is enough. A ticket row is useful, but it is not the same thing as a ticket and its full conversation.
- Before you commit, ask what the export leaves out and what the destination will skip.
03
Clean the source before export
A migration carries old clutter as faithfully as useful history.
- Merge duplicate contacts and companies where it is safe to do so.
- Resolve or label abandoned test tickets so they are easy to exclude.
- Remove obsolete agents from the active rollout list without deleting their historical ownership.
- Review knowledge articles for private notes, old links, and outdated instructions.
04
Map fields and values
Make sure the same words mean the same thing in both systems.
- Map ticket status, priority, type, category, requester, assignee, and dates.
- Decide where custom fields and tags belong in the new workspace.
- Keep a short note of anything renamed, combined, skipped, or moved into notes. That makes surprises easier to explain later.
05
Run a representative pilot
Find mapping mistakes while they are still easy to correct.
- Test a small mix of open, closed, old, new, simple, and complex tickets.
- Include an old ticket, a recent one, a long thread, an internal note, a large attachment, and a record with custom fields.
- Ask an agent who knows the old system to compare the same records side by side.
06
Plan the cutover
Keep new requests from being split between two inboxes.
- Pick a quiet window and tell agents when the old help desk becomes read only.
- Choose the exact time to update email forwarding, portal links, forms, and integrations.
- Pause old automations that could send duplicate replies after the final export.
- Keep a rollback note with the old routing settings until the new flow is verified.
07
Validate before closing the old account
A completed import is not the same as a verified migration.
- Compare record counts and review the import report for skipped or failed rows.
- Open sample tickets and verify dates, requesters, ownership, status, replies, and attachments.
- Search for several known customers and old ticket subjects.
- Keep the old system available according to your retention and contract requirements until the team signs off.
Choose the transfer method
Direct importer or CSV?
Neither method is automatically better. The right choice depends on how much history and structure you need to preserve.
Direct importer
Best when the connector understands the source system and can retrieve related records through its API.
Usually better for
- Threaded ticket conversations
- Ticket attachments
- Agent and requester relationships
- Source specific fields and identifiers
CSV import
Best when the old tool can export clean tables or when you want control over every mapped column.
Usually better for
- Companies and contacts
- One row per ticket
- Knowledge articles
- Cleaning and reshaping data before import
Important CSV limitation
A flat ticket file cannot represent a complete reply thread or its attachments. If that history must remain inside each ticket, use a direct importer or ask the destination team about a custom migration path before committing.
Before you export
What transfers—and what can get left behind?
Start with the export, not the import button. A file can look complete while it only contains the ticket fields you can see in a list. Ask the old provider what that export includes, then use a few familiar tickets to check the answer.
Replies and internal notes
Does the export include the whole thread, including older or archived tickets? Can you still tell which messages were private? Freshdesk says its standard ticket export leaves out full conversations and archived ticket history; an account export is needed for that history. See Freshdesk’s export guidance.
Attachments that really open
Check that the file itself came across, not just a link. Zendesk’s guidance uses its API to retrieve ticket attachments; private files can need authenticated access, and some download links expire. See Zendesk’s attachment guidance.
Fields that still mean the same thing
Compare status, priority, requester, assignee, tags, and custom fields. “Pending” may need to map to a different status in the new help desk. Keep a note of fields you rename or skip so agents know where to find that information.
The work around the tickets
Forms, email forwarding, notifications, automations, and integrations may need to be set up again. Make a list before cutover, then send a test request through every channel your customers use.
If you’re moving into FyneDesk
Direct imports from Freshdesk, Zendesk, and Zoho Desk support conversations and attachments. A CSV ticket is one row, so it cannot rebuild a full thread or carry its files. FyneDesk skips attachments over 25 MB and lists them in the import report. Check the current import details before choosing your route.
The FyneDesk path
Try a few real tickets before you switch
FyneDesk includes import and migration support on every plan, including Free. Start with a small sample, look closely at the result, and sort out any field or file issues before changing your live support address.
- Direct import: Freshdesk, Zendesk, and Zoho Desk can bring over agents, contacts, companies, tickets, conversations, attachments, custom fields, teams, and knowledge articles.
- CSV: Guided imports for companies, contacts, tickets, and knowledge articles with column and value mapping.
- Control: Imports run in the background and can be paused, resumed, or cancelled.
- Review: The results report separates created, linked, skipped, and failed records with reasons for failed rows.
Import sourceConnection
FreshdeskDomain and API key
ZendeskSubdomain and API token
Zoho DeskSecure OAuth connection
Other help desksCSV upload and field mapping
Every path includes a guided scope, mapping, progress, and results flow. Zendesk is phasing out API tokens beginning July 28, 2026. If your account cannot create one, ask FyneDesk about a safe migration path.
Pilot review
What to verify before the full import
A “complete” message is a good start. Now open the records and check the details your agents rely on.
| Area | What good looks like |
|---|---|
| Replies and notes | The thread is in order, authors and dates make sense, and private notes have not become customer-visible replies. |
| Attachments | Files open from the right ticket. Check filenames and larger files, not just the attachment count. |
| Fields and status | Statuses, priorities, custom fields, and tags still mean what your team expects. |
| People | Requesters and companies are matched correctly. Former agents still make sense in the ticket history. |
| Knowledge | Titles, categories, links, formatting, and publication status are correct. |
| New requests | Support email, forms, portal links, and integrations create tickets only in the new workspace. |
| Agent workflow | Routing, notifications, templates, permissions, and one real reply work as expected. |
Cutover day
Move the live support flow in a controlled order
- 1Finish the final export.
Record the export time so everyone knows where the old history ends.
- 2Start the final import.
Watch progress and resolve blocking errors before changing customer entry points.
- 3Switch inbound routes.
Update email forwarding, forms, portal links, and integrations so new requests land in one place.
- 4Send real tests.
Submit a request through every active channel and confirm assignment, notification, reply, and resolution.
- 5Make the old workspace read only.
Keep it available for validation and retention, but stop agents from creating split history.
Frequently asked questions
Help desk migration questions
Can I migrate from any help desk to FyneDesk?
FyneDesk has direct importers for Freshdesk, Zendesk, and Zoho Desk. If you use another help desk that can export usable CSV data, FyneDesk can import companies, contacts, tickets, and knowledge articles through the CSV workflow. Contact FyneDesk before you begin if your export uses unusual fields or formats so the mapping can be reviewed first.
Will customers receive emails during a FyneDesk import?
No. FyneDesk imports are silent. Customer notifications do not send and ticket automations do not run while historical records are being imported.
Can I move the whole conversation with a CSV file?
A standard FyneDesk ticket CSV has one row per ticket, so it cannot rebuild the full reply thread or bring over ticket attachments. FyneDesk direct importers support conversations and attachments for Freshdesk, Zendesk, and Zoho Desk. Check what your source export includes before choosing a route; Freshdesk notes that its standard ticket export omits full conversations and archived ticket history.
What if a few records or files are missing?
Start with the import report, then compare the affected source records with the new ones. FyneDesk lists skipped attachments over 25 MB in its report. Fix failed rows using the same import job where possible, and check the current import guide before starting a new ticket import because a new CSV ticket job can create duplicates.
How do I know private notes stayed private?
Check a pilot ticket that contains both a public reply and an internal note. Compare their order, author, and visibility in the new system before importing the rest. If the importer does not show how it maps visibility, ask the destination team before moving sensitive history.
Should I cancel my old help desk immediately after importing?
No. Keep it available in read only form until record counts, sample tickets, new ticket routing, and retention requirements have been verified. The right archive period depends on your contract and data retention policy.
Does FyneDesk charge for migration support?
Import and migration support are included on every FyneDesk plan, including Free. You can use the import tools yourself or contact the team for help planning and testing the move.
Start with a pilot
Bring a small sample first. Switch when it feels right.
Create a free FyneDesk workspace and test your mapping without changing the support flow your customers use today.
About this guide: Written by the FyneDesk team. FyneDesk import details were checked against the current import guide on October 7, 2026. Export options can vary by vendor plan and account, so confirm the current details with your provider before you move a large or regulated archive. For help planning a FyneDesk import, email support@fynedesk.io.