Skip to content
DataGrine home

Migrating call logs and recordings when you switch helpdesk or contact centre

Call history rarely moves into a new phone system as calls. What the APIs give you is a call log (who called, when, for how long, which agent, which ticket) and a link to each recording, sometimes one that expires quickly. The usual approach is to carry the log onto the migrated tickets as a note, download the recordings you are allowed to keep into storage you control, link them from the ticket, and settle retention and consent before anything moves.

By the DataGrine team · Updated · 3 min read

Key takeaways

  • Plan for two outputs: a readable call history on each ticket, and an archive of recording files you control.
  • Recording links from APIs can be short-lived. Aircall’s direct recording link is valid for one hour.
  • Retention clocks keep running while you plan. Check them early.
  • Routing, IVR menus and phone numbers are not data. They are rebuilt, and numbers are ported.

What each platform exposes

PlatformCall log and recordingsWorth knowing
Freshcaller (Freshdesk Contact Center)A calls API, and an Export data API Freshworks recommends instead; each recording has a urlPer-minute rate limits by plan
AircallList and search calls; a direct recording link valid for one hourThe last six months of recordings are in the Dashboard; older ones via Aircall Support
TalkdeskA Recordings API that lists a call’s recordingsRecordings are deleted after 180 days by default, configurable by admins
Zendesk TalkIncremental exports of calls, each with its ticket_id; recordings are voice comments on the ticketRecordings are kept with no time limit unless automatic deletion is set

Where a recording link expires, download the recording in the same pass that reads the call. Expect some calls never to have had a recording, and report them as gaps rather than failures.

How call history is usually carried

  • One note per call on the related ticket: date and time with time zone, direction, the customer’s number, the agent, duration, outcome and a link to the recording.
  • A few attributes where reporting needs them, such as call count or last call date.
  • Recording files in storage you control, with access limited to the people who need it, linked by a stable address rather than the source’s expiring link.
  • Calls without tickets either become their own tickets or are summarised on the contact. Decide before the run.

Questions

Asked about this, often.

Can I import call recordings into my new helpdesk?

Usually not as native calls. The common approach is to keep recordings in storage you control and link each one from a note on the migrated ticket, alongside the call details.

How long does Talkdesk keep call recordings?

By default Talkdesk deletes recordings after 180 days. Administrators can change the period, and purged recordings cannot be recovered.

Do I need consent to move call recordings?

Recording laws differ by jurisdiction, and Zendesk notes that some require caller or agent consent. Moving recordings to a new system is a data protection decision as well as a technical one.

What about phone numbers and IVR menus?

They are not data to migrate. Numbers are ported to the new provider in a separate process, and IVR menus, queues and routing rules are rebuilt by hand, so document them before you cancel.

Let’s move your data forward.

Tell us where you are moving from and to. Run it yourself on the DataGrine platform or let our migration team handle it end to end, with 24/7 support either way.

  • A written mapping document before anything moves
  • A sample migration you review before the live run
  • Delta sync at cut-over and rollback per run
  • 24/7 premium support until you sign off