How To · July 15, 2026

Help Desk Migration Checklist

Move without losing the ticket history, customer context, and working habits your support team depends on.

The safest migration is not one giant import. First identify what matters, then map it, test a representative sample, move the rest, and verify the result before closing the old system. A clean cutover protects both historical data and the next request that arrives.

Before the checklist

Why help desk migrations go wrong

Most failures are not caused by the file transfer itself. They happen because the old and new systems organize support differently. A status called Pending may mean waiting for a customer in one tool and waiting for an internal team in another. A contact may be matched by email in one system but tied to a company record in another.

The other risk is operational. Email forwarding, web forms, automations, and integrations can keep sending new requests into the old workspace after the historical data has moved. A strong migration plan handles the data model and the live support flow as separate jobs.

Preserve context

A ticket without its dates, requester, ownership, and replies is only a subject line.

Test the mapping

A small pilot reveals mistakes before they affect the full history.

Control the cutover

Choose when new requests stop entering the old system and start entering the new one.

The migration plan

Seven stages from inventory to signoff

Work in order. Each stage reduces a different kind of risk.

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.
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.

Choose the right import path

Use a direct connector when history matters. Use CSV when portability matters.

Choose a direct importer when it can preserve threaded conversations, attachments, agent links, and source specific metadata.
Choose CSV when your current tool can export clean tables or when you only need the essential records.
Confirm the destination can map every required field before scheduling the move.

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.

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.
Document every value that is renamed, combined, skipped, or moved into notes.

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 records with attachments, long reply threads, custom fields, and unusual characters.
Ask an agent who knows the old system to compare the same records side by side.

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.

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.

The FyneDesk path

Test the move before you switch

FyneDesk includes import and migration support on every plan, including Free. You can create a workspace, test a small import, review the result, and adjust the mapping 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.

Read the import guide Ask about your migration

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

Do not judge a pilot by the success banner alone. Open the records and test how agents will actually use them.

Area	What good looks like
Ticket history	Created and resolved dates match the source. Reply order still makes sense.
Ownership	Active agents are linked correctly. Former agents remain visible in historical records.
Customers	Contacts are matched by the intended email. Companies are not duplicated.
Attachments	A sample of common file types opens and belongs to the correct ticket.
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, and permissions work for a real test request.

Cutover day

Move the live support flow in a controlled order

1
Finish the final export.
Record the export time so everyone knows where the old history ends.
2
Start the final import.
Watch progress and resolve blocking errors before changing customer entry points.
3
Switch inbound routes.
Update email forwarding, forms, portal links, and integrations so new requests land in one place.
4
Send real tests.
Submit a request through every active channel and confirm assignment, notification, reply, and resolution.
5
Make 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 CSV preserve complete ticket conversations and attachments?

Not through the standard flat ticket file. The FyneDesk CSV importer treats each ticket as one row, so it does not recreate a full conversation thread or ticket attachments. FyneDesk direct importers can bring conversations and attachments across.

What happens when some rows fail?

Valid rows can still finish. FyneDesk reports failed rows with a reason and provides an error report. Correct those rows and run them again instead of repeating the entire migration.

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.

Create a free workspace Review supported imports

About this guide: Written by the FyneDesk team from the migration workflow shipped in FyneDesk and the practical checks support teams should complete before a cutover. Product capabilities were verified against the FyneDesk application on July 15, 2026. If something has changed, email support@fynedesk.io.