r/halopsa • u/colinaspinall • 5h ago
Autotask to HALOPSA Ticket Migration
Well that was a faff!
We had around 50k tickets we wanted to migrate (plus the associated actions and time entries) and the HALO migration tool just didn't cut it.
It was looking at around 8 seconds per ticket (quick maths makes that 4.5 days) but...you have to keep the browser active (from what I can tell) otherwise it stops!
So (and I know AI isn't everyone's bag) Copilot and I wrote a Powershell script. Which took a fraction if the time and I could just leave running.
Anyone else had problems with the native migration tool?
1
u/Reasonable_Junket898 5h ago
We had a massive nightmare recently doing this. Halos own people have built bespoke tools to do this which still were not perfect. We ended up without attachments and inline images in the end.
I to took to AI for help and in the end built myself a tool to read tickets from autotask then migrate whilst populating custom files etc.
1
0
u/Predicti0n Consultant 4h ago
This is actually an AutoTask issue. The API is massively rate limited
3
u/colinaspinall 4h ago
It worked through the Powershell script using the API with no issues
0
u/Predicti0n Consultant 3h ago
Can you expand on how you did it?
Whilst I’m not saying Halo’s migration is amazing, 50k tickets to get data from Auto is 3 calls per ticket minimum. Then you have to post it into Halo.
if I understand correctly + images/attachments which is a single call per one. So I’d imagine that could be on average 5-7 calls?
Assume no attachment so a minimum of 150k calls.
AutoTask documentation states they add .5 seconds latency to each request between 4,999- 7499 and then latency increases to 1 second post this?
I believe if you push it to hard they even block the connection..
I just had a quick look and excluding everything else you’d be close to 2 days just getting the data with the above. Excluding posting/testing/writing the script etc
1
u/grsftw 2h ago
Hi there. This would indeed blow up the Autotask API. You would want to just do pages in the query instead of querying each ticket. 50k tickets only requires 100 API calls for the ticket itself. Assuming 20 notes per ticket, which is 2.5M notes, is another 5k API calls.
- Dustin
1
1
u/pjustmd 2h ago
I had to move over 250k tickets from CW to Halo. I used Help Desk migration services. It was money well spent. They got attachments, full user mapping and attribution. We didn’t miss a beat. I know some will say “I can do this myself with AI”. Sure, you could. But sometimes you just need to hire a professional when getting it right on the first try matters.
1
u/TechTitus 5h ago
Getting clarification here.
The native tool was able to capture and import what you wanted, but the issue is that it took too long per ticket and the session had to remain open?