
FreshserviceHaloITSM
Freshservice to HaloITSM migration
ITSM specialists move your incidents, service requests and problems into HaloITSM, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 14 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Freshservice to HaloITSM at a glance
A Freshservice to HaloITSM migration turns tickets, problems, changes and service requests into Halo tickets, and each reply or private note into an action. Halo documents no Freshservice importer, so the move runs on both APIs, paced by Halo's limit of 700 requests in any five minutes. Freshservice stays live until the final delta sync.
- Objects mapped
- 14
- in this route's mapping
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
- Who it is for
- IT teams on Freshservice that want Halo's configurable ticket types, workflows and client structure, or that Halo's all-inclusive per-agent licence suits.
- What does not move
- Workflows, ticket rules, SLAs and service catalog forms are configuration. We list each Freshservice rule for your Halo admin to rebuild as a workflow, ticket rule or ticket type form.
- What sets the scope
- Ticket and conversation volume (Halo's request window sets the number of days), attachment count, workspaces, and how departments and locations become clients and sites.
What moves
What moves from Freshservice to HaloITSM
Tickets, problems, changes and service requests become Halo tickets of the matching ticket type, replies and public notes become actions visible to the user, and private notes become actions hidden from the user.
- 14 included
| Freshservice | maps to | HaloITSM | Status |
|---|---|---|---|
| Incidents | Tickets, incident ticket typeThe ticket type is chosen for each record, and its field list decides which custom fields are filled. | Included | |
| Service requests | Tickets, service request ticket typeAnswers given on the catalog form go into custom fields on that ticket type. | Included | |
| Problems | Tickets, problem ticket typeHalo keeps every ITIL type in one ticket table, set by the ticket type. | Included | |
| Changes | Tickets, change ticket typeMapped to the change ticket type and its initial status. | Included | |
| Replies and public notes | Actions visible to the userPosted in order against the ticket, which must already exist. | Included | |
| Private notes | Actions with Hide from User setHidden from the self-service portal, so the user never sees them. | Included | |
| Attachments | Attachments, posted as Base64Attached to the ticket, or to the action where they sat. | Included | |
| Departments | ClientsOur default for an internal IT desk. A Freshservice for MSPs account maps its clients to Halo clients instead. | Included | |
| Locations | Sites under a clientEvery user needs a client and a site, so requesters with no location get a default site. | Included | |
| Requesters | UsersCreated with their client and site before any ticket. | Included | |
| Agents | AgentsMatched by email. Agents need a Halo licence to log in. | Included | |
| Agent groups | TeamsTeam members are the matched agents. | Included | |
| Assets and asset types | Assets and asset types in an asset groupEach asset needs an asset type, and each asset type sits in an asset group. | Included | |
| Solution categories, folders and articles | FAQ groups, FAQ lists and articlesFAQ lists need an article type and an FAQ group before the articles arrive. | Included |
- IncidentsTickets, incident ticket type
The ticket type is chosen for each record, and its field list decides which custom fields are filled.
- Service requestsTickets, service request ticket type
Answers given on the catalog form go into custom fields on that ticket type.
- ProblemsTickets, problem ticket type
Halo keeps every ITIL type in one ticket table, set by the ticket type.
- ChangesTickets, change ticket type
Mapped to the change ticket type and its initial status.
- Replies and public notesActions visible to the user
Posted in order against the ticket, which must already exist.
- Private notesActions with Hide from User set
Hidden from the self-service portal, so the user never sees them.
- AttachmentsAttachments, posted as Base64
Attached to the ticket, or to the action where they sat.
- DepartmentsClients
Our default for an internal IT desk. A Freshservice for MSPs account maps its clients to Halo clients instead.
- LocationsSites under a client
Every user needs a client and a site, so requesters with no location get a default site.
- RequestersUsers
Created with their client and site before any ticket.
- AgentsAgents
Matched by email. Agents need a Halo licence to log in.
- Agent groupsTeams
Team members are the matched agents.
- Assets and asset typesAssets and asset types in an asset group
Each asset needs an asset type, and each asset type sits in an asset group.
- Solution categories, folders and articlesFAQ groups, FAQ lists and articles
FAQ lists need an article type and an FAQ group before the articles arrive.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from Freshservice to HaloITSM as-is
Workflow Automator rules, business rules, SLA policies, catalog forms and portal customisation are configuration, so your Halo admin rebuilds them from the list we hand over.
- Ticket activitiesOn request
- In HaloITSM: Private action summaryHalo keeps its own audit log, so the Freshservice activity history can be kept as one hidden action.
- On request
- ReleasesOn request
- In HaloITSM: Tickets with a release ticket typeThe ticket type is created first.
- On request
- WorkspacesOn request
- In HaloITSM: Clients or ticket type setsHalo has no workspace object, so the split is agreed on the scoping call.
- On request
- Asset relationshipsOn request
- In HaloITSM: Asset linksLoaded after both assets exist. Each asset needs an asset type in an asset group.
- On request
- Workflow Automator and business rulesNot migrated
- In HaloITSM: Workflows and ticket rulesConfiguration under Configuration > Tickets, rebuilt by your Halo admin from the list we hand over.
- Not migrated
- SLA policies and business hoursNot migrated
- In HaloITSM: SLAs and workdaysRebuilt in Halo and applied by site or ticket type.
- Not migrated
- Service catalog item formsNot migrated
- In HaloITSM: Ticket type field lists and formsForms are rebuilt per ticket type. Past answers move as custom field values.
- Not migrated
- Portal customisation and email templatesNot migrated
- In HaloITSM: Halo portal and email settingsSet up again in Halo.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Freshservice to HaloITSM migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayWe agree how departments and locations become clients and sites, what happens to workspaces, and which ticket type each Freshservice record gets.
Connect Freshservice and Halo
You0.5 dayYou share a Freshservice API key from an admin account and create a Halo API application under Configuration > Integrations > Halo API with an agent to impersonate.
Ticket types, statuses and fields
Both1 dayYour Halo admin creates the ticket types, statuses and custom fields we agreed. Ticket rules and SLA hold reminders are switched off for the load.
Migration
Day 3-7
Free sample
MigrateX1 day100 of your records, chosen for the longest threads, the most private notes and a problem and a change, loaded into Halo end to end. We test whether a past date and author are kept.
You review the sample
You1 dayYour team opens the tickets as an agent and as an end user in the portal, and checks hidden actions, dates, clients and sites.
Full load
MigrateX2-3 daysClients, sites, users, agents and teams first, then tickets, actions and attachments in batches inside Halo's five-minute window, over as many days as the volume needs.
Delta sync
MigrateX0.5 dayTickets changed in Freshservice since the full load are updated in Halo by their ids, so nothing is created twice.
Validation
Day 8-10
Reconciliation report
MigrateX1 dayTickets against tickets per workspace and year, conversations against actions, attachments against files, assets against assets.
Sign-off and rules back on
You1-2 daysYour leads check a random sample, ticket rules and reminders are switched back on, and Freshservice stays read-only until you agree.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
Every known risk on this route, with how we handle it
- 3 solved
- 4 handled
- 01SolvedMost critical
Halo's five-minute window, not Freshservice's read limit, sets the pace
The problem
Every ticket, action and Base64 attachment is a separate write inside Halo's tenant-wide window of 700 requests, while Freshservice on Pro reads at up to 400 calls a minute. Reading is the fast end of this route and writing the slow one.
How we handle it
Tickets and actions are posted as arrays with bulkresponse=true, so every result is visible, and the load is spread across days for a large account. We stay inside the limit, because Halo's fair use policy treats working around it as prohibited use.
Source: Halo guides, checked 15 Nov 2026
- 02HandledMost critical
Halo does not document keeping a past date or another author
The problem
Halo's API models carry a logged date on tickets and a date and agent on actions, but no Halo page says a past date or a different author is kept when a record is created. A migrated ticket could show the day it was loaded.
How we handle it
Both are tried on the free sample before the full run. If Halo keeps them, they are used. If it does not, the original date and author go at the top of each action and into custom fields on the ticket.
Source: Halo API documentation, checked 15 Nov 2026
- 03Solved
A spreadsheet import cannot be corrected or topped up afterwards
The problem
Halo's spreadsheet imports for tickets and actions cannot update what they have loaded, and the actions they create are labelled Imported Notes. A re-run or a delta pass that goes through a spreadsheet creates duplicates.
How we handle it
Tickets and actions are loaded through the API, which updates a record when an id is given. Spreadsheets are used only for reference data such as clients and sites, if you prefer that.
Source: Halo guides, checked 15 Nov 2026
- 04Handled
Freshservice departments and locations do not form a client tree by themselves
The problem
Every Halo user sits under a client and a site. A Freshservice requester may have a department but no location, or neither.
How we handle it
Each Freshservice department becomes a Halo client and each location a site under it, agreed on the scoping call, with a default site for requesters who have no location. A Freshservice for MSPs account, where each workspace is called a Client, maps client to client instead.
Source: Halo guides, checked 15 Nov 2026
- 05Handled
Halo rules and emails can fire on tickets that are history
The problem
Halo ticket rules update new tickets when conditions match, users can have acknowledgement emails when a ticket is logged, and SLA hold reminders can email and close tickets that sit on hold. A loaded backlog can trigger all three.
How we handle it
Reminders and rules are switched off per ticket type, SLA or status for the load. Flags in the API that look like suppression switches, such as dont_do_rules and sendack, are undocumented, so each is tested on the sample before it is relied on.
Source: Halo guides, checked 15 Nov 2026
- 06Solved
A Freshservice export can miss workspaces, old tickets and archived tickets
The problem
By default the Freshservice ticket list covers the last 30 days of the primary workspace only. On large accounts archived tickets come back one at a time by ID, and activity history arrives 20 entries a page.
How we handle it
The export walks every workspace and date window, fetches archived IDs individually, and reads activities page by page. Counts per workspace and year are checked against Freshservice before Halo is touched.
Source: Freshservice API documentation, checked 15 Nov 2026
- 07Handled
Every file is a Base64 upload to Halo
The problem
Halo takes attachments as Base64 text posted to its Attachment endpoint, and each one counts against the same five-minute allowance as tickets and actions, so a desk with years of screenshots spends much of its request budget on files. Halo's guides state no attachment size limit.
How we handle it
Attachments are counted during export and uploaded last, after tickets and actions, so a file backlog never delays the conversations. The file size limit of your tenant is confirmed during your free sample.
Source: Halo API documentation, checked 15 Nov 2026
Technical profile
What makes this route technical
Freshservice is read through paged API calls that default to 30 days and the primary workspace, and Halo is written inside its limit of 700 requests per tenant in any five minutes.
- Exporting from Freshservice: 30 records a page, 100 at most
- Freshservice list endpoints return 30 records a page by default and 100 at most, and a larger page size returns an error.
Source: Freshservice API documentation, checked 15 Nov 2026
- Exporting from Freshservice: only the primary workspace is listed
- Freshservice's List All Tickets endpoint reads only the primary workspace unless workspace_id is passed, and workspace_id=0 returns tickets from every workspace with their global fields only.
Source: Freshservice API documentation, checked 15 Nov 2026
- Exporting from Freshservice: who did what comes 20 activities at a time
- A Freshservice ticket's history of who did what is read from its activities endpoint, which returns the recent 20 activities and continues through a next_page_url token.
Source: Freshservice API documentation, checked 15 Nov 2026
- Exporting from Freshservice: archived tickets come back one at a time
- Freshservice archives closed, inactive tickets on accounts with at least 500,000 tickets, after one year of inactivity by default, and an archived ticket is read individually through its own ticket ID.
Source: Freshservice support documentation, checked 15 Nov 2026
- Exporting from Freshservice: 400 calls a minute on Pro
- Freshservice allows 100 API calls a minute on Starter, 200 on Growth, 400 on Pro and 500 on Enterprise, counted across the whole account, and answers HTTP 429 with a Retry-After header when the allowance is used up.
Source: Freshservice API documentation, checked 15 Nov 2026
- Importing into HaloITSM: 700 requests in any five minutes
- The HaloITSM API allows 700 requests per tenant over a rolling 300-second window, and going over returns HTTP 429.
Source: Halo API documentation, checked 15 Nov 2026
- Importing into HaloITSM: working around the limit is prohibited use
- Halo's fair use policy lists intentionally circumventing the rate limit as prohibited use, with possible suspension or extra charges.
Source: Halo guides, checked 15 Nov 2026
- Importing into HaloITSM: an action needs its ticket to exist
- POST /Actions adds or updates HaloITSM actions in one call, and ticket_id is mandatory, so a ticket must exist before any of its actions is written.
Source: Halo API documentation, checked 15 Nov 2026
- Importing into HaloITSM: a batch reports only its first result by default
- POST /Tickets returns the result of only the first object unless bulkresponse=true is passed, which returns a status for every ticket posted.
Source: Halo API documentation, checked 15 Nov 2026
- Importing into HaloITSM: no Freshservice migration module listed
- Halo's guide to importing and migrating data points to built-in modules under Configuration > Migrations for platforms such as Autotask, ServiceNow and Freshdesk, and a search of Halo's guides on 15 Nov 2026 returned no Freshservice module.
Source: Halo guides, checked 15 Nov 2026
- Importing into HaloITSM: every user sits under a client's site
- In HaloITSM a site is a location under a client, and the users of that client are split into its sites.
Source: Halo guides, checked 15 Nov 2026
- HaloITSM is now sold as Halo
- Halo's own site presents one platform called Halo, priced per agent with no feature tiers and no separate editions, while its guides still use the HaloITSM name.
Source: Halo website, checked 15 Nov 2026
Facts checked 15 Nov 2026 against Freshservice and Halo documentation. Each fact links its source.
Freshservice to HaloITSM questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
Can we migrate from Freshservice to HaloITSM and keep the full conversation on each ticket?
Yes. Every Freshservice reply and note arrives as an action on its Halo ticket, in order, because the export reads each thread through its own conversations endpoint rather than the ten conversations a ticket read returns.
Do Freshservice private notes stay hidden from users in Halo?
Yes. Freshservice private notes become Halo actions with Hide from User set, which keeps them out of the self-service portal. You open the free sample in the portal as an end user before the full load to confirm it.
How long will the load take with Halo's API limit?
Longer than the Freshservice export, because every ticket, action and file is a request inside Halo's 700 per five minutes. A large account is spread over several days, and the free sample gives a measured pace for your volume.
Will original ticket dates show in HaloITSM?
That is proven on the free sample, not assumed, because no Halo page says a past date is kept on create. If HaloITSM keeps it, it is used. If not, the original Freshservice date goes into a custom field and the first line of each action.
Does Halo have its own Freshservice importer?
Not one that Halo documents. Halo's built-in migration modules cover platforms such as Autotask, ServiceNow and Freshdesk, and Halo's guides list none for Freshservice, so this route runs on the Freshservice and Halo APIs.
How do Freshservice departments and locations become Halo clients and sites?
Each Freshservice department becomes a Halo client and each location a site under it, on a tree agreed on the scoping call. Halo needs a client and a site for every user, so requesters with no location get a default site.
Do problems, changes and service requests keep their type in Halo?
Yes. HaloITSM keeps incidents, problems, changes and service requests as tickets told apart by ticket type, each with an ITIL type set against it. A ticket type is chosen or created for each Freshservice record type before the sample.
Will users get acknowledgement emails while history loads?
Not if those settings are off for the load. Acknowledgement emails, ticket rules and SLA hold reminders are switched off per ticket type, SLA or status, and the free sample shows that no message went out.
Do Freshservice assets and the knowledge base move too?
Yes. Freshservice assets move with their asset types into Halo asset groups, with relationships as asset links on request. Solution categories, folders and articles become FAQ groups, FAQ lists and articles.
What does a Freshservice to HaloITSM migration cost?
The price is set by what moves: tickets and the conversations and attachments on them, workspaces, assets and articles, and how many clients and sites Halo needs. You get a fixed quote within 24 hours of the scoping call, after a free sample migration of 100 of your records.
How it compares
Four ways to run Freshservice to HaloITSM
The same data, moved four different ways. This is what changes between them.
Object coverage (incidents, problems, changes, requests, KB)
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Tickets and contacts are covered. Problems, changes and request items often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Work notes vs comments fidelity
MigrateX
Each entry is posted separately, private stays private, public stays public.
Automated migration software
Threads usually arrive, but per-entry author and visibility can be flattened.
Vendor CSV import
Notes collapse into one field on the ticket, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Attachments
MigrateX
Uploaded against the right note, and re-hosted with a link when they exceed the HaloITSM cap.
Automated migration software
Supported up to the destination cap. Oversize files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. Support answers tickets.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Guides
Guides for a Freshservice to HaloITSM migration
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your HaloITSM move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.


