API Enum Migration Mapper
Map the values of an old enum to a new one and see which values are unmapped, removed or new. Works with JSON Schema, OpenAPI, GraphQL, protobuf and plain lists.
Accepts up to 200,000 characters per definition and up to 10,000 values per enum. Matching is done in your browser. Downloads are two CSV files and a JSON report. JSON Schema, OpenAPI, GraphQL enum, .proto enum or one value per line. Up to 200,000 characters. Review the settings before running.
Your result
How to use API Enum Migration Mapper
- Paste the old enum definition.
- Paste the new enum definition and choose how values are matched.
- Add confirmed overrides for values that were renamed.
- Run the mapping and download the from,to CSV and the review table.
Useful next steps
Accepts up to 200,000 characters per definition and up to 10,000 values per enum. Matching is done in your browser. Downloads are two CSV files and a JSON report.
Matching
Identical values of the same JSON type map exactly. Normalized matching also ignores letter case, spaces, dashes and underscores while preserving other punctuation and Unicode characters. When two new values could match, the old value is marked ambiguous instead of guessing. Distinct values in one enum that have identical CSV text, such as 1 and "1", are rejected because a two-column migration file cannot distinguish them. Overrides entered as from,to CSV win; an empty to marks a removed value.
Where enums are found
For JSON or YAML the tool uses the only enum array in the document, or the one your JSON Pointer names. For GraphQL SDL and .proto files it uses the only enum, or the one you name. A plain list uses one value per line.
Using the result
The from,to CSV contains only mapped values, ready for Dataset value mapper. The review CSV lists every old value with its status and every new value that nothing maps to. The tool builds the map; it does not change your data.