Migrate from Flagsmith

FlagTGL uses a Flagsmith organisation API key and the Management API. The default hosted URL is https://api.flagsmith.com; self-hosted customers can supply their own API base URL. Flagsmith's data model shares projects, environments, flags, values, identities, traits, and segments, but not every concept should be copied as stored data.

What moves

Flagsmith	FlagTGL	Transformation
Project	Project	Name becomes a normalized project key
Environment	Environment	Name becomes a normalized key; color retained
Feature	Flag	Feature name/key and description retained
Environment feature state	Environment state/default	Enabled state and feature-state value retained
Boolean feature	Boolean variation	false/true used when no remote-config value exists
Remote-config scalar	Typed variation	Boolean, integer, or string becomes the flag's typed value
Segment trait rules	Project segment	Rule groups and supported trait comparisons retained
Segment feature override	Targeting rule	Segment match serves the override state/value before default

Differences that require review

• Identities and their per-environment feature overrides are not imported. Pass equivalent identity traits as FlagTGL context attributes or recreate exceptional targeting explicitly.
• Segment rules are portable only for equality, contains, and numeric greater/less operators, including inclusive comparisons. Modulo, regex, semantic-version, in-list, not-equal, and other Flagsmith-specific operators require manual recreation.
• Multivariate options and provider-specific allocation behavior are not fully represented by the portable remote-config import. Confirm any A/B/n or weighted feature independently.
• Feature version history, change requests, scheduled changes, approvals, Edge/offline state, audit logs, identities, and trait values are not moved.
• Organization/project/environment roles, groups, SSO, API keys, server-side secrets, and third-party integrations are not moved.
• Segment priority and identity-versus-segment override precedence may differ. Validate contexts that match multiple segments or have exceptional source identity overrides.
• Replace Flagsmith SDK initialization and environment keys with a supported FlagTGL SDK/API. Flagsmith environment keys are not reused.

Run the migration

1. Create a dedicated organisation API key with the minimum access needed to list the intended projects, environments, features, versions, and segments.
2. Open Organization → Migrations → Flagsmith and enter the key and API URL.
3. Optionally scope by exact project ID or name.
4. Preview and reconcile projects, environments, flags, and segments.
5. Migrate into a non-production FlagTGL organization.
6. Validate default states, every segment override, remote-config type/value, overlapping segments, and any multivariate behavior using the cutover checklist.