Which files can be exported and imported to Qlik Replicate to allow for remote backup, migration, troubleshooting, and configuration updates of tasks?

Qlik Replicate uses JSON (JavaScript Object Notation) files to export and import task definitions. This feature is fundamental for administrative operations such as creating backups, migrating tasks between different Replicate servers, or sharing task configurations with Qlik Support for troubleshooting. The exported JSON file encapsulates all the necessary task settings, including source and target endpoint configurations, table selections, and transformation rules, allowing for a complete and portable representation of the task.

A. Task CFG files: Qlik Replicate does not use the .cfg extension for the export and import of task definitions; this format is not standard for this function.

B. Task XML files: While XML is a common data interchange format, Qlik Replicate has standardized on JSON for exporting and importing task configurations.

C. Task INI files: INI is a legacy configuration file format and is not used by Qlik Replicate for managing modern, complex task definitions.

---

1. Qlik Replicate User Guide, "Exporting and importing tasks" section: The official documentation explicitly states, "You can export one or more task definitions to a JSON file. You can then import the task(s) to the same or a different Replicate server." This confirms JSON as the correct file format for task migration and backup. (Accessed via Qlik Help Portal for Qlik Replicate, May 2024 version).

2. Qlik Replicate repctl Command Line Reference, "exportrepository" command: The documentation for the command-line utility repctl shows the syntax for exporting a task, which specifies a JSON file. For example: repctl exportrepository task= file=. This provides further official validation of the JSON format. (Accessed via Qlik Help Portal, repctl Command Line Utility documentation).