> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enkryptify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migration guide

> Migrate your secrets from other tools to Enkryptify.

This guide covers migrating secrets from common sources into Enkryptify.

## Migration checklist

Regardless of where you're migrating from, follow these steps:

<Steps>
  <Step title="Inventory your secrets">
    List all secrets across your environments. Identify which are still in use, which are duplicated and which can be retired.
  </Step>

  <Step title="Set up your Enkryptify workspace">
    Create your workspace, teams, projects and environments to match your current structure. See [Quickstart](/getting-started/quickstart).
  </Step>

  <Step title="Add secrets">
    Add secrets through the dashboard or CLI. Start with a non-production environment to verify the process.
  </Step>

  <Step title="Secrets injection">
    Replace existing secret injection with the [Enkryptify CLI](/cli/quickstart) and set up [syncs](/sync/overview) to your providers.
  </Step>

  <Step title="Decommission old sources">
    Once everything runs on Enkryptify, remove secrets from your old tool and revoke any unused credentials.
  </Step>
</Steps>

## From .env files

If your team shares `.env` files (via Slack, email or a shared drive), you can add each key-value pair to Enkryptify through the dashboard or the [CLI](/cli/commands#import).

After migrating, remove `.env` files from your workflow and use `ek run` instead:

```bash theme={"dark"}
# Before
npm run start

# After
ek run -- npm run start
```

Keep `.env` in your `.gitignore` to prevent accidental commits.

## From cloud provider secret managers

If you're using AWS Secrets Manager, GCP Secret Manager or similar:

1. Export the current secret values
2. Add them to Enkryptify
3. Set up a [sync](/sync/overview) back to the same provider if you still need secrets there
4. Use Enkryptify as the single source of truth going forward

This gives you centralized management while keeping secrets available in your cloud provider.