Migrate from ConfigCat
FlagTGL uses a ConfigCat Public Management API credential ID and password. The default API URL is https://api.configcat.com. ConfigCat also provides a product JSON export containing flags/settings, values, targeting rules, percentage options, configs, environments, tags, and segments, as described in its export documentation. FlagTGL currently uses the Management API so preview and repeatable sync do not require uploading files.
What moves
| ConfigCat | FlagTGL | Transformation |
|---|---|---|
| Config within a product | Project | Key is generated from product name plus config name and normalized |
| Product environment | Environment | Environment name becomes its normalized key |
| Feature flag or setting | Typed flag | Boolean, string, integer, and double values become boolean, string, or number variations |
| Environment default value | Default variation | Flag remains enabled and serves that typed value |
| Targeting rule user condition | Rule clause | Supported attribute comparison is normalized |
| Segment condition | Segment-match clause | Segment ID resolves to the migrated segment key |
| Percentage options | Percentage rollout | Values become variations and percentages remain weights |
| Segment | Project segment | Name, description, and supported conditions retained |
Differences that require review
- ConfigCat product is an organizational container; FlagTGL creates one project for each selected config. Product-level permissions and metadata are not reproduced.
- Comparator fidelity is limited to equality, contains, starts-with, ends-with, and greater/less families. Negated, case-sensitive, semantic-version, date/time, array, confidential/hashed, and other specialized comparators must be recreated and tested.
- Prerequisite-flag conditions are not migrated as FlagTGL prerequisites. Recreate prerequisite relationships explicitly.
- Percentage weights are preserved, but ConfigCat documents sticky, cross-SDK bucketing per flag. FlagTGL uses its own bucketing algorithm and user key, so the same person is not guaranteed to remain in the same cohort.
- Complex rule results that serve nested percentage options need manual review; the portable importer treats top-level targeting results and top-level percentage options as FlagTGL rules.
- ConfigCat tags, zombie/stale reports, code references, webhooks, config preferences, audit history, and organization access are not moved.
- Users are runtime contexts in FlagTGL, not imported ConfigCat account or audience records. Management API credentials and SDK keys are never copied.
- Replace ConfigCat SDK initialization and SDK keys with a supported FlagTGL SDK/API. There is no drop-in ConfigCat SDK credential swap.
Run the migration
- Create a dedicated Public Management API credential and record its ID and password. Use the narrowest organization permissions available.
- Open Organization → Migrations → ConfigCat and enter both credential fields.
- Optionally scope by config ID, config name, or product name. Product-name scope selects every config in that product.
- Preview the generated project keys and counts. Pay particular attention when product and config names normalize to similar keys.
- Migrate into a non-production FlagTGL organization.
- Validate every specialized comparator, prerequisite, and percentage rollout using the cutover checklist.
ConfigCat V1 and V2 value shapes are read through their corresponding Management API endpoints. Environment order is kept deterministic so repeat migrations produce stable FlagTGL configuration.