Skip to main content
The Confidence plugin for AI coding assistants includes migration kits that automate moving from PostHog, Eppo, Statsig, or Optimizely to Confidence. Each kit guides your AI assistant through recreating your flags in Confidence and rewriting your application code to use the Confidence SDK. Install the kits and pick the one for your platform: 
npx skills add spotify/confidence-ai-plugins
The installer works with Claude Code, Cursor, Codex, Gemini CLI, and other AI assistants, and asks which skills and assistant to install to. To get the full plugin—including flag management and documentation search—install it with your assistant’s own plugin manager instead. The plugin works with Claude Code, Cursor, Codex, and Gemini CLI.

​
How Migration Works

Every migration kit runs in two phases:
  1. Flag definitions: The kit reads your flags, targeting rules, and rollout percentages from the source platform and recreates them in Confidence.
  2. Code transformation: The kit rewrites your application code from the source platform’s SDK to OpenFeature with the Confidence SDK, creating one pull request per flag.
Each phase separates planning from execution. The kit first writes a plan file that you review, then executes it:
  • plan flag generates a migration plan for your flag definitions
  • plan code generates a migration plan for your code changes
  • execute <plan-file> carries out the plan you generated
Plan files are self-contained and resumable. You can pause a migration, review what remains, and continue later—even with a different AI assistant.

​
Install the Confidence Plugin

claude plugin install confidence

​
Before You Begin

To run any migration kit, you need:
  • A Confidence account with a client to resolve flags
  • The Confidence Flags MCP server, authenticated with your account—see the Use AI with Confidence quickstart
  • The Confidence Documentation MCP server, used during code transformation
  • Read access to your source platform, typically an API key—see each migration kit page for details
Some advanced features, such as partial traffic allocation and reusable segments, require a Confidence REST API token in addition to the MCP server. The kit tells you when this applies.

​
Migration Kits

Migrate from PostHog

Move feature flags and multivariate flags with the /confidence:migrate-posthog command.

Migrate from Eppo

Move feature flags, allocations, and audiences with the /confidence:migrate-eppo command.

Migrate from Statsig

Move feature gates, dynamic configs, and experiments with the /confidence:migrate-statsig command.

Migrate from Optimizely

Move flags, rulesets, and audiences with the /confidence:migrate-optimizely command.
The plugin also includes skills for onboarding new Confidence accounts and setting up a data warehouse connection. See the plugin repository for the full list.

Use AI with Confidence

Set up the Confidence MCP servers for your AI assistant

MCP Servers Reference

Complete reference for all MCP tools and capabilities

Analyze a Past Experiment

Re-analyze experiments that ran on another platform

SDK Integration

Integrate Confidence SDKs into your application