FEATURE-FLAG CONFIGURATION TRANSLATOR
Configferry maps each rule—translated, approximated, or not translatable—and names every difference. The export never leaves your browser.
01 / THE PROBLEM
Teams migrating between flag platforms—LaunchDarkly to Unleash, Split to a self-hosted service—do it by hand, flag by flag. The exports look similar and are not. A percentage rollout, a user-segment targeting rule and a prerequisite flag each mean something slightly different on each side, and the differences are invisible until a flag behaves differently in production.
Configferry is a precision translation tool for feature-flag configuration. Paste one platform's export, choose the target format, and receive the equivalent configuration plus a translation report in three parts: TRANSLATED, APPROXIMATED, and NOT TRANSLATABLE. A flag that cannot be moved cleanly is named, never silently simplified.
This tool runs entirely in the browser. The export never leaves the page—which matters because a flag export names internal services, customer segments and unreleased features.
02 / HOW IT WORKS
The converter accepts a JSON export from either LaunchDarkly or Unleash, identifies the source platform from the document structure, and maps every flag to its equivalent in the target format.
Drag a JSON file into the upload area or paste the text directly. The parser inspects the document structure to identify the source platform.
Choose the platform you are migrating to from the dropdown. The translator knows both directions: LaunchDarkly ↔ Unleash.
One click runs every flag through the translation rules. Each rule produces a TRANSLATED, APPROXIMATED or NOT TRANSLATABLE result with a note explaining why.
Download the translated configuration and the report. The engine verifies coverage—every source flag has exactly one report entry. Silent drops register as a detected error.
03 / THE REPORT
Every flag in the source export generates exactly one report entry. The three categories are the feature explanation—the tool demonstrates itself as it describes itself.
Direct functional equivalent exists in the target platform. The rule behaves identically after conversion.
Close equivalent exists but semantics differ slightly. The note describes exactly what changed and why.
No equivalent exists in the target. The rule is listed with the reason, so you can decide how to handle it.
04 / WHAT IT COSTS
Configferry runs entirely on the client side. There is no server, no account, and no data storage. The tool itself has no marginal cost, so it is free for anyone to use.
Additional source and target platform adapters require backend work not yet built.
05 / WHAT IT WILL NOT DO
The product is deliberately scoped. These are the things it refuses to do, stated plainly so no team depends on a capability that does not exist.
06 / A TRANSLATION SEEN
A boolean flag enable-dark-mode from a LaunchDarkly export becomes an Unleash toggle. A prerequisite flag produces an APPROXIMATED entry with a note. Here is what the report looks like for one translation pass:
07 / WHY ACCURACY MATTERS
The cost of a silently dropped rule is not theoretical. A percentage rollout that vanishes during migration means the new toggles fire for 100% of users instead of 5%. A prerequisite that is not translated means a dependant flag activates when it should not.
Configferry does not approximate silently. Every difference is named in the report. The team that runs the migration knows exactly what changed and what did not cross, and can decide how to handle each exception before deployment.
“Translation is not complete until every flag that could not be moved is listed, and every flag that was approximated has a note explaining the difference in behaviour.”
TRY THE CONVERTER
No account. No sign-up. No data leaves your browser.
Open Configferry
Configferry