Skip to content

Export and backup

The Export recordings job copies recordings — audio files and/or metadata — to a storage target. It serves two main purposes: recurring backups (for example, a nightly export to an FTP server or S3 bucket) and data handoff (delivering a tenant's recordings to the customer's own storage).

Where: Administration › Storage › Export Recordings, which opens the jobs console filtered to this job type. Jobs run manually or on a schedule.

Job settings

  • Storage Target — the destination; see Storage targets.
  • Filename format — the parameterized path/name template for exported files (see the file name reference). Post-processing parameters such as %{tenant-name}, %{user-name}, and %{group-name} are available here, so exports can be organized by tenant or team.
  • Export dataAudio files and/or Call metadata. Metadata is written as MiaRec-format JSON files, which the import job can restore.
  • Skip existing files — check whether the file already exists at the destination before copying; makes recurring backup runs incremental.
  • Group call segments — group hold/resume segments of the same call together.
  • Remove after export — delete records after a successful export, turning the job into move-to-archive; leave off for backups. Not compatible with Group call segments (the job rejects the combination).
  • Decrypt files — decrypt files before exporting them (see below).
  • Filtering Criteria — which conversations to export (date ranges, tenant, group, and other attributes).
  • Schedule — for recurring backups.

Runs, processed-record counts, and logs are on the job page — see Jobs console.

Encrypted recordings

By default, encrypted recordings are exported as-is, still encrypted — safe for backups, since the destination never holds playable audio and the archive can only be used by importing it together with the encryption key. Enable Decrypt files only when the consumer needs plain audio, and treat the destination accordingly. See Encryption.

Restoring

A MiaRec-format export (metadata + audio) is restored with the Import recordings job — point it at the export location, choose the MiaRec (*.json) vendor format, and import into the same or a new system. For an encrypted archive, import the encryption key first.