ServiceRocket and the expensive gap between buying software and making it work

The semiconductor company had chosen its destination. Its internal service operation was moving to Jira Service Management. Then the journey stopped. Seven years of history, spread across FreshService and FreshDesk, would not fit through the standard import tools. Ticket comments, attachments and custom fields were the problem. A ticket without its history is rather like a detective novel with the middle chapters removed.

For more than 1,400 users, this was working memory: what had broken, who had tried to fix it, and which remedy had finally worked. ServiceRocket’s account of the project describes custom scripts and API extraction to move more than 26,000 tickets. The team also rebuilt more than 100 automations. The company reports preserving all critical ticket data and completing the move without disrupting operations.

That episode makes a useful introduction to the company. The software purchase was settled. The difficult questions concerned continuity. Would yesterday’s knowledge remain available tomorrow? Would an employee’s familiar request still reach the right person? ServiceRocket earns its place by answering questions that a product demonstration can afford to skip.

A bug tracker with an unlikely entourage

Rob Castaneda started the business in Sydney in 2001, after returning from Silicon Valley. Its early work involved Enterprise Java training and projects. Atlassian arrived a year later. Although their offices were only blocks apart, Castaneda recalls that a contact in Silicon Valley made the introduction. Geography apparently needed a connecting flight.

In his account of the partnership, Castaneda remembers being challenged about working with a company selling a two-thousand-dollar bug tracker. He saw appeal in Atlassian’s combination of openness, self-service and a personable brand. ServiceRocket became an early user as well as a partner: it bought Confluence while the product was in beta and replaced existing tools with Jira and Confluence version 0.2.

The recollection has a pleasingly domestic detail. A reseller agreement for Johnson & Johnson helped develop the reseller program while an Atlassian operations lead typed invoices in Microsoft Word at a kitchen table. Enterprise procurement, one of business’s least romantic activities, had a kitchen-table beginning.

The relationship produced support operations, training and apps. ServiceRocket opened its Kuala Lumpur office in 2005. A custom Salesforce-Jira plugin followed in 2007, became publicly available in 2010 and acquired a cloud version in 2014. These dates suggest a repeatable method: solve a customer’s particular problem, then see whether the solution deserves a wider audience.

Two customers on either side of the same problem

ServiceRocket serves enterprises using software and vendors selling it. Its Tech Services help the first group administer, configure, migrate and learn platforms, especially Atlassian and Miro. Its Platform Services help the second group deliver technical support, customer education, onboarding and app engineering. A vendor wants customers to adopt its product; an enterprise wants employees to accomplish something with the product it bought.

The public customer record includes Polycom and Code42, with platform-service testimonials from Docker, Preset and Thought Industries. ServiceRocket reports more than 4,000 active customers. The work reaches beyond development teams into service desks and other business operations. Jira’s usefulness depends partly on whether those different groups can agree on what a request means.

The business model follows that breadth: project services, continuing managed services and support, training, licensing and commercial apps. Its market position combines specialist Atlassian knowledge with the ability to keep operating after an implementation finishes. Buyers can also choose another Atlassian partner or do the work internally. The relevant comparison is the depth of expertise and ongoing capacity required by their particular environment.

Customer education gives the company another route into the adoption problem. In 2015 it acquired the assets behind Learndot, a learning management platform. A Code42 case describes replacing multiple learning systems with a centralized environment linked to Salesforce and Skytap. Course registration, delivery and hands-on practice became parts of one education operation. Training here is work infrastructure, rather than a ceremonial webinar at launch.

What fails before the software does

The semiconductor story begins with a tool limitation. Polycom’s published customer account describes another: a custom Bugzilla migration that exceeded built-in tooling. ServiceRocket also built integration plugins that could track and resubmit transactions between Siebel and Jira, accommodating imperfect data and unavailable systems.

“The built in migration tools didn’t cut it.”Kent Bodell, Polycom

An Australian energy-company case exposes a different failure. Projects and Confluence spaces had accumulated without consistent lifecycle rules. Some workflows were unused; others were complicated. Archived projects still had data links. The approaching Jira 11 upgrade and a future cloud move made that untidiness consequential. More engineering alone would have left the ownership problem intact.

According to ServiceRocket, it began with lightweight planning discipline and earned the mandate for a 12-month Center of Excellence. Program leadership handled priorities; architecture established standards; engineering carried out fixes and testing. Quarterly planning and business reviews sat alongside weekly governance forums and a rolling backlog. The company reports that the user base grew from 2,000 to 6,000 under that arrangement.

The useful change of mind was quite specific: early evidence of orderly delivery persuaded the customer to authorize a larger operating model. That makes the case more instructive than an exhortation to “transform.” Prove that a small routine helps people make decisions, then ask it to carry more responsibility.

The bill includes the things the demo omits

A migration budget includes subscriptions, add-on apps, data transfer, integrations, customizations, training and support. ServiceRocket lists these as cost factors. A tidy license comparison can therefore conceal a much less tidy project. Matching the old system’s exceptions may demand more effort than moving its rows of data.

In a published 2024 case, an unnamed technology company changed partners after delays and difficulties aligning stakeholders. ServiceRocket reused the previous discovery work, brought stakeholders into agreement and completed the migration in ten weeks. The case reports a saving of 20% of the initial budget, reinvested in post-migration support. The customer subsequently engaged ServiceRocket for HR service management.

A separate media-company case describes moving from ServiceNow to Jira Service Management, with an Arabic portal, asset-system integration and automation to retain needed functions. It reports return on investment in eighteen months. Both cases reward careful reading: savings belong to particular starting conditions, functionality and contracts. Another buyer’s arithmetic will depend on its own system.

The habits worth borrowing

Start with a specimen of your ugliest data. Include comments, attachments, custom fields and dependencies. Test an entire service request, from submission to resolution. Decide who owns platform rules and who can retire a space or workflow. Put training and support in the initial budget, where they can compete honestly with everything else.

Then introduce a small decision-making routine before a grand governance program. The energy case offers a sequence worth copying. It also suggests limits: governance needs people with authority to make decisions, while migration needs workable mappings and validated integrations. If every old customization must survive unchanged, a new platform may require substantial custom engineering. Small, straightforward installations may have less reason to buy an extensive managed service.

ServiceRocket calls its employees Rocketeers and lists “Share the Knowledge” and “Talk Straight” among five values. Its careers materials describe hack weeks, career pathways and a return-to-work program for primary caregivers. Those are declared practices rather than proof of every employee’s experience, but they fit a business whose expertise must move between colleagues as well as customers.

In September 2026, the company announced Atlassian Gold Solution Partner status in EMEA, alongside its Platinum standing in AMER and APAC. Twenty-five years after its Sydney beginning, the central task remains recognizable. A company chooses a tool. Then someone must preserve its memory, adapt its routines and teach its people. ServiceRocket has made a business of staying for that part.