An enterprise data migration doesn’t always mean a data import for a large company. More often than not, it is a complex project that involves custom development.
In Totalmobile's case, they had to split their Freshdesk data across several target projects. They needed to bring an acquired business onto its ticketing platform, Jira Service Management, so customer support could continue to be managed through a single system.
Customers also needed to keep seeing their historical data in the support portal, and the team needed to keep reporting on historical data and trends. This enterprise migration case study explores how Totalmobile approached the migration, customized the process, and transferred its data with Help Desk Migration.
About Totalmobile
Totalmobile is a Belfast-based provider of field service management solutions, founded in 1985 and now a team of 201-500 people. It helps organizations transform how field work gets done. Every day, over 500,000 field staff rely on its field software to work more efficiently and deliver better service.
The Totalmobile team provides services for companies across the UK, the Nordics, Ireland, and Australia. The company serves industries such as housing, utilities, social care, and emergency services. Their field software minimizes admins’ involvement, improves service processes, and helps teams overcome operational challenges.
Enterprise Migration Goals and Scope
Totalmobile needed to merge Freshdesk with its existing ticketing platform, Jira Service Management, so customer support could continue to be managed through a single help desk system. To maintain the customer experience, the team wanted clients still to see their historical data in the support portal. They also wanted to keep reporting on historical data and trends.
What was migrated:
1.2K Articles
How Totalmobile Planned Its Enterprise Help Desk Migration
At first, Totalmobile found Help Desk Migration through a Google search, where it appeared well rated. Then the team contacted our sales reps and discussed the impending enterprise migration in depth.
After that, Totalmobile tested the migration via a free sample migration. They liked that they could customize the migration to their specific needs and data requirements, and they ordered custom work for the ticket and knowledge base structure.
For the Full Migration, Totalmobile chose the Premium support plan. Out-of-hours support during that run was key to the enterprise data migration's success. The Help Desk Migration team also responded quickly to emails ly and resolved questions and issues promptly.
Challenges During the Freshdesk Split
- Migrate source data into five target projects: The Totalmobile team needed to split Freshdesk tickets into five separate Jira projects with source-side filtering.
- An acquisition to absorb: They had to merge the acquired business with the existing Jira Service Management platform without splitting customer support.
- History that still had to be useful: Customers needed to see their past data in the support portal, and the team needed it for reporting and trends.
- A target structure with several rules: Tickets in one project had to land in different Jira issue types. Contacts were assigned to several organizations, while tickets were not assigned to organizations.
- A knowledge base built to order: Articles were filtered at the source and moved into specific spaces, with the structure set by the client’s requirements.
How the Enterprise Migration Was Customized
Totalmobile tested first and then requested the following custom development. Rows marked (custom) were custom work for this migration.
| Option | What it did | Why Totalmobile needed it |
|---|---|---|
| Source-side ticket filtering | Filtered tickets in Freshdesk and migrated each set into a different project in Jira Service Management | One account had to be split into five projects |
| Several issue types in one project (custom) | Migrated tickets into more than one Jira issue type within the same project | Tickets in a project needed different issue types |
| Contacts in several organizations | Migrated contacts assigned to multiple organizations, without assigning tickets to organizations. | Contacts kept their organization links, and tickets stayed independent of them. |
| Knowledge base articles into specific spaces (custom) | Filtered articles at the source, migrated them into a chosen space, and built the knowledge base structure to the client’s requirements. | The knowledge base had to follow Totalmobile’s own structure. |
| Inline images as attachments | Converted inline images into attachments | Jira Service Management doesn’t support inline image migration. This way, Images from ticket conversations stay with the migrated tickets. |
Results of Jira Service Management Migration
- The Freshdesk data migrated into five separate Jira Service Management projects.
- Knowledge base articles now sit in the specific spaces the client chose.
- This cloud migration for enterprise support lets customers view their historical data in the support portal, and the team keeps reporting on it.
Migration Tips from the Totalmobile Team
Why the team recommends Help Desk Migration:
The data migration went well, and the support was top-notch. Help Desk Migration greatly reduces the time it takes to migrate between systems. It also reduces the time technicians or help desk employees spend reconciling migrated data.
Insights for companies splitting one Source into several projects:
1. Run test migrations before the real one
Test the migration thoroughly, so you know all the data comes across correctly in each of your scenarios.
2. Size the run to your outage window
When you migrate data for an operational system out of hours, remember that many tickets with images as attachments take a long time. Confirm that every task fits inside your window.
3. Keep new and migrated data apart in a live system
If the Target is already in use, plan how to avoid disruption. Labels let you quickly tell migrated data from new incoming data.
Split Your Source Data Easily
Totalmobile’s case shows that one account can be split across several projects in a single engineer-led migration. It works when you filter the source data, request custom development where your structure needs it, and test it out before the Full Migration.
As a result, Totalmobile moved 200K tickets and 1.2K articles to meet their requirements, while keeping its historical data available. Run a Free Demo Migration to see how your own tickets, articles, and attachments look in Jira Service Management before you commit.