For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
      • Custom flags
      • Release flags
      • Kill switch flags
      • Experiment flags
      • Migration flags
        • Creating migration flags
        • Targeting with migration flags
        • Migration flag metrics
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Create migration flags
  • Modify the migration flag template
Feature flagsFlag templatesMigration flags

Creating migration flags

Was this page helpful?
Previous

Targeting with migration flags

Next
Built with

This topic explains how to create migration flags. Migration flags are temporary flags you can use to migrate data or tech systems without causing outages or downtime.

Migration flags can have two, four, or six stages. To learn more about when to use different types of migrations, read Performing multi-stage migrations with migration flags.

Not all SDKs support migration flags

Not all SDKs are compatible with migration flags. For a full list of compatible SDKs, read supported SDKs.

Create migration flags

Here’s how to create a migration flag:

  1. Click Create and choose Flag. The “Create flag” dialog appears.
  2. Enter a unique, human-readable Name. A suggested key auto-populates from the name you enter, but you can customize it if you wish.
  3. (Optional) Click Edit key to update the flag key. You’ll use this key to reference the flag in your code.
  4. (Optional) Enter a Description of the flag. A brief, human-readable description helps your account members understand what the flag is for.
  5. (Optional) Click No template and select 2-, 4-, or 6-stage migration.
    • If you selected 6-stage migration, select a Context kind.
Migrations with six stages require a context kind

You must choose a context kind to create a six-stage migration. The context kind you choose should indicate how the migrated data is partitioned. It determines how rollouts are bucketed and which context kind to reference when you create cohorts.

  1. (Optional) Click on your member name to change the flag maintainer.
  2. (Optional) Click the tag icon to add one or more tags.
  3. (Optional) Click the views icon to add the flag to a view.
  4. (Optional) Click All SDKs to make the flag unavailable to client-side or mobile SDKs. Flags are available to all SDKs by default.
  5. (Optional) Click Temporary to change the flag from temporary to permanent.
  6. Click Create flag.

The flag Targeting tab appears.

After you create a flag, you can make further changes to it as needed, such as to update flag targeting.

To learn more, read Creating new flags.

Modify the migration flag template

To modify your migration flag template:

  1. Click the project dropdown. The project menu appears:

The project menu.

The project menu.
  1. Select Project settings.
  2. Select Flags. The Flags settings list appears.
  3. In the “Flag templates section, click the pencil icon next to “Migration.”
  4. In the “Tags” section, type to add tags to each new flag by default.
  5. Click Save.

Verify that the updated default template settings are correct by navigating to the Flags list and creating a new migration flag.