Freshdesk to Freshservice: when customer support and IT should split
Short answer
Freshdesk is Freshworks’ customer support help desk; Freshservice is its IT service management product. Many companies start with one Freshdesk account for everything, then find IT tickets mixed with customer tickets, no problem or change records, and no asset register. Split when IT needs ITSM processes, not just a queue: a service catalogue, change approvals, problem records or a CMDB. Do not split if IT is two people answering password resets. Freshworks documents a native Freshdesk–Freshservice integration: Freshdesk agents can create Freshservice incidents or service requests from a customer ticket, Freshdesk automation rules can raise incidents automatically, and each side controls how much of the other’s conversation it can see. It links new work; it does not move history. History moves through Freshdesk’s exports and Freshservice’s partner bulk API, with assets loaded by CSV. On price, official list prices checked Nov 10, 2026 put Freshdesk Pro at $55 / £39 and Freshservice Growth at $49 / £40 per agent per month billed annually, so moving IT agents to Freshservice Growth is roughly cost-neutral; Freshservice Pro is $99 / £79.
Contents
- Who this guide is for
- Same vendor, different products
- When IT should split from customer support
- How the native Freshdesk–Freshservice integration works
- Running both products: an operating model that works
- What migrates, and how
- Clean up before you split
- What it costs: Freshdesk vs Freshservice list prices
- A four-to-six-week plan
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for companies where the internal IT team works inside Freshdesk, usually because Freshdesk arrived first for customer support and IT borrowed a group in it. It is also for IT leads running a dedicated Freshdesk account for employees who now wonder whether Freshservice is worth the change. If your IT team is on Zendesk rather than Freshdesk, the same questions are covered in our Zendesk vs Freshservice for internal IT and Zendesk to Freshservice migration guides.
We rely on Freshworks’ own pages, checked on Nov 10, 2026: the Freshdesk pricing page, the Freshservice pricing page, the Freshdesk article introducing the Freshdesk–Freshservice integration, the Freshdesk admin setup article for the integration, the Freshservice article on the Freshdesk integration, the Freshdesk FAQ on raising tickets from Freshservice, the Freshdesk ticket export article, the Freshdesk account export article, the Freshservice bulk migration API guide for data migration partners and the Freshservice “Importing Assets” article. The judgement calls about when to split are ours.
Same vendor, different products
It is easy to assume Freshdesk and Freshservice are two editions of one product. They are not. They share a vendor, a look and some platform pieces, but they are built for different requesters and different work.
| Freshdesk | Freshservice | |
|---|---|---|
| Built for | Customers contacting a company | Employees contacting IT (and other internal teams) |
| Core record | Ticket | Ticket (incident or service request), plus problem, change and release on Pro |
| Request intake | Email, customer portal and knowledge base, with further channels depending on edition | Email, portal, chat, widget, and ServiceBot on Microsoft Teams and Slack on every plan |
| Catalogue | No IT service catalogue | Service catalogue from Growth |
| Assets | No IT asset register | IT asset management and CMDB, licensed in Asset Units |
| ITIL processes | Not modelled | Problem, change, release and major incident management on Pro and Enterprise |
| Pricing unit | Per agent | Per agent |
The practical consequence: an IT team can run in Freshdesk for a long time if all it does is answer questions. The moment it needs to approve changes, track laptops against users or run a request catalogue with approvals, Freshdesk becomes a set of workarounds with custom fields and tags.
When IT should split from customer support
These are the signals we look for. Two or more usually means it is time.
| Signal | Why it matters |
|---|---|
| IT tickets and customer tickets share one account and one SLA set | Customer SLAs and reports are distorted by internal work, and internal tickets compete with customers for attention |
| IT needs a request catalogue with approvals (access, hardware, software) | Freshservice’s service catalogue starts on Growth; recreating it with Freshdesk forms is fragile |
| Auditors or security ask for change records | Change management with CAB and change calendars is on Freshservice Pro |
| You keep a spreadsheet of laptops and licences | Freshservice holds assets and links them to requesters and tickets |
| Repeated incidents never get a root cause | Problem management is on Freshservice Pro |
| Employees want to raise requests from Teams or Slack | ServiceBot on Microsoft Teams and Slack is on every Freshservice plan |
| Customer support needs IT or engineering help on customer issues | The native integration links the two products without merging them |
When not to split
If IT is one or two people, handles a few dozen tickets a week, and has no need for approvals, change records or an asset register, a separate product is overhead. Keep IT as its own group in Freshdesk with its own SLA policy and reports, and revisit when the signals above appear. Our shared inbox to first ITSM tool guide covers that earlier stage.
How the native Freshdesk–Freshservice integration works
Splitting does not mean the two teams stop working together. Freshworks documents an out-of-the-box integration for exactly the case where a customer issue needs an internal team.
- Setup is by an admin on either side: in Freshdesk, Admin, then Support Operations, then Freshservice, using the Freshservice domain and API key. The same is done from Freshservice to link back.
- From a Freshdesk ticket, agents use Threads to create an incident or create a service request in Freshservice. The form is pre-filled from the ticket; service requests use the publicly displayed catalogue items.
- Freshdesk admins can set automation rules that raise Freshservice incidents automatically, for example when the subject contains “Outage”.
- Visibility is configurable: Freshdesk agents can see all conversations on the Freshservice ticket or only public ones; Freshservice agents can see all, public only, or none (ticket properties only) of the Freshdesk conversation.
- In Freshservice, tickets from Freshdesk carry Freshdesk as the source, so admins can build SLA policies, reports and Workflow Automator rules for that source.
- It is one-directional for ticket creation: Freshworks says Freshservice agents cannot raise Freshdesk tickets through this integration.
That last point shapes the design. Customer support stays the owner of the customer conversation; IT works the internal incident; status and notes flow back through the thread. If IT needs to open customer-facing tickets, that is a process question, not something the integration does.
What the integration does not do
It links new work between the two products. It does not move historical tickets, requesters or knowledge from Freshdesk into Freshservice. That is a separate migration.
Running both products: an operating model that works
Once IT is on Freshservice and customer support stays on Freshdesk, most friction is about ownership, not tools. These are the rules we write down with both teams before go-live.
| Question | Our default answer |
|---|---|
| Who owns the customer? | Customer support, always. The Freshdesk ticket stays open until the customer is answered, even if IT resolved the root cause |
| When does support raise an IT incident? | When the cause is internal (an outage, an access problem, a bug in an internal system) and support cannot resolve it. Use an automation rule for clear patterns such as “Outage” |
| What SLA applies? | A separate Freshservice SLA policy for tickets with Freshdesk as the source, shorter than internal requests if customers are waiting |
| What can each side see? | Support sees IT’s public notes by default; IT sees customer conversations only where needed. Start restrictive and open up if it slows resolution |
| Who reports on it? | IT reports on Freshdesk-sourced tickets in Freshservice analytics; support reports on time waiting for IT in Freshdesk |
| What about employees who email the support address? | Redirect them to the IT portal or Teams/Slack bot; do not let internal requests drift back into Freshdesk |
Two habits keep this healthy. First, review the Freshdesk-sourced incidents monthly: if the same cause appears repeatedly, open a Freshservice problem (on Pro) or fix it in the product. Second, keep the integration rule list short. Every automation rule that raises incidents automatically is a source of noise for IT if it is too broad.
What migrates, and how
We did not find a documented self-service tool in Freshworks’ help articles that copies Freshdesk history into Freshservice. Ask Freshworks support what they can offer for your account; otherwise the route is export from Freshdesk, then import into Freshservice through APIs, usually with a migration partner.
Out of Freshdesk
Freshworks documents two exports. The ticket export (Tickets, All tickets, filter, Export) gives CSV or Excel with the fields you choose, including the description and other multi-line fields, but Freshworks says it does not include the full conversation or archived tickets. For conversations and archived history, an Account Admin runs the account export from Admin, Account, Account Details, Export data, which delivers tickets, solutions, forums and customers as XML. Developers then convert that XML for loading. Many migration partners instead read directly from the Freshdesk API, which avoids XML parsing and lets you filter by group.
Into Freshservice
Freshservice’s partner bulk migration API creates tickets and notes with attachments, up to 50 per request and 10 requests per minute per account, with a 40 MB attachment limit per entity, and requires a migration token issued to data migration partners. Other records (requesters, departments, agents, groups, solution articles) go through the standard REST API. Freshworks warns that workflows, business rules and Slack or Teams notifications are not muted during migration, so pause them first. Assets do not exist in Freshdesk at all; build them by CSV import per asset type, following Freshworks’ Freshservice “Importing Assets” article.
| Freshdesk data | Freshservice destination | Notes |
|---|---|---|
| IT tickets (by IT group, type or tag) | Tickets, split into incidents and service requests | Agree a rule per Freshdesk ticket type; keep the original type and ID in custom fields |
| Ticket conversations and private notes | Ticket replies and private notes | From the account export or the API |
| Contacts (employees) | Requesters | Better: sync from your identity provider and match on email |
| Companies | Departments, if used for internal units | Often not needed for internal IT |
| Agents and groups | Agents and groups | Only the IT agents move; reassign roles in Freshservice |
| IT solution articles | Solution articles | Move only internal IT articles; leave customer-facing articles in Freshdesk |
| Canned responses, automations, SLA policies | Rebuilt | Configuration does not migrate; rebuild what is still used |
Scope is the main decision. Only IT tickets, IT requesters and IT articles move. Customer support history stays in Freshdesk and should not be touched. Filter by group, tag or requester email domain, and reconcile counts on both sides before cutover.
Clean up before you split
A split is the cheapest moment to fix years of shortcuts. Do these before loading anything into Freshservice:
Pre-split clean-up
- List every Freshdesk group, ticket type, tag and custom field used by IT, and count tickets against each. Retire the ones with no recent use
- Write the rule that decides whether a historical ticket is an incident or a service request, and keep the original Freshdesk type in a custom field
- Separate IT solution articles from customer-facing articles; check which internal articles are still accurate before moving them
- Identify employees who exist as Freshdesk contacts and decide whether they come from your identity provider instead
- Export the IT automations and SLA policies (screenshots are fine) so you can rebuild the ones that matter
- Agree the date after which new IT work must go to Freshservice, and tell employees how to reach IT
Teams that skip this step usually migrate clutter: dozens of tags nobody filters on and categories that only made sense in a customer support tool.
What it costs: Freshdesk vs Freshservice list prices
Official USD and GBP list prices from the Freshdesk pricing page and the Freshservice pricing page, checked Nov 10, 2026, per agent per month.
| Plan | Billed annually | Billed monthly |
|---|---|---|
| Freshdesk Growth | $19 / £15 | $23 / £18 |
| Freshdesk Pro | $55 / £39 | $66 / £47 |
| Freshdesk Enterprise | $89 / £67 | $107 / £81 |
| Freshservice Starter | $19 / £15 | $29 / £25 |
| Freshservice Growth | $49 / £40 | $59 / £45 |
| Freshservice Pro | $99 / £79 | $119 / £95 |
| Freshservice Enterprise | Contact sales | Contact sales |
Worked example from list prices only, 10 IT agents billed annually: on Freshdesk Pro that is $6,600 / £4,680 a year; on Freshservice Growth $5,880 / £4,800; on Freshservice Pro $11,880 / £9,480. In USD, Growth is slightly cheaper than Freshdesk Pro; in GBP it is slightly dearer. Pro roughly doubles the cost, so only move to Pro if you will actually run problem and change. Freddy AI Copilot is listed at $29 per agent per month on both pricing pages in the annual view; Freshservice also shows an official £23 (billed annually) and $35 / £28 billed monthly. Asset Units for Freshservice’s CMDB are sold in packs of 500 with no unit price on the page, so get a quote if you have many assets.
There is a less visible saving too. Moving IT agents out of the customer support account reduces Freshdesk seats, and customer support reports stop including internal tickets. For the full Freshservice tier comparison, see our Freshservice pricing guide.
A four-to-six-week plan
| Week | Work |
|---|---|
| 1 | Decide scope: which groups, ticket types and articles are IT. Count them by year. Open a Freshservice trial (14 days) and set up SSO and requester sync |
| 2 | Configure Freshservice: groups, categories, SLA policies, a first service catalogue of the top ten requests, asset types |
| 3 | Link Freshdesk and Freshservice with the native integration; set visibility; add a Freshdesk automation rule for outages; test with customer support |
| 3 to 4 | Sample migration of IT history; agents work migrated tickets; then full load in date windows |
| 5 | Cutover: point the IT mailbox and portal links at Freshservice; remove IT groups from Freshdesk; delta load |
| 6 | Hypercare; reduce Freshdesk seats; retire IT-only automations and SLA policies in Freshdesk |
Keep the customer support team in the loop from week one. The integration only works if support agents know when to raise an incident and what they will see back.
Best for, and wrong choice when
Splitting to Freshservice is right when
IT needs a catalogue, approvals, assets, or change and problem records, or IT and customer support SLAs are getting in each other’s way. The native integration keeps the two teams connected.
Splitting is the wrong choice when
IT is very small and handles simple questions. A separate IT group and SLA policy inside Freshdesk is cheaper and simpler until the signals appear.
Look beyond Freshservice when
Engineering already lives in Jira and IT wants to link incidents to development work; compare Jira Service Management in our Freshservice vs JSM vs ServiceNow comparison.
Frequently asked questions
What is the difference between Freshdesk and Freshservice?
Freshdesk is Freshworks’ help desk for customer support. Freshservice is its IT service management product for employees, with incidents and service requests, a service catalogue, asset management and, on Pro, problem, change and release management.
Can Freshdesk and Freshservice work together?
Yes. Freshworks documents a native integration: Freshdesk agents create Freshservice incidents or service requests from a ticket through Threads, Freshdesk automation rules can raise incidents automatically, and both sides choose how much of the other’s conversation is visible.
Does the integration migrate old tickets?
No. It links new work between the two products. Historical IT tickets are exported from Freshdesk and imported into Freshservice separately.
Can Freshservice agents create Freshdesk tickets?
Not through the native integration. Freshworks’ FAQ says Freshservice agents cannot raise Freshdesk tickets using it.
How do I export Freshdesk tickets with conversations?
The ticket list export gives fields in CSV or Excel but not full conversations or archived tickets. An Account Admin can run the account export from Admin, Account, Account Details, Export data, which delivers tickets, solutions, forums and customers as XML.
Is Freshservice more expensive than Freshdesk?
At list price, Freshservice Growth ($49 / £40 per agent per month billed annually) is close to Freshdesk Pro ($55 / £39). Freshservice Pro is $99 / £79. Prices checked Nov 10, 2026 on Freshworks’ pricing pages.
Should all of IT history move to Freshservice?
Move open IT tickets and the history agents actually search, typically the last 12 to 24 months. Leave customer support history in Freshdesk and keep an export of the rest.
How long does a Freshdesk to Freshservice move take?
For a small to mid-sized IT team with a clear scope, four to six weeks is a realistic plan in our experience. Large histories, heavy automation or unclear ownership of tickets add time.