How to export your data from Replicated

Replicated (Vendor Portal) lets you export customer and instance data as CSV from the Customers page, or pull it as JSON/CSV via the Vendor API v3 (customer_instances and events endpoints); there is no single 'export all my data' button — application images, air gap build data, and release manifests are handled separately from this export.

Formats: CSV, JSONPlan: Not specified in the docs — the CSV download and Vendor API export are described as standard Vendor Portal functionality, not gated to a specific plan tierRole: Not specified in the docs — requires a Vendor Portal Team account with access to the Customers page; programmatic export requires a Vendor API token (sent as the Authorization header)

✓ Verified against Replicated's official documentation, September 2026

Step by step

1Log in to the Replicated Vendor Portal and open the Customers page for your application
2Click the 'Download CSV' dropdown on the Customers page
3Choose 'Customers' for license/entitlement-level data only, or 'Customers + Instances' (recommended) for the superset including per-instance Kubernetes distribution, cloud provider, status, and version data
4For a JSON export of the same customer/instance data, call the Vendor API v3 customer_instances endpoint instead of using the UI
5To pull historical instance event/telemetry timeseries data (including custom metrics), call the Vendor API v3 /app/{app_id}/events endpoint with at least one filter (date range, customerIds, or eventTypes)
6Save the resulting CSV/JSON files locally before canceling or downgrading your account
7Cross-reference the data dictionary in the docs to map each CSV/JSON column (e.g. customer_id, instance_kots_version, customer_entitlement__*) before loading it into another system

What the export includes

✓Customer-level fields: customer ID/name, created and expiration dates, channel assignment, customer type (prod/trial/dev/community), status, enabled features (Airgap, GitOps, Snapshot, Identity, Embedded Cluster), and any custom license entitlement fields
✓Instance-level fields (Customers + Instances export): Kubernetes distribution and version, cloud provider/region, KOTS/SDK version, app version, active/inactive status, first/last check-in timestamps, GitOps and preflight status, and custom metrics or tags set on the instance
✓Historical instance event timeseries data via the /app/{app_id}/events API, filterable by date, customer, or event type

What it doesn't include

✗Application container images and registry data, which Replicated stores separately in AWS S3 buckets logically isolated per vendor Team
✗Air gap build data delivered to customers via the download portal, also stored in S3 rather than included in the CSV/JSON export
✗Release/channel manifests, KOTS config, and Helm chart source — these are managed through the Releases/Channels area of the Vendor Portal, not through this export feature
✗Any customer entitlement or custom metric columns that were never configured for a given customer/instance (the docs note customer_has_entitlements and instance_has_custom_metrics flags indicate presence/absence of those columns)

Before you start

⚠The events API requires at least one query parameter (date, customerIds, or eventTypes) to scope the query — it will not return unfiltered results
⚠If a filter references an ID that doesn't exist or that you don't have access to, the API silently returns an empty array rather than an error
⚠Only two CSV download options exist on the Customers page: 'Customers' and 'Customers + Instances' — there is no separate one-click export for events/telemetry from the UI, only via the API
⚠The data dictionary lists dozens of columns (customer_*, instance_*, custom_metric__*, instance_tag__*) so exported CSVs can be wide; map them against the published data dictionary before importing elsewhere

Where to take your data

Free and cheaper tools that can take a Replicated export. See all Replicated alternatives →

Helm

Helm has no concept of customer/license records, so the exported CSV/JSON isn't 'imported' into it directly. Instead, repackage the application itself as a standard Helm chart for distribution, and keep the exported customer/entitlement data in a CRM or billing system to track licenses previously managed in the Replicated Vendor Portal.

Rancher

Use Rancher's app catalog/Fleet to distribute the Helm chart to customer clusters in place of KOTS/Embedded Cluster installs. The exported instance data (Kubernetes distribution, version, status) can inform which clusters to onboard, but Rancher doesn't natively import Replicated's customer CSV.

Portainer

Use Portainer stacks/templates to deploy the application's container images to customer environments instead of KOTS. As with Rancher, the exported customer/license CSV is reference data for your own tracking, not something Portainer imports directly.

Exporting from Replicated: common questions

Can I export all my customer and license data before canceling Replicated?+

Yes — download the 'Customers' or 'Customers + Instances' CSV from the Customers page, or pull the same data as JSON via the Vendor API v3 customer_instances endpoint.

Can I export historical usage/telemetry data, not just current customer status?+

Yes — the Vendor API v3 /app/{app_id}/events endpoint returns historical instance event timeseries data, including custom metrics, filterable by date range, customer ID, or event type.

Does the export include my application's container images or air gap bundles?+

No. Those are stored separately in AWS S3 buckets isolated per vendor Team and are not part of the CSV/JSON customer and instance export.

Do I need a paid plan to export customer data?+

The documentation doesn't state a plan restriction for the CSV download or Vendor API export — it's described as standard Vendor Portal functionality.

What format is the data in, and can I load it into a CRM or BI tool?+

Data is available as CSV (from the UI) or JSON (via the Vendor API), and is explicitly intended for import into CRMs like Salesforce/Gainsight, data warehouses, or BI tools.

Will exporting this data help me migrate my packaging/distribution off Replicated?+

Only partially — it gives you your customer and license records, but rebuilding the packaging/distribution layer (e.g., in Helm, Carvel, Rancher, or Portainer) is a separate task not covered by this export feature.