Today I used NXT query export for the first time, and I realized that the field values for gifts exported from the same query in NXT vs database view have different field values for gift type and fund list (and possibly others).

This is more than a bit crazy, because any downstream data processing now has to take into account at least two fields that may be using completely different sets of field values. If I want to sort on gift type (to exclude pledges, for instance), I need to filter for two different sets of values. Maintaining this is a pain, because it means that I can't rely on scheduled queries in NXT or in database view...**I need to run both to make sure I've caught any new terms from both systems**.

Consistency is the first job of any decent data system, and currently this migration of queries to NXT is failing that basic test. If we must update field names, fine. Do so in a consistent way so that database view and NXT both provide the same field names and values. It's essential.