Methodology: built from vendor pricing pages, vendor documentation and migration pages, and two attributed third parties (Vendr and itsm.tools), all checked on 13 Oct 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.
Help desk migration cost is set by three things: how much you move, how tangled it is, and how you run the cutover. There is no neutral public benchmark for what an ITSM migration project costs, so any number quoted without a scope behind it is a guess. If you have to get a migration budget approved, this guide breaks the price into the drivers a provider quotes on, the pricing models on offer, and the costs that never reach the quote: license overlap, staff time and freeze periods.
Key takeaways
- No platform vendor we checked publishes a dollar price for an ITSM migration. BMC Helix prices its own Remedy to BMC Helix ITSM Migration Service in success credits (120 or 300) and scopes it to up to 3 integrations (BMC Helix service listing, as of 13 Oct 2026).
- Workflows, automations, business rules, SLA definitions, macros and running SLA timers are rebuilt on the target, not migrated, and that rebuild belongs in the budget. During a bulk load, Freshservice says workflows and business rules are not muted, so a cutover plan has to account for them (Freshservice support, modified 24 Nov 2025).
- License overlap is a real budget line. At list price, one month of 100 Freshservice Pro agents is $9,900 ($99 per agent per month billed annually; Freshworks pricing page, as of 13 Oct 2026).
- Renewal timing changes the math. Atlassian's new cloud list prices took effect on 13 Oct 2026 PT, moving Service Collection Standard for 100 agents (annual) from $19,700 to $21,000 (Atlassian pricing tables, as of 13 Oct 2026).
Help desk migration cost: the short answer
A provider's quote is driven by eight things you can count before you ask for a price, and your own budget adds a second set. The biggest lever on a migration quote is scope: what you decide to move, and how much of it has to be proven correct.
| Cost driver | What pushes the cost up | What to count before you ask for a quote |
|---|---|---|
| Record volume | More records to load and reconcile | Record counts per type and per year |
| Attachment volume | Large files and target size limits | Total attachment size, files over the target's limit |
| History depth | Retired users, groups and categories to map | Years of history that audit, reporting and AI actually need |
| Customizations | Each custom field, state and table needs mapping and a test | Custom fields, states and tables in scope |
| Integrations | Each is repointed, tested and switched at cutover | Integration inventory with owner and direction |
| CMDB and relationships | CIs and their links must load in order | CI count by class, relationship count, ticket links to CIs |
| Test cycles | Each run means a review and a fix round | Number of test runs and who signs off each one |
| Cutover window | A short freeze needs delta sync and weekend staff | Freeze length, go/no-go owners, rollback criteria |
Why there is no honest price list for ITSM migration
Vendors publish durations, not prices. Freshworks says ServiceNow to Freshservice "migration timelines typically range from 4-12 weeks, depending on data volume, customization complexity" (Freshworks migration page, as of 13 Oct 2026).
The closest thing to a published price is BMC Helix's ITSM Migration Service, from Remedy ITSM on premises to hosted BMC Helix ITSM. It lists 14 to 20 weeks and 120 or 300 success credits depending on delivery option, with no dollar amount. It covers standard configurations and up to 3 integrations, and says "Non-Standard remediation for Customization/Integrations are excluded" (BMC Helix service listing, as of 13 Oct 2026). Even the platform vendor prices against a fixed scope and hands the exceptions back to the customer.
Vendr says ServiceNow "implementation costs can range from a significant portion to multiples of annual software spend" (Vendr ServiceNow page, updated Feb 2026). That bundles implementation and migration, so read it as a warning about scale, not a migration price.
The cost drivers in detail
Record and attachment volume
Volume decides how many load runs and reconciliation checks the project needs, and platform limits turn volume into labor. Atlassian recommends about 1,500 work items per CSV file and estimates about an hour per file (Atlassian support, as of 13 Oct 2026). Freshservice's bulk migration route takes 50 tickets or notes per request at 10 requests per minute, limits the article marks "To be confirmed post load testing" (Freshservice support, modified 24 Nov 2025).
Attachments add work too. Freshservice caps attachments on a ticket created through its API at 40 MB in total (Freshservice API docs, as of 13 Oct 2026), and every file over a limit needs a decision.
History depth
Older records carry retired users, closed assignment groups and dead categories, each needing a mapping rule. An itsm.tools article by Brian Parks sets out three options (full history, active work only, or an archive plus targeted migration) and says the cost of migrating everything "is significant, as is the technical risk."
Cutting history to zero is not free either. A ServiceNow employee's Predictive Intelligence FAQ recommends "from 30,000 through 300,000" records to train a good classification solution (ServiceNow community, 7 Nov 2019). History you leave behind is training data you no longer have.
Customizations
Custom fields, states and tables are where a quote moves after discovery, because each needs a target, a transformation rule and a test. ServiceNow's own workbook warns that "excessive customization can create downstream maintenance costs," "increase the testing time required for upgrades, and delay implementation" (ServiceNow Essentials for implementation success, March 2021). Leaving such an instance, you pay to map every custom state, then again to rebuild the logic behind it.
Integrations
Each integration is a small project: repointed, tested end to end and switched at the same moment as the data. The BMC Helix listing caps its standard scope at 3 integrations, which shows how directly integration count drives price.
CMDB and relationships
Relationships drive CMDB migration cost, because they only work if everything they point to already exists. Atlassian says you "must import the referenced object type first," and that each import "will generate a new key for each object," so references are mapped by label, not key (Atlassian support, as of 13 Oct 2026). That means ordered loads, lookup tables and a reconciliation pass for every link, so a CMDB with deep relationship chains costs more to move than a flat asset list of the same size.
Test cycles
Each test migration is a full load into a non-production target, a review by service desk leads and a round of fixes, paid in provider time and your reviewers' time. In the BMC Helix listing, the customer performs user functional testing for up to three weeks. Agree the number of runs and the acceptance criteria before you sign, so an extra run is a priced decision rather than a surprise.
Cutover window
The shorter the freeze, the more the cutover costs. A short window needs a bulk load beforehand, a delta sync, weekend staffing and a rollback plan. Freshworks says delta migration matters most for organizations that cannot freeze their ServiceNow instance (Freshworks migration page, as of 13 Oct 2026). Automation adds work: Freshservice says Slack, Teams, business rules and workflows "will not be muted" during bulk migration, so someone has to pause and restore them.
Scope decisions that set the bill
How much history to move. Ask audit, reporting and the team planning AI features how many years they use. The itsm.tools article calls an archive plus targeted migration "essentially the best of both worlds." An archive still needs storage and an owner, so price it too.
What gets rebuilt, not migrated. Workflows, automations, business rules, SLA definitions, macros and running SLA timers are rebuilt on the target. Recorded SLA outcomes can move as data, but the clock logic cannot. Budget the rebuild as its own line with whoever configures the target, so it does not hide inside the migration quote.
How imported history behaves. Atlassian documents that SLAs keep counting on closed issues imported by CSV, because they have no history beyond the creation event. Its fixes, a flag field that excludes them from SLA goals or a bulk transition to Done, are cheap before cutover (Atlassian support, updated 26 Sep 2025).
ITSM migration pricing models compared
The pricing model decides who pays when the data turns out messier than expected. None is cheaper by default.
| Pricing model | How the price is set | Who carries the risk of surprises | Fits when | Ask before you sign |
|---|---|---|---|---|
| Fixed project price | One price for an agreed scope, set after discovery | The provider inside the scope; you outside it, through change requests | Volumes, customizations and integrations are known | What triggers a change request? How many test runs are included? |
| Per record | A rate multiplied by the records moved | You, if counts grow or "record" is loosely defined | A simple record model with few relationships | Do comments, attachments and CI relationships count as records? Are re-runs charged? |
| Time and materials | Hours or days multiplied by a rate | You | Discovery, unknown data quality, custom logic | Is there a cap? Weekly burn reports? |
A fixed price is only as good as the scope behind it. Per-record pricing tracks volume but not complexity: two instances with the same ticket count can be very different jobs. Time and materials has no ceiling unless you write one in. One middle path is a paid discovery on time and materials, then a fixed price for the phases discovery has made predictable.
Hidden costs of a help desk migration
These costs never appear on the migration quote, but they are part of the budget your CFO will see.
License overlap during cutover
You pay for two platforms from the day the target is licensed until the source is switched off. The table shows one month of overlap at list price for 100 agents, before discounts or tax.
| Platform and plan | List price (as of 13 Oct 2026) | One month, 100 agents, at list |
|---|---|---|
| Jira Service Management (Service Collection) Standard | $20 per agent per month (Atlassian pricing page) | $2,000 |
| Jira Service Management (Service Collection) Premium | $51.42 per agent per month (Atlassian pricing page) | $5,142 |
| Freshservice Growth | $49 per agent per month, billed annually (Freshworks pricing page) | $4,900 |
| Freshservice Pro | $99 per agent per month, billed annually (Freshworks pricing page) | $9,900 |
| ServiceNow ITSM | No public price, custom quote (ServiceNow pricing page) | Ask your account team |
Contract terms set the real overlap. Freshworks says downgrades or cancellations take effect "at the end of your term" (Freshservice pricing FAQ, as of 13 Oct 2026). Atlassian bills monthly Service Collection subscriptions for the exact number of agents (Atlassian pricing page, as of 13 Oct 2026). Leaving too early is risky too: Zendesk says that when you cancel "you lose access to your data," with reactivation on request within 90 days and automated deletion after that (Zendesk support, as of 13 Oct 2026).
Internal staff time
Your people confirm mappings, review test loads, test integrations and sign off reconciliation. The BMC Helix listing makes the customer supply user functional testing and an application subject matter expert. Put named people and days against each task.
Freeze periods
A change freeze stops configuration changes, new catalog items and process fixes until cutover, and a weekend cutover can mean overtime. Price the freeze in business terms: what waits, and for how long.
Rebuild, training, hypercare and add-ons
The rebuild of workflows, SLA definitions, automations and macros is a separate line from the data migration. Add agent training and a hypercare period with the source read-only for lookups. Check API capacity too: Freshservice sells add-on packs that raise the overall API limit to 1,000 or 2,000 calls per minute on Pro and Enterprise, priced through support (Freshservice API docs, as of 13 Oct 2026).
Total cost of ownership: the migration is one-off, the platform is not
The migration is paid once; licenses and upkeep are paid every year, so compare options over the full contract term. A simple TCO model for a switch has five lines: target licenses for the term, the migration project, rebuild and implementation work, license overlap, and internal staff time. Set that against the cost of staying: the current renewal plus the upkeep of customizations you already carry, which ServiceNow's workbook links to maintenance cost and longer upgrade testing. For scale, Vendr reports a median ServiceNow contract of $129,871 per year across 109 purchases of all ServiceNow products (Vendr, updated Feb 2026). That is a third-party median, not a quote, but it shows the size of the recurring line a one-off migration sits next to.
Also price the value of history: a cheaper migration that drops years of records can cost more later in audit requests and reporting gaps.
How to lower help desk migration cost and time it to your renewal
- Count before you ask for a quote. Use the driver table above, so providers price your real volumes, customizations and integrations.
- Scope history by need. Move what audit, reporting and AI use, and archive the rest with a named owner.
- Clean before you move. Retire unused custom fields, states and categories. ServiceNow's workbook warns against "a lift and shift of bad (or incomplete) processes."
- Plan backwards from the renewal date. Land cutover before the source renews, with room for reconciliation, and check for list-price changes like Atlassian's on 13 Oct 2026. Vendr notes that pricing improves when buyers engage "well before renewal or purchase deadlines" (Vendr, updated Feb 2026).
- Buy target licenses in step with the rollout. Service Collection monthly billing charges for the exact number of agents, and Freshservice sells day passes "starting from $3" for occasional users such as test reviewers (vendor pricing pages, as of 13 Oct 2026).
- Keep the source only as long as you need it. Hold it read-only through reconciliation and hypercare, then end it at term. Put test runs, reviewers and acceptance criteria in the contract too.
FAQ
Methodology
We checked vendor pricing pages, documentation and migration pages (Atlassian, Freshworks, ServiceNow, Zendesk, BMC Helix) and two attributed third parties (Vendr and itsm.tools) on 13 Oct 2026. Overlap figures are list price times 100 agents for one month. No migration provider's pricing page was used, and we did not run hands-on tests. Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.