SysAid to Freshservice or Jira Service Management migration: what exports, what you rebuild, and a phased plan
Short answer
SysAid gives you two documented ways to get data out. The Spaces queue export writes the service records in your current view to CSV, with the visible columns only. The REST API covers service records, notes, activities, action items, related items, users and groups, categories, assets, CIs and knowledge base articles. It uses client-credential app keys and allows up to 1,000 requests per 5-minute window per account, and service record searches return at most 100 records per call (SysAid developer docs, checked Nov 11, 2026). For a real migration, use the API for history and relationships and the CSV export for reconciliation. Then pick the target. Freshservice is the closer match to how SysAid works: one ITIL data model with incidents, requests, problems, changes and assets. Pro, at $99 / £79 per agent per month billed annually, is where problem and change start. Jira Service Management fits better if engineering already works in Jira. Change management is a Premium feature there, at $55.28 per agent per month at Atlassian’s 75-agent default with monthly billing (about £41.24, indicative). SysAid’s workflows (action items), SLAs and automations do not migrate as configuration. You rebuild them, and that is where most of the effort goes.
Contents
- Who this guide is for
- Why teams move from SysAid, and when they should not
- How SysAid organises data
- Getting data out of SysAid
- Mapping SysAid to Freshservice and JSM
- Loading into Freshservice
- Loading into Jira Service Management
- What you rebuild: action items, SLAs and automation
- A phased plan
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for IT managers and SysAid administrators who have decided to leave SysAid, or are pricing the move, and have Freshservice or Jira Service Management on the shortlist. If you are still comparing tools on AI deflection and price, start with our SysAid vs Freshservice vs HaloITSM AI comparison, then come back here.
All facts about SysAid come from SysAid’s own documentation: the SysAid “Exporting Service Records” documentation, the SysAid API Standards & Conventions, the SysAid API Authentication Guide, the SysAid “Search Service Records” API reference and the SysAid developer API index. Destination facts come from Freshworks and Atlassian documentation and pricing pages. Everything was checked on Nov 11, 2026. Sequencing advice is our own, from service desk migrations, and is labelled as opinion.
What we will not claim
We did not find a native “import from SysAid” tool in Freshservice or Jira Service Management documentation, so we do not claim one. Third-party migration services exist; evaluate them on your own data. We also do not estimate how long your migration will take without seeing record counts and customisations.
Why teams move from SysAid, and when they should not
SysAid’s current pricing page lists one published tier, Professional, at $59 per agent per month billed annually, with request, incident, change and problem management, asset management and its AI Copilot included, plus a custom Enterprise tier from 20 agents. So the move is rarely about price alone. The reasons we hear most:
- Engineering moved to Jira and IT wants incidents and changes linked to the same work (points to JSM).
- The organisation standardised on Freshworks for customer support and wants IT on the same vendor (points to Freshservice).
- An acquisition brought a second ITSM tool and one has to go.
- Admins want a larger partner and talent market around the tool.
When not to move: if SysAid’s included AI agents are delivering deflection you rely on and the tool fits your processes, migrating for its own sake adds cost and risk. Compare AI capability like for like before deciding; the destination may need add-ons or a higher tier to match.
How SysAid organises data
SysAid centres on the service record (SR). An SR can be an incident, a request, a problem or a change, and carries a category hierarchy, priority, status, assigned group and agent, request user, notes and activities. Requests and changes can run through action items, the workflow steps SysAid attaches to a service record. SRs link to related items such as other SRs, assets, CIs and knowledge base articles.
Around the SR sit users (agents and end users) and groups, assets (the inventory of hardware and software) and configuration items in the CMDB, with CI types, CI relations and relation types. Each of these has its own endpoints in SysAid’s public API, which is good news for a migration: the relationships you need to keep are exposed, not just flat ticket fields.
Getting data out of SysAid
Route 1: CSV export from the Spaces queue
SysAid documents a queue export in Spaces: open a service record queue, apply filters and sorting, open the three-dot menu and choose Export to CSV. You can also export only selected records from the bulk action bar. SysAid says there are no size limitations and no special permissions are needed. The catch is that the CSV contains only the columns visible in your current view. It is a flat list, without notes history, attachments or relationships.
Use it for what it is good at: record counts and reconciliation. Export open and closed SRs by type and year before you start, and compare those counts with what lands in the target.
Route 2: the REST API
For history and relationships, use the API. The documented basics a migration script has to respect:
| Topic | What SysAid documents | What it means for a migration |
|---|---|---|
| Authentication | Client credentials: create an app key (Client ID and Client Secret), then request an access token. Token lifetime defaults to 24 hours, configurable up to 30 days. Each organisation is limited to 100 app keys | Create one app key for the migration and reuse it. You need SysAid administrator permissions, and API key generation must use SysAid account credentials, not SSO |
| Rate limit | Up to 1,000 requests per 5-minute window, enforced per account. Exceeding it returns HTTP 429; headers show limit, remaining and reset time | Build back-off into the script. The limit is shared by every integration on the account |
| Pagination | Offset-based with limit and offset; general default 20, maximum 500. Service record search returns up to 100 records per request | Page through SRs in date windows rather than one huge query |
| Data format | JSON; dates in ISO 8601 UTC | Convert time zones deliberately when loading the target |
| Updates | Version-based optimistic locking on mutable entities | Only relevant if you write back to SysAid, for example to stamp migrated records |
The SysAid developer API index lists endpoints for service records (search, get by ID), notes (list per record and search across records), activities, action items, related items, users, groups, the category hierarchy, assets, CIs with CI types and relations, and knowledge base articles. That covers what most migrations need.
A rough sense of scale, from the documented limits only: at 1,000 requests per 5 minutes you have about 200 requests a minute. If you fetch notes with one call per service record, 100,000 records need about 100,000 note calls, which is more than eight hours of continuous extraction before activities, related items and retries. Plan the extraction in date windows over several days, and do not run it during working hours if other integrations share the limit.
Attachments and reporting extracts
SysAid’s SysAid “Manage Attachments Storage” documentation page, under Settings > Service Desk, lets administrators view attachments by year and by entity type (service requests, articles, users and so on), and filter, export and delete them. Use it to take a bulk copy of attachments for the archive and to decide which ones need to move with migrated records. SysAid also sells a SysAid Power BI Extract add-on documentation that writes SR data as JSON to OneDrive or to SysAid storage. If you already license it, it is a useful second copy of SR data for validation, but it is not a migration tool.
If you run SysAid on-premises
On-premises SysAid runs on Microsoft SQL Server, as SysAid’s SysAid Migration to Cloud documentation prerequisites show. That gives you a third option: a database-level extract, provided someone understands the schema. We prefer the API for live data, because it returns records the way SysAid presents them, and keep the database backup as the legal archive.
SysAid export checklist
- CSV exports of SR counts by type, status and year (for reconciliation)
- API extraction of open SRs with notes, activities, action items and related items
- Closed SRs for the retention window you have agreed (often 12 to 24 months in the live tool)
- Users, groups and group membership
- Category hierarchy, priorities, statuses and custom fields
- Assets and CIs, with CI types and relations
- Knowledge base articles
- Attachments, via Manage Attachments Storage, for the archive and for migrated records
- A full archive copy for everything you do not migrate
Mapping SysAid to Freshservice and JSM
| SysAid | Freshservice | Jira Service Management |
|---|---|---|
| Service record: incident | Ticket, type Incident | Work item, Incident type |
| Service record: request | Ticket, type Service Request (catalogue items on Growth and above) | Work item, Service request type with request types in the portal |
| Service record: problem | Problem (Pro and Enterprise) | Problem type; advanced incident and problem management is listed on Premium |
| Service record: change | Change (Pro and Enterprise) | Change type; change management with approval workflows is listed on Premium |
| Notes and activities | Private notes and public replies; time entries | Comments (internal or public) and worklogs |
| Action items (workflow steps) | Tasks plus Workflow Automator rules | Workflow statuses and transitions, plus automation rules |
| Categories (hierarchical) | Category, sub-category, item category fields | Request types plus custom fields or components |
| Groups and agents | Agent groups and agents | Teams, queues and agents |
| End users | Requesters (sync from your directory) | Customers (sync from your directory) |
| Assets | Assets by asset type, via CSV import per type | Assets objects by object type, via CSV or JSON import |
| CIs, CI types and relations | CMDB CI types and relationships | Assets object schema with references between objects |
| Knowledge base articles | Solution articles | Confluence knowledge base pages |
| SLAs | SLA policies (multiple on Growth and above) | SLA goals per project |
Two rules from our own projects. Keep the SysAid SR ID in a custom field on every migrated record so you can trace emails and audit questions back. And write down the status and priority mapping and get the service owner to sign it off before any load runs. SysAid statuses are often customised, and every “in progress” variant needs a deliberate home.
Loading into Freshservice
Freshservice has three relevant routes. Tickets and notes go through the partner bulk migration API in the Freshservice bulk migration API guide for data migration partners: up to 50 tickets or notes per request and 10 requests per minute per account, with a 40 MB attachment cap per entity. That is at most 500 records a minute before retries. Freshworks notes that Slack, Teams, business rules and workflows are not muted during migration, so switch them off before loading. Problems, changes, requesters, agents, groups and solution articles go through the standard REST API. Assets load by CSV, one asset type per file, per the Freshservice “Importing Assets” article.
Plan choice: SysAid shops that use problem and change need Freshservice Pro. Official prices from the Freshservice pricing page, checked Nov 11, 2026:
| Plan | Billed annually | Billed monthly | Fit for SysAid leavers |
|---|---|---|---|
| Starter | $19 / £15 | $29 / £25 | Incident and knowledge only; rarely enough |
| Growth | $49 / £40 | $59 / £45 | Adds service catalogue and SLA management; enough if you never used problem or change |
| Pro | $99 / £79 | $119 / £95 | Adds problem, change, release and major incident management; the usual target |
| Enterprise | Contact sales | Contact sales | Adds sandbox, audit logs and Freddy AI Agent (Classic) |
Prices are per agent per month. Freddy AI Copilot is an add-on at $29 / £23 per agent per month billed annually. If you are moving from SysAid because of AI, note that SysAid includes its Copilot in Professional, while Freshservice charges for Copilot on Pro and includes its AI Agent only on Enterprise. Price both sides honestly.
Loading into Jira Service Management
The Atlassian CSV importer documentation imports work items from CSV. Non-admins can import 250 work items per file, and the bulk work-item option cannot map parent-child relationships. Larger and hierarchical imports go through the administrator CSV importer (External System Import). Attachments can be imported by URL, so stage SysAid attachments somewhere the importer can reach. Assets and CIs go into JSM Assets via CSV or JSON import; see the Atlassian guide to preparing data for Assets imports. Plan the object schema first so that SysAid CI relations become object references.
Plan choice: SysAid change processes need Premium, because Atlassian lists change management there. Prices from the Atlassian Jira Service Management pricing page, checked Nov 11, 2026, at the page’s default of 75 agents with monthly billing. Atlassian publishes USD only.
| Plan | USD per agent per month | GBP (indicative) | Notes |
|---|---|---|---|
| Free | $0 | £0 | Up to 3 agents |
| Standard | $21.50 | about £16.04 | Assets included (5,000 objects), audit logs, 3,000 automation steps per user per month |
| Premium | $55.28 | about £41.24 | Change management, advanced incident and problem management, Data Manager, 50,000 objects |
| Enterprise | Contact sales | Contact sales | Billed annually |
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3403 per £1 for 9 Nov 2026, the latest published figure when we checked on Nov 11, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ.
What you rebuild: action items, SLAs and automation
Nothing in SysAid’s configuration layer migrates as configuration. Use the API and admin screens to list what exists, then decide what is worth rebuilding.
| SysAid behaviour | Rebuild in Freshservice | Rebuild in JSM |
|---|---|---|
| Request and change workflows (action items) | Service catalogue items and Workflow Automator | Request types, workflows and automation rules |
| Routing and assignment rules | Workflow Automator, Assignment rules | Automation rules and queues |
| SLAs and escalations | SLA policies | SLA goals and automation |
| Templates | Ticket templates, canned responses | Request type fields and canned responses |
| AI agents and Copilot | Freddy AI Copilot (add-on) and AI Agent (Enterprise) | Rovo agents and virtual service agent (Premium) |
| Integrations | Native apps, connector apps, REST API | Atlassian Marketplace apps, automation webhooks, REST API |
In our experience, open service records sitting halfway through an action-item workflow are the trickiest part of cutover. Either finish them in SysAid during a short overlap, or recreate them in the target as new work with the SysAid history attached as a note. Do not try to replay workflow state.
A phased plan
| Phase | Work | Done when |
|---|---|---|
| 1. Inventory (week 1–2) | Record counts by type and year; list of categories, statuses, custom fields, action-item workflows, SLAs, integrations | Counts and configuration list signed off |
| 2. Design (week 2–4) | Mapping tables, target plan choice, retention window, archive approach | Service owner signs off the mapping |
| 3. Build (week 3–7) | Configure the target: groups, categories, catalogue or request types, SLAs, workflows | An agent can work a request end to end in the target |
| 4. Trial load (week 6–8) | Load a sample of each record type with notes and attachments | Trial counts reconcile with the SysAid CSV exports |
| 5. Full load and delta (week 8–10) | History in date windows; then a delta of records changed since the full load | Counts within agreed tolerance |
| 6. Cutover (week 10–11) | Redirect email and portal, set SysAid read-only, final delta, hypercare | New work only in the target |
These week ranges are our planning defaults for a mid-sized desk, not a promise. Large histories, many custom fields or heavy CMDB use stretch phases 2 and 5. Align cutover with your SysAid renewal date to avoid paying for both.
Best for, and wrong choice when
Freshservice is the better target when
Your SysAid use is mainstream ITSM, you want a guided ITIL tool with official USD and GBP prices, and nobody needs Jira integration.
Jira Service Management is the better target when
Engineering already works in Jira, you want incidents and changes linked to development work, and you are willing to budget for Premium if you run change management.
Stay on SysAid when
Its included AI agents are delivering deflection you would have to pay extra to match, and the reasons to move are not strong. Compare total cost including AI before deciding.
Frequently asked questions
How do I export data from SysAid?
In SysAid Spaces, open a service record queue, apply filters and choose Export to CSV from the three-dot menu. The CSV includes only the visible columns. For notes, relationships, assets and CIs, use SysAid’s REST API.
What are SysAid’s API rate limits?
SysAid documents up to 1,000 requests per 5-minute window, enforced per account, with HTTP 429 when exceeded. Service record search returns up to 100 records per request.
Does Freshservice or JSM have a native SysAid importer?
We did not find one in Freshworks or Atlassian documentation. Use SysAid’s API to extract, then the Freshservice bulk migration API, REST API and CSV asset import, or JSM’s CSV and Assets importers.
Which Freshservice plan matches SysAid Professional?
For incident, request, problem and change, Freshservice Pro at $99 / £79 per agent per month billed annually (official, checked Nov 11, 2026). Freddy AI Copilot is an extra $29 / £23 per agent per month.
Which JSM plan do SysAid users need?
Premium if you run change management, at $55.28 per agent per month at Atlassian’s 75-agent default with monthly billing (about £41.24 indicative). Standard ($21.50) covers incidents, requests and Assets without change management.
Do SysAid action items migrate?
No. Action items are SysAid workflow configuration. Rebuild the workflows that matter in Freshservice Workflow Automator or JSM workflows and automation, and finish or recreate in-flight records at cutover.
How do I move SysAid attachments?
Administrators can export attachments by year and entity type from SysAid’s Manage Attachments Storage page. Keep a full copy for the archive and load the ones linked to migrated records.