Migration guide
Migrate from Split
Feature delivery, reimagined. Again.
Five steps. Five minutes.
Step 1
Install the CLI
One global install. Works on macOS, Linux, and WSL.
terminal
npm install -g @quonfig/cli
Step 2
Run the migration
Point the importer at your Split account and let it run.
terminal
qf import --source split --api-key $YOUR_KEY
Step 3
Agent translates your config
Every flag, segment, and environment becomes a readable JSON file in a git repo.
Step 4
Review the pull request
The agent opens a PR with your entire config. You review the diff.
Step 5
Merge. You're done.
Swap your SDK key and your apps connect to Quonfig.
What gets migrated
Feature flags
Config values
Segments
Targeting rules
Environment configs
Change history
as git commits
Before and after
Split
- Treatments locked in Split's cloud
- Activity log with limited history
- API keys scoped to traffic types
- REST API with rate limits
- No branching for targeting rules
- No code review for split definitions
Quonfig
- Flags as JSON files in a git repo you own
- Full git history: log, diff, blame, revert
- SDK keys: qf_sk_production_a8f7d3e2b1c4
- Agent access via CLI, MCP, or just git
- git checkout -b experiment/new-pricing
- Open a pull request. Same as code.
Start your migration
Install the CLI and run one command. Your Split config becomes git-native JSON in minutes.