Migration guide
Migrate from Flagsmith
Open source, but still a database.
Free and local, or cloud and live
One command either way, and the git repo is yours in both. Read it straight from disk for free — or sync it to Quonfig Cloud and every SDK gets the update the moment a flag flips.
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 Flagsmith account and let it run.
terminal
qfg migrate --from flagsmith --source-api-key $YOUR_KEY --dir ./my-workspace
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
Flagsmith
- Flags stored in Postgres or SQLite
- Audit log in the dashboard only
- Agent access via REST API with pagination
Quonfig
- Flags as JSON files in a git repo you own
- Full git history: log, diff, blame, revert
- Agent access via CLI or just git
Start your migration
Install the CLI and run one command. Your Flagsmith config becomes git-native JSON in minutes.