Last updated: September 2026
Configferry translates a feature-flag export from one platform format into another. It runs entirely in your browser — no data leaves your machine, no account is required.
The translation report is the most important output. Read it before deploying. Every rule that could not be translated exactly is listed, and every approximation is explained.
Configferry currently supports translating from LaunchDarkly to Unleash. That is the only translation path available today. Support for additional platforms (Split, flagsmith, custom JSON formats) requires new adapters that are not yet built. See the known limitations section below for details.
No. The tool runs entirely in your browser using client-side JavaScript. The JSON export you paste or upload is processed locally, never transmitted, logged, or stored on any remote server. The only external resource the site loads is Google Fonts for typography. See the Privacy Policy for full details.
Every rule in the export is evaluated. Rules that can be translated exactly are listed in the TRANSLATED section. Rules that could be translated but with a behavioural difference appear in APPROXIMATED with an explanation of what changed and why. Rules with no equivalent in the target platform appear in NOT TRANSLATABLE with the reason. Configferry never silently drops or simplifies a rule.
Percentage-based rollouts are translated in the APPROXIMATED category. LaunchDarkly and Unleash use different bucketing algorithms, so the same percentage value may assign different users to the treatment group. The report includes a note explaining that the bucketing behaviour differs and recommends verifying the rollout after deployment.
No. Configferry is free and requires no account, sign-up, login, or payment. There is no user database, no API authentication, and no stored configuration. Open the App page, paste your export, and translate immediately.
First, read the translation report. Open the downloaded report file and check the APPROXIMATED and NOT TRANSLATABLE sections. Most unexpected differences are explained there. Common causes include:
If the report does not explain the discrepancy, see the contact section below.
These are the current limitations of Configferry that users should know about. We are honest about them because a team that depends on a capability that does not exist is worse off than one that knows the boundaries.
The only supported translation is LaunchDarkly → Unleash. Reverse translation (Unleash → LaunchDarkly) and other platforms (Split, flagsmith, Cloudflare, DevCycle, custom formats) are not built. There is no timeline for additional adapters; priority will be informed by user requests sent to configferry@agen2ic.ai.
Configferry does not connect to any feature-flag platform's API. It cannot fetch an export on your behalf, push translated configuration to a platform, or validate the output against a live environment. It is a file-to-file conversion tool. You must export from the source platform and import to the target platform manually.
LaunchDarkly prerequisite flags have no direct counterpart in Unleash. Prerequisites are reported as NOT TRANSLATABLE with an explanation. You must recreate these dependencies manually in your Unleash project by ordering toggle activations or using custom activation strategies.
Percentage rollouts use different sticky-bucketing algorithms on each platform. A 10% rollout on LaunchDarkly will not necessarily affect the same 10% of users after translation. The report flags these as APPROXIMATED with a bucketing note.
The translation engine is not user-configurable. You cannot add custom mapping rules, override a specific flag's translation, or inspect the internal rule set. The three-part report is the only window into what the engine decided. Custom rule support is a potential future feature but is not currently planned.
There is no hard cap on flag count or JSON file size, but very large exports (thousands of flags) may cause the browser tab to become slow or unresponsive because all processing happens in a single thread. For production-scale exports, consider splitting the export into smaller batches. We recommend batches of 200–500 flags per translation pass.
Support for Configferry is handled directly by the team that builds it. We cannot respond instantly, but we read every message and prioritise by severity.
Email: configferry@agen2ic.ai
Messages to this address reach a human who handles Configferry-specific matters. Please include a description of the issue, the source platform and export format you are using, and any relevant export excerpts (with sensitive values redacted).
If you have a feature request for a platform adapter beyond LaunchDarkly → Unleash, please mention that in your email — requests help determine which adapter is built next. The operator of Configferry is Agen2ic, LLC, a Colorado limited liability company.
Configferry