Migration guides

Freshservice to HaloITSM Migration: Tickets, Assets and SLAs Mapped

Freshservice to HaloITSM migration: how tickets map to Halo ticket types, assets to asset types and SLA policies to Halo SLAs, and what to check first.

Ayush BothraFounding Member, MigrateX

Published 7 min read

Geometric blocks moving from a loose pile under the Freshservice logo to an ordered stack under the HaloITSM logo, for a Freshservice to HaloITSM migration
On this page

In a Freshservice to HaloITSM migration, incidents, service requests, problems and changes become Halo tickets by ticket type, assets load under Halo asset types, and SLA policies are rebuilt as Halo SLAs by site or ticket type. Halo does not document how it treats original dates and authors on API-created records, so that is confirmed on a free sample.

This guide is for IT service owners who have chosen HaloITSM, which Halo now sells as one platform called Halo, and want the three mappings that decide how usable the history is. Rate limits, the full object list and the risks are on the Freshservice to HaloITSM migration page.

How do tickets map in a Freshservice to HaloITSM migration?

One Halo ticket type per Freshservice record type. Freshservice keeps incidents, service requests, problems and changes as different records. HaloITSM keeps them all as tickets, and Halo's guide to ticket types says a ticket type categorises tickets and sets their ITIL type.

How each Freshservice record is read and what its Halo ticket type needs:

Freshservice recordHow it is readWhat the Halo ticket type needs
IncidentTickets API, which supports only the incident type as of November 2026Incident ITIL type, your custom fields on its field list
Service requestIts own endpoints; item fields sit with the requested itemService request ITIL type, one custom field per catalog answer you keep
ProblemIts own moduleProblem ITIL type
ChangeIts own moduleChange ITIL type and an initial status

Three settings on each Halo ticket type are set before anything loads:

  1. Field list. Halo's guide says the Field List tab "is where fields can be added to the ticket type - both custom and system". A Freshservice custom field has to be added to every ticket type that should carry it.
  2. Initial status. The ticket type sets the status a ticket opens with. History that arrives closed needs its real final status, so the status map is agreed first.
  3. Workflow start. The ticket type also decides "whether the ticket should automatically start a workflow or approval process". A change approved two years ago should not ask for approval again.

One detail catches teams out. Freshservice's help article on exporting tickets says service request item fields "are stored with the requested item rather than the ticket" and "are not included in standard ticket exports". The answers an employee gave on a catalog form have to be read from the requested item, or they are lost.

How do Freshservice assets land in HaloITSM?

Each Freshservice asset becomes a Halo asset, but only after its asset type exists. Halo's guide to asset types says "each asset will need to be assigned an asset type, and each asset type will sit within an asset group". Asset types have their own field lists, as ticket types do.

That gives a fixed build order:

  1. Asset groups. The top layer, agreed with you.
  2. Asset types. One per Freshservice asset type you keep, each with the fields it needs.
  3. Assets. Loaded into their type, with the client and site they belong to.
  4. Links. Freshservice relationships connect assets to other assets, agents and requesters, each with a relationship type. They load last, after both ends exist.

Reading assets has its own pace. Freshservice's API documentation gives the List All Assets call a lower limit than the account's overall one: 40 calls a minute on Starter, 70 on Growth, 120 on Pro and 140 on Enterprise.

What happens to Freshservice SLA policies in HaloITSM?

They are rebuilt, not migrated. SLA policies are configuration in both platforms. Halo's SLA guide says "SLAs can be applied to a particular site or ticket type", with response and resolution targets for each priority, so the rebuild starts with a choice Freshservice never asked you to make: by site, or by ticket type.

The decisions an SLA rebuild asks of you:

In FreshserviceIn HaloITSMDecision for you
SLA policySLA, applied to a site or a ticket typeWhich of the two fits how your desk is organised
Priorities: Low, Medium, High, UrgentResponse and resolution targets per priorityWhether the four levels map one to one
Business hoursWorkdaysWhich calendar each SLA uses
Pending statusA status that puts the ticket on holdWhich Halo statuses pause the clock

