Guides and playbooks
Migration from Homegrown Feature Flags
Replace an in-house flag system in phases so you can keep production stable while Zenmanage becomes the source of truth.
Migration pattern
- 1. Inventory your existing flags and categorize them as boolean, string, or number controls.
- 2. Recreate the highest-value flags in Zenmanage with safe defaults in code.
- 3. Run both systems in parallel temporarily and compare served values for a small set of contexts.
- 4. Switch application reads to Zenmanage once parity is acceptable.
- 5. Remove the old flag path after the new system has been stable in production.
Context migration
Map your current actor identifiers into Zenmanage context type and identifier fields. Do this before you move complex rollout logic, otherwise the audience you think you are targeting may not match the audience Zenmanage sees.
Next step
Take the next integration step in your own stack.
Start with the quickstart that matches your runtime, then return to the reference pages when you need exact request and payload details.