Migration Overview
Moving from another feature flag platform? FeatureSignals provides an automated migration engine that exports your flags, transforms them to the FeatureSignals model, imports them, and validates parity — so you can switch with confidence.
Supported Platforms
The Migration Process
Every migration follows the same four-phase process:
Export
Use your current platform's API or export tool to pull a complete snapshot of your feature flags. The migration engine supports JSON, CSV, and platform-specific export formats. You'll get flag keys, types, targeting rules, segments, environments, and rollout configurations.
Transform
The migration engine maps your exported data to the FeatureSignals flag model. It handles type conversions (e.g., multivariate flags → AB flag type), targeting rule translation, segment mapping, and default value normalization. A preview report shows what will be created, updated, or skipped before any write occurs.
Import
The transformed flags are created in your FeatureSignals project. The import is transactional — if any flag creation fails, the entire batch is rolled back. You can import to a staging or test environment first to validate without affecting production traffic.
Validate
Run parity checks to confirm that flag evaluations produce the same results in both platforms. The validation engine evaluates each flag in both systems with a sample of user contexts and compares the results. Any discrepancies are reported with the specific flag, context, and expected vs. actual value.
Cutover Strategy
Once your flags are imported and validated, you'll cut over your SDKs. The recommended approach:
- Dual-write (optional). During a transition period, update flags in both platforms simultaneously. This gives you a safety net while you validate the new setup.
- Cut over non-critical environments first. Switch your dev and staging environments to FeatureSignals. Monitor for a few days.
- Canary production traffic. Route a percentage of production traffic to FeatureSignals SDKs. Compare evaluation results.
- Full cutover. Switch all traffic to FeatureSignals. Keep the old platform as read-only for a week as a fallback.
- Deprovision old platform. Export a final backup, then decomission the old platform.
SDK migration is straightforward
Because FeatureSignals SDKs are OpenFeature-native, migrating your code is often as simple as swapping the provider. The OpenFeature API is client.getBooleanValue(flagKey, defaultValue, context) regardless of which platform is behind it. See SDK documentation for language-specific examples.