mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
23 lines
1.1 KiB
Plaintext
23 lines
1.1 KiB
Plaintext
---
|
|
title: "External Migrations"
|
|
sidebarTitle: "Overview"
|
|
description: "Learn how to migrate resources from third-party secrets management platforms to KMS."
|
|
---
|
|
|
|
## Overview
|
|
|
|
KMS supports migrating resources from third-party secrets management platforms to KMS. This is useful if you're looking to easily switch to KMS and wish to move over your existing resources from a different platform.
|
|
|
|
KMS offers two types of migration approaches:
|
|
|
|
- **In-Platform Migration Tooling**: Configure platform connections to enable granular, on-demand imports of secrets, policies, and configurations directly within the KMS UI. This allows you to migrate resources incrementally as needed.
|
|
|
|
- **Bulk Data Import**: Perform one-time organization-level migrations to import all resources from external platforms at once. This is ideal for initial migrations when moving entirely to KMS.
|
|
|
|
## Supported Platforms
|
|
|
|
- [EnvKey](./envkey)
|
|
- [Vault](./vault)
|
|
|
|
We're always looking to add more migration paths for other providers. If we're missing a platform, please open an issue on our [GitHub repository](https://github.com/ghcr.io/hanzoai/kms/issues).
|