The last row matters most for agents. Halo's introduction guide says the default "With User" status "puts the ticket on hold so the SLA timer pauses". If Freshservice's Pending maps to a Halo status that does not hold, the SLA clock keeps running on every waiting ticket.

Halo's SLA guide also says SLA hold reminders can send automated emails and close on-hold tickets, and can be switched off per ticket type, per SLA or per status. They stay off while history loads.

What should you check on the HaloITSM sample?

Check the three mappings and one open question: dates and authors. Halo's API documentation shows a logged date on tickets and a date and agent on actions in its example models, but no Halo page says a past date or a different author is kept on creation. If the sample shows Halo keeps them, they are set directly. If not, both go into custom fields and the first line of each action.

Ask for a sample with an incident, a service request with catalog answers, a change, an asset with a relationship, and a ticket that sat in Pending. Then check:

  1. Each record opened as the right ticket type, with the right ITIL type.
  2. Custom field values are present, including a service request's catalog answers.
  3. No workflow or approval started on a ticket that was already closed.
  4. The asset sits under the expected asset type and group, with its link to another asset or a user.
  5. A ticket that was Pending is in a Halo status that holds the SLA.
  6. The date and author on the ticket and on each action: original, or import day.
  7. No acknowledgement email or hold reminder went out.

Scope for both sides is on the Freshservice and HaloITSM platform pages.

Facts checked November 15, 2026 from Freshservice: Service Desk API for Developers, Freshservice: Exporting tickets, Freshservice pricing, Halo guide: Altering Ticket Types, Halo guide: Service Level Agreements (SLAs), Halo guide: Asset Types/Groups, Halo guide: Introduction to HaloITSM/ESM, Halo guide: Importing Data, Halo API Documentation and Halo pricing. No vendor paid for this article. How we research

Freshservice to HaloITSM migration FAQ

Does HaloITSM charge extra for API access during a migration?

Halo's pricing page says no. It states that Halo "is priced per agent, with every feature, module and integration included in that one price", with no feature tiers or separate editions. So there is no higher plan to buy for API access, as of November 2026. Confirm your own contract terms with Halo.

Can Halo's spreadsheet import load our SLAs?

Halo's SLA guide lists creating SLAs from an XLS import as an option, so the definitions can be loaded from a sheet instead of typed in. You still decide whether each SLA applies to a site or a ticket type, and which workdays and priorities it uses. Tickets and their history go through the API.

Do migrated closed tickets start SLA timers in HaloITSM?

Halo does not say. No Halo guide or API page we read states whether a closed ticket created through the API starts an SLA timer. The sample answers it in your own instance before the full load is scheduled. If you report on past SLA results, the original Freshservice resolution times are kept in custom fields.

Can asset records be corrected in Halo after they load?

Yes, more easily than tickets. Halo's Importing Data guide says its imports can update existing records when a unique identifier is set, except for tickets, actions, contracts and knowledge base articles. The identifier "must be a perfect match", or duplicates appear, so one identifier per asset is agreed before the first load.

Do problems, changes and SLA policies exist on every Freshservice plan?

No. Freshservice's pricing page lists service catalog and SLA management from the Growth plan, and problem, change and release management from the Pro plan. An account on Starter or Growth has no problems or changes to move, which makes the ticket type list in Halo shorter.

See your Freshservice tickets, assets and SLAs in Halo first

MigrateX is an AI migration platform, SOC 2 Type II, GDPR and HIPAA compliant, with ITSM engineers reviewing each step. Send us your Freshservice record counts by type and how many assets you track. You get 100 of your records in HaloITSM, free, and a fixed quote within 24 hours. Book a scoping call. Coming from Freshdesk before that? Read Freshdesk to Freshservice: keep your IT ticket history, or see the reverse route, HaloITSM to Freshservice.

Written by

Ayush Bothra

Founding Member, MigrateX

Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.