Skip to main content

Data Migration - API Documentation

Overview

The Data Migration feature exports app data from one Countly environment and imports it into another. It supports archive generation, remote transfer, import token flow, lifecycle status tracking, and cleanup operations.

Database Collections

CollectionPurpose
countly.data_migrationsTracks export/import jobs, progress, remote handoff details, and status history fields.
countly.auth_tokensStores scoped import tokens created for migration import endpoint access.
countly.systemlogsStores migration lifecycle audit actions (for example export/import success/failure and callback reporting).
countly.* and countly_drill.*Source/target app data collections read during export and written during import.

Configuration & Settings

SettingDefaultEffect
Nginx client_max_body_sizeWeb-server defaultInfluences practical max import upload size; surfaced by o/datamigration/get_config as fileSizeLimit.
security request configServer-definedAffects outbound remote calls used by validate/send/report migration workflows.

Operational Flow

  1. Export app data (i/datamigration/export) and capture export ID.
  2. Validate remote target (o/datamigration/validateconnection) if exporting to another server.
  3. Send export (i/datamigration/sendexport) or transfer archive manually.
  4. Start import (i/datamigration/import) and track status (o/datamigration/getstatus).
  5. Clean up local artifacts when done (i/datamigration/delete_export, i/datamigration/delete_import, i/datamigration/delete_all).

Last Updated

2026-02-17