LaunchDarkly migration checker
Drop in a LaunchDarkly flags export and find out what a move to rollfuse would actually involve: how many flags and targeting rules you have, which constructs map straight across, and which ones need a person to look at them.
Your file is read and analyzed in this browser tab. It is never uploaded, stored, or sent anywhere: open your network inspector and check.
Save the JSON response from LaunchDarkly's GET /api/v2/flags/{projectKey} endpoint, then pick that file here. Up to 10 MB.
Three steps, none of them involve us
Export your flags
Call LaunchDarkly's GET /api/v2/flags/{projectKey} with a read token and save the JSON response.
Analyze it in your browser
Pick the file above. It is parsed by JavaScript running in this tab; no bytes leave your machine.
Read the plan
You get the counts and the score straight away, and the flag-by-flag plan once you leave an email.
Quick answers
Does my export get uploaded anywhere?
No. The file is read with the browser's own file API and parsed in this tab. The only request this page makes is the email you choose to submit.
How is the compatibility score calculated?
Every construct in your export is classified against what rollfuse supports today: a direct match counts as one, a construct that needs a human decision counts as a half, and one with no equivalent counts as zero. The score is that total over the number of constructs.
Does a high score mean the migration is automatic?
No. This tool plans a migration; it does not perform one. Nothing here creates flags, rules, or rollouts in rollfuse.
What if my export has constructs you do not support?
They are named in the plan, with the reason, instead of being quietly translated into something that would behave differently.
Ready to move off LaunchDarkly?
Sign up with Google and import your flags on the free plan, no credit card required. Want help planning the move? Request access and an operator walks through the plan with you.