Export v2 to CSV loses custom fields?

I’m working on migration to V3, but it appears that one of my custom fields is skipped when exporting to CSV. (300 is dropped, 301 is kept).

Are you sure that is part of the custom fields list? If it was added to key, but later custom field was deleted for the version, it won’t show up.

This is in my product:

image561×135 4.72 KB

I managed to figure out the API calls to get an existing key, so I’m just pulling it from the API. It’s going to hit your servers twice as hard when I do the transition, but that’ll only be for a few thousand keys, once.

Looks like some bug, not replicable in general. It’s good you figured out the API, v2 and v3 are hosted separately, for v3 just ensure you do that in the rate limit (max 50 reqs in 5 sec window).