How Do You Migrate from Freshdesk to Freshservice? (2026 Steps)

To migrate from Freshdesk to Freshservice, pause Freshservice's notifications and automations, re-create your custom fields, move tickets, contacts, agents and knowledge base with a migration tool (a free Help Desk Migration demo tests 20 records first), build assets separately by CSV, then run a delta pass and cut over; Help Desk Migration puts the whole project at 1-2 weeks. Records move; SLA policies, automations and reports are rebuilt by hand.

Why do teams move from Freshdesk to Freshservice?

The trigger is almost always the same: a support team on Freshdesk starts fielding internal IT requests (laptop provisioning, access grants, software installs) and finds that a customer-support help desk has no native concept of the things those requests revolve around. There's no asset record for the laptop, no configuration item for the server, no change process for the deployment. Freshservice adds all of that. Its CMDB (configuration management database) stores assets and the relationships between them, so a ticket links to the exact device or service it concerns, and change management wraps risky work in approvals.

That's the gain worth migrating for. The cost is that Freshservice's richer object model doesn't fall out of a Freshdesk export: assets and CMDB items are built fresh in Freshservice, and your Freshdesk data has to be mapped into a structure it was never shaped for.

What migrates from Freshdesk to Freshservice, and what do you rebuild?

Help Desk Migration's Freshdesk to Freshservice page lists what its tool carries across: tickets, agents, contacts (as requesters), companies (as departments), attachments, internal notes, and knowledge base articles with their categories and folders. Its Freshservice migration checklist covers the prep. Here's the split between what ports and what you re-create.

The pattern: records travel, logic doesn't. Tickets, people and articles cross the gap; the SLAs, automations and reports that acted on them are re-created in the new system. Budget real time for that rebuild. It's usually the longest part of the project, not the data copy.

Step 1: How do you prepare Freshservice before importing?

The biggest cause of a messy migration is importing into a Freshservice instance that's still live and reacting. Help Desk Migration's checklist says to turn these off first:

1. Email notifications: Admin → General Settings → Email Notifications; disable every tab so migrated tickets don't email your requesters.
2. Automations: under Admin → Automations & Productivity, disable every Workflow Automator rule, and document then delete Scenario Automations, so nothing fires on imported records.
3. Priority Matrix: toggle it off (Admin → Service Management → Priority Matrix) so original ticket priorities are kept rather than recalculated.
4. Closure rules: deactivate them (Admin → Service Management → Service Desk Settings → Closure Rules) to stop unexpected status changes.
5. Parent-child ticketing: toggle off under Admin → Workflows to avoid failures on task-type tickets.

Then replicate your custom fields. Custom fields only migrate if a matching field already exists in Freshservice, so re-create each one (same type, same required flag, same dropdown options) before the import runs. Get this wrong and custom-field data silently lands nowhere.

Step 2: Should you use native CSV import or a migration tool?

There are two realistic paths, and they suit different data.

Freshservice's native CSV import is free and fine for simple objects: requesters, agents and especially assets, which don't come from Freshdesk at all and have to be built in Freshservice regardless. It's the right tool for standing up your CMDB. But it's manual and rule-bound. Per Freshservice's Importing Assets article, you can import one asset type per import, you create custom asset types and fields before importing, Display Name is the only required field by default, serial numbers must be unique, and an asset can't already sit in the inventory trash. CSV gives you no way to carry ticket conversations, history or the relationships between objects.

A paid migration tool like Help Desk Migration (Relokia) automates the ticket-and-history side. Its process: connect both platforms, map fields, run a free demo migration of 20 records, review the result, then run the full migration followed by a delta migration for records created or updated in Freshdesk since the full run. It doesn't publish a price on that page; the quote depends on record volume, complexity and options, and you get it by running the demo. The incentive is plain: the demo is the vendor's sales funnel, which suits you fine, because it's also your test.

A split that works: the paid tool for tickets, contacts, agents and the knowledge base; native CSV import for assets and the CMDB from your own inventory data.

Step 3: How do you map fields and test before committing?

Mapping is where a migration is won or lost. Because Freshservice renames and restructures things, decide explicitly how each Freshdesk value lands: statuses, priorities, ticket types and tags all need mapping, and custom fields need matching by name, type and options. Two mappings people forget: contacts becoming requesters and companies becoming departments. Check those relationships survived.

The safety net is the demo migration. Run it on a representative slice, then open Freshservice and verify ticket formats, timelines, requester and department links, custom fields, tags and attachments. If closed_at/solved_at dates matter for reporting, confirm your custom-field mapping captured them here, before you migrate tens of thousands of records with the same mistake baked in. If what you actually need is to move Freshdesk history to another support platform rather than ITSM, the sibling Freshdesk to Zendesk migration guide covers that path.

How long does the migration take, and what breaks?

Help Desk Migration gives a data migration timeline of 1-2 weeks covering preparation, migration and post-migration. No migration is truly zero-downtime: you keep Freshdesk answering live tickets, run the main copy, use a delta pass to sweep up anything that changed, then cut over with a short freeze or read-only window.

Be clear about what doesn't survive the trip:

• SLA policies: targets, reminders and escalations rebuild in Freshservice from scratch.
• Automations: every Freshdesk rule is re-authored in the Workflow Automator.
• Reports and dashboards: historical analytics are re-created against the migrated data.
• Resolution timestamps: they're lost unless you deliberately mapped them into custom fields.

None of this is a reason not to migrate. It's a reason to plan the migration as a rebuild project with a data copy inside it. The teams that get burned treated the copy as the whole job and found on go-live day that their SLAs and reports were blank.

Do you need Freshservice, or AI on the Freshdesk you already run?

Not every team on Freshdesk needs ITSM. If the driver is "our agents are drowning in repetitive tickets" rather than "we need asset and change management," a migration may solve the wrong problem. The answer might be automation on the help desk you already run, which we cover in how to automate Freshdesk with AI.

That's where Macha fits. Macha is an AI agent layer that runs on top of the Freshdesk you already use as a native connector. It isn't a help desk, isn't a Freshdesk replacement and isn't a reason to migrate. AI agents for customer service do the reasoning work (reading a ticket, drafting a grounded reply, looking up an order) that no amount of ITSM structure does for you, and it's worth understanding the build-versus-buy tradeoff before adding any of it. You connect Macha to Freshdesk with your subdomain and API key; it reads and writes the same tickets, drafting or posting grounded replies and checking account or order status through a custom tool that turns a REST API into something the agent can call.

One caveat, since this is a Freshservice post: Macha's connector is for Freshdesk, not Freshservice, Freshchat or Freshcaller. If your endgame is ITSM on Freshservice, Macha isn't the layer for that instance. Where it does apply, Macha bills per ticket (one conversation, charged once however many messages it takes), never per resolution, starting at $299 a month for up to 750 tickets with setup and monitoring included; the pricing page has every tier. Migrate to Freshservice when you need assets, CMDB and change management; automate on Freshdesk when you need faster tickets.

FAQ

What data migrates from Freshdesk to Freshservice? Tickets (with notes and history), attachments and inline images, contacts (which become requesters), companies (which become departments), agents, and the knowledge base (categories, folders and articles). Custom fields migrate only if you create matching fields in Freshservice first.

What does not migrate and has to be rebuilt? SLA policies, automations and workflows, and reports and dashboards are rebuilt by hand in Freshservice. closed_at/solved_at dates don't migrate by default, so map them into custom fields to keep resolution history.

How long does the migration take and is there downtime? Help Desk Migration puts a Freshdesk-to-Freshservice project at 1-2 weeks including preparation and post-migration checks. Freshdesk stays live during the main copy; a delta migration afterward catches records that changed, so the freeze at cutover is short.

Is there a free way to test the migration? Yes. Help Desk Migration's free demo moves 20 records so you can check mapping before paying, and it's also how you get a price quote.

Do my Freshdesk assets migrate into the Freshservice CMDB? No. Assets and CMDB items are new to Freshservice and built separately, usually via CSV import: one asset type per import, custom asset types and fields created first, Display Name required and serial numbers unique.

Can I add AI to Freshdesk instead of migrating? Yes. If the goal is handling repetitive tickets rather than IT asset management, an AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of it, with no migration. Macha connects to Freshdesk, not Freshservice.

Planning the migration but want your Freshdesk agents faster in the meantime? Start free with Macha ($50 of usage, no credit card) and connect it to your Freshdesk